From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] CAKE related iproute2 & kernel patches - keeping things in sync
Date: Sun, 29 Jul 2018 10:05:42 +0000 [thread overview]
Message-ID: <942CB8C5-81AD-4359-8DEB-77603EB91D1F@darbyshire-bryant.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
To whom it may concern (Dave) ;-)
This is a general plea that when patches are submitted to upstream please can we also commit them to our current development repositories.
4.19 isn’t even released yet, so most people, including Openwrt, get cake via our 'out of tree’ repositories. This is also a good idea from a point of view of testing. I appreciate the latest changes are of ‘one line’ type variety and so mostly harmless but ideally it should at least be in our own out of tree repo’s first/at the same time.
I had to submit the latest ‘split-gso by default’ patch, accepted to upstream, manually to our own cake repo for Toke to commit. I note with some distress that there’s an ‘iproute2’ upstream patch pending to enable the userspace side of the same thing that currently is NOT in the ‘tc-adv’ repo.
Dare I also suggest that a man page update would be appreciated by iproute2-next too.
The above would make the ‘Cake for Openwrt’ maintainer very happy ;-)
Cheers,
Kevin D-B
012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-07-29 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 10:05 Kevin Darbyshire-Bryant [this message]
2018-07-29 23:42 ` Dave Taht
2018-07-30 15:07 ` Kevin Darbyshire-Bryant
2018-07-30 15:41 ` Loganaden Velvindron
2018-07-30 17:23 ` [Cake] man page bikeshed Dave Taht
2018-07-30 17:39 ` Dave Taht
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=942CB8C5-81AD-4359-8DEB-77603EB91D1F@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