From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Thibaut <hacks@slashdirt.org>, Jonathan Morton <chromatix99@gmail.com>
Cc: Erik Taraldsen via Cake <cake@lists.bufferbloat.net>,
Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Subject: Re: [Cake] Trouble with CAKE
Date: Sat, 14 Dec 2019 13:59:35 +0100 [thread overview]
Message-ID: <874ky3cbbc.fsf@toke.dk> (raw)
In-Reply-To: <D6F8BB5F-EFA7-4275-84E6-48479356DD93@slashdirt.org>
Thibaut <hacks@slashdirt.org> writes:
>> On 14 Dec 2019, at 13:09, Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>>> On 14 Dec, 2019, at 1:59 pm, Thibaut <hacks@slashdirt.org> wrote:
>>>
>>> I’m wondering if this could be an “use of uninitialized data” type of bug.
>>
>> This is why I wouldn't keep working on an old kernel that's full of vendor patches.
>
> Forgive me for trying to use cake on a supported stable distro.
>
> All distros are full of vendor patches (OpenWRT is no exception). The
> subset of linux machines that use vanilla is ‘below measurable
> threshold’...
The Linux kernel development moves at a fairly rapid pace, and sadly
it's not practical to have fully supported backwards compatibility in a
community effort such as CAKE.
Now, this doesn't mean that we won't take patches to fix things for old
kernels; or even help with debugging on old versions, as you've already
seen in this thread. But the reality is unfortunately that the bulk of
this effort is going to have to be on the users running on those
kernels. I.e., you in this case. Such is open source: everyone scratches
their own itch and the end result is something that (mostly) works for
everyone :)
-Toke
next prev parent reply other threads:[~2019-12-14 12:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 13:43 Thibaut
2019-12-13 14:02 ` Jonathan Morton
2019-12-13 22:39 ` Thibaut
2019-12-13 22:40 ` Thibaut
2019-12-13 23:52 ` Thibaut
2019-12-14 9:50 ` Jonathan Morton
2019-12-14 10:01 ` Thibaut
2019-12-14 10:35 ` Kevin 'ldir' Darbyshire-Bryant
2019-12-14 10:56 ` Kevin 'ldir' Darbyshire-Bryant
2019-12-14 11:59 ` Thibaut
2019-12-14 12:07 ` Thibaut
2019-12-14 12:09 ` Jonathan Morton
2019-12-14 12:11 ` Thibaut
2019-12-14 12:59 ` Toke Høiland-Jørgensen [this message]
2019-12-14 14:04 ` Thibaut
2019-12-14 21:35 ` Toke Høiland-Jørgensen
2019-12-13 14:13 ` Thibaut
2019-12-13 14:15 ` Sebastian Moeller
2019-12-13 14:21 ` Thibaut
2019-12-13 18:44 ` Thibaut
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=874ky3cbbc.fsf@toke.dk \
--to=toke@redhat.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=hacks@slashdirt.org \
--cc=ldir@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