From: Dave Taht <dave@taht.net>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: "cake\@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cobalt through checkpatch
Date: Thu, 23 Nov 2017 09:07:28 -0800 [thread overview]
Message-ID: <87po88x6sv.fsf@nemesis.taht.net> (raw)
In-Reply-To: <7FAC50AA-5AEB-475E-B796-2933D3F48BD7@darbyshire-bryant.me.uk> (Kevin Darbyshire-Bryant's message of "Thu, 23 Nov 2017 15:14:50 +0000")
Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
>> On 21 Nov 2017, at 21:59, Dave Taht <dave@taht.net> wrote:
>>
>>
>> You will want to pull and rebase on top of this.
>>
>> Are there any other patches still lying out of tree worth considering?
>
> Just did a PR for turning max_skblen (or whatever it is) to a u32….since there *are* super packets out there >64KB.
There are?
> Opinions on doing a PR for LEDE so they can enjoy(/crash) the fruits of our latest cobalt. They’re currently missing ingress mode & ack filtering filtering toys.
Nah. Let's get it into net-next first this time. I would hope for some
good comments.
Also, I *think* that that version will build on 4.9 without any backward
compatability cruft except for patching pkt_sched.h. Is lede fully 4.9 now?
>
> KDB
>
>
>>
>> * retired cobalt.c
>> * made checkpatch considerably less unhappy
>> (down to zero warnings and checks)
>> * I added a few comments as well.
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2017-11-23 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 21:59 Dave Taht
2017-11-23 15:14 ` Kevin Darbyshire-Bryant
2017-11-23 17:07 ` Dave Taht [this message]
2017-11-23 17:44 ` Kevin Darbyshire-Bryant
2017-11-23 21:34 ` 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=87po88x6sv.fsf@nemesis.taht.net \
--to=dave@taht.net \
--cc=cake@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