From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] [Codel] Proposing COBALT
Date: Thu, 30 Jun 2016 09:16:54 +0100 [thread overview]
Message-ID: <5774D576.8040104@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <5773E7C4.6030402@darbyshire-bryant.me.uk>
On 29/06/16 16:22, Kevin Darbyshire-Bryant wrote:
>
>
> Ok, so the above is done: cobalt merged into mainline cake/master.
> cobalt branch rebased/fast-forwarded to the same place, so don't
> forget to 'git pull' (or fetch & merge) your own repos.
>
> Patches for LEDE to point at those latest updates have been sent in
> and subject to build testing should be accepted shortly.
Now accepted.
>
> The updated tc containing package will be 'tc_4.4.0-3' - note the
> version 3.
>
> I'm still trying to understand why the kmod-sched-cake package version
> doesn't change in quite the way I expected ;-)
Solved that too - some 'legacy' package makefile cruft. You're looking
for kmod-sched-cake -
4.4.14+2016-06-29-747954dd0bde66bb28d2b6c2c109597c9abbe5c5-1 in the
output of 'opkg list' as the COBALT enabled version of cake.
Kevin
next prev parent reply other threads:[~2016-06-30 8:17 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 10:04 [Cake] " Jonathan Morton
2016-05-20 11:37 ` moeller0
2016-05-20 12:18 ` Jonathan Morton
2016-05-20 13:22 ` moeller0
2016-05-20 14:36 ` Jonathan Morton
2016-05-20 16:03 ` David Lang
2016-05-20 17:31 ` Jonathan Morton
2016-05-20 16:37 ` Luis E. Garcia
2016-05-20 16:43 ` Jonathan Morton
2016-05-20 16:55 ` Luis E. Garcia
2016-05-23 18:30 ` Jonathan Morton
2016-05-23 19:11 ` Luis E. Garcia
2016-05-24 13:47 ` [Cake] [Codel] " Jeff Weeks
2016-05-24 14:07 ` Jonathan Morton
2016-05-24 15:52 ` Dave Täht
2016-05-24 15:56 ` Jonathan Morton
2016-05-24 16:02 ` Dave Taht
2016-05-25 6:40 ` Loganaden Velvindron
2016-05-25 12:00 ` Benjamin Cronce
2016-05-26 12:33 ` Jonathan Morton
2016-06-03 19:09 ` Noah Causin
2016-06-03 19:34 ` Jonathan Morton
2016-06-04 1:01 ` Andrew McGregor
2016-06-04 6:23 ` Jonathan Morton
2016-06-04 13:55 ` Jonathan Morton
2016-06-04 14:01 ` moeller0
2016-06-04 14:16 ` Vincent Frentzel
2016-06-04 14:16 ` Jonathan Morton
2016-06-04 15:03 ` moeller0
2016-06-04 17:10 ` Noah Causin
2016-06-04 17:49 ` Eric Dumazet
2016-06-04 19:55 ` Jonathan Morton
2016-06-04 20:56 ` Eric Dumazet
2016-06-27 3:56 ` Jonathan Morton
2016-06-27 7:59 ` moeller0
2016-06-27 15:18 ` Kevin Darbyshire-Bryant
2016-06-28 2:51 ` Jonathan Morton
2016-06-28 8:40 ` Kevin Darbyshire-Bryant
2016-06-28 15:33 ` Jonathan Morton
2016-06-28 17:37 ` Kevin Darbyshire-Bryant
2016-06-29 15:22 ` Kevin Darbyshire-Bryant
2016-06-30 8:16 ` Kevin Darbyshire-Bryant [this message]
2016-06-28 15:44 ` Dave Taht
2016-05-20 13:41 ` [Cake] " David Lang
2016-05-20 13:46 ` moeller0
2016-05-20 14:04 ` David Lang
2016-05-20 15:12 ` Jonathan Morton
2016-05-20 16:05 ` David Lang
2016-05-20 17:06 ` Jonathan Morton
2016-05-20 16:20 ` [Cake] [Codel] " Rick Jones
2016-05-20 16:35 ` Jonathan Morton
2016-05-20 17:01 ` Rick Jones
2016-05-20 17:07 ` Jonathan Morton
2016-05-20 17:21 ` Rick Jones
2016-05-20 17:26 ` David Lang
2016-05-20 17:33 ` Jonathan Morton
2016-05-20 14:09 ` [Cake] " Jonathan Morton
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5774D576.8040104@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
/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