From: Rich Brown <richb.hanover@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] (very) rough guide to 'Cake' in OpenWrt
Date: Fri, 17 Jul 2015 11:58:07 -0400 [thread overview]
Message-ID: <ABCC4038-998A-4971-B35B-036F5805DD3B@gmail.com> (raw)
In-Reply-To: <55A8CDD1.6000201@darbyshire-bryant.me.uk>
Hi Kevin,
This is great. I'm not in a position to test it out right now, but am cheering wildly from the sidelines!
Rich
On Jul 17, 2015, at 5:41 AM, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> If anyone is interested, I've updated http://www.bufferbloat.net/projects/codel/wiki/Cake to include details of how I get 'Cake' into OpenWrt.
>
> Feel free to ignore, amend, point, laugh etc as required.
>
> Kevin
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2015-07-17 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 9:41 Kevin Darbyshire-Bryant
2015-07-17 15:58 ` Rich Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ABCC4038-998A-4971-B35B-036F5805DD3B@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox