From: Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Cake List" <cake@lists.bufferbloat.net>,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [Cake] Patch "sch_cake: avoid possible divide by zero in cake_enqueue()" has been added to the 4.19-stable tree
Date: Sun, 12 Jan 2020 09:53:40 +0000 [thread overview]
Message-ID: <0418C624-2EAC-4541-AB8F-5CC6F3538AE7@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw5FGuyFhkej_V7wQXgGx6+dwve7fVj6+X0OZcO68GEhYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
> On 11 Jan 2020, at 21:38, Dave Taht <dave.taht@gmail.com> wrote:
>
> Thank you for all the gymnastics to keep cake alive in openwrt.
>
> I would still like there to be a sce branch of the out of tree work
> that I could point people at
> in my lca talk this week, but I understand that's increasingly difficult.
Jonathan advised me that the version of SCE in CAKE was out of date and we didn’t really want openwrt accidentally using the bonus features, hence the ‘no objection’ to removing all the non upstream kernel stuff from master. Perhaps creating an ’SCE’ feature branch is the way forward? Wireguard recently went through a similar change in that now wireguard is in (very recent) kernels, Jason has split development repos into something like ‘Wireguard for upstream’, ‘Wireguard for out-of-tree with loads of compat stubs’ & ‘wireguard userspace tools’.
We have a similar problem in that we have requirement for ‘cake for upstream’, ‘cake for out-of-tree’ & ‘cake for out-of-tree feature dev'
Cheers,
Kevin
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-12 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 8:18 gregkh
2020-01-11 20:40 ` Dave Taht
2020-01-11 21:20 ` Kevin 'ldir' Darbyshire-Bryant
2020-01-11 21:38 ` Dave Taht
2020-01-12 9:53 ` Kevin 'ldir' Darbyshire-Bryant [this message]
2020-01-16 12:47 ` Sebastian Gottschall
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=0418C624-2EAC-4541-AB8F-5CC6F3538AE7@darbyshire-bryant.me.uk \
--to=ldir@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=toke@toke.dk \
/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