From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: David Miller <davem@davemloft.net>,
stable@vger.kernel.org, cake@lists.bufferbloat.net
Subject: Re: [Cake] [PATCH for-4.19 0/3] Backport of series: 'sched: A few small fixes for sch_cake' from 5.1
Date: Fri, 05 Apr 2019 14:43:53 +0200 [thread overview]
Message-ID: <87h8bc1v1y.fsf@toke.dk> (raw)
In-Reply-To: <20190405122044.GB2299@kroah.com>
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Fri, Apr 05, 2019 at 02:13:18PM +0200, Toke Høiland-Jørgensen wrote:
>> Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
>>
>> > On Fri, Apr 05, 2019 at 12:28:21PM +0200, Toke Høiland-Jørgensen wrote:
>> >> Hi Greg
>> >>
>> >> This series contains backports for a couple of fixes to sch_cake that was just
>> >> merged for 5.1. This series backports an earlier refactoring commit, which makes
>> >> the fixes themselves apply cleanly from upstream.
>> >
>> > You have read:
>> > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>> > for how to submit networking patches to the stable trees, right?
>> >
>> > I suggest trying it that way first...
>>
>> Yeah, Dave already queued the original fixes up for stable, but they are
>> not going to apply cleanly on 4.19; hence the first patch in this
>> series.
>>
>> I thought it was better to just include the full series with that, for
>> context, but maybe that was wrong? Should I just have sent the first
>> one? If so, feel free to just take the first patch in this series and
>> let the others go through the usual stable submission process...
>
> Dave queues up and sends me the stable backports for networking code,
> as the document states. If there is a special series needed for 4.19,
> I'm sure he would be glad to take them. Or, I can take them directly,
> after I have the 5.0 series queued up, if I get an ack from him.
>
> But to seemingly circumvent the normal process, isn't ok, I need to
> know that at least you tried :)
Well I did ask Dave if he wanted me to supply a backport, see
https://marc.info/?l=linux-netdev&m=155440061002032&w=2 - I just thought
sending that directly to you was the natural thing to do. Certainly
wasn't trying to circumvent process, just haven't done any backports for
the net tree before :)
Actually, looking at the log again now, I see that I got my versions
mixed up, and the backport patch is also needed for 5.0... so I guess
I'll just (re-)submit that to Dave to put into his stable queue...
-Toke
prev parent reply other threads:[~2019-04-05 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 10:28 Toke Høiland-Jørgensen
2019-04-05 10:28 ` [Cake] [PATCH for-4.19 3/3] sch_cake: Make sure we can write the IP header before changing DSCP bits Toke Høiland-Jørgensen
2019-04-05 10:28 ` [Cake] [PATCH for-4.19 2/3] sch_cake: Use tc_skb_protocol() helper for getting packet protocol Toke Høiland-Jørgensen
2019-04-05 10:28 ` [Cake] [PATCH for-4.19 1/3] sch_cake: Simplify logic in cake_select_tin() Toke Høiland-Jørgensen
2019-04-29 12:43 ` Greg Kroah-Hartman
2019-04-29 12:45 ` Greg Kroah-Hartman
2019-04-05 11:34 ` [Cake] [PATCH for-4.19 0/3] Backport of series: 'sched: A few small fixes for sch_cake' from 5.1 Greg Kroah-Hartman
2019-04-05 12:13 ` Toke Høiland-Jørgensen
2019-04-05 12:20 ` Greg Kroah-Hartman
2019-04-05 12:43 ` Toke Høiland-Jørgensen [this message]
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=87h8bc1v1y.fsf@toke.dk \
--to=toke@redhat.com \
--cc=cake@lists.bufferbloat.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
/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