From: Cong Wang <xiyou.wangcong@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Roland Franke <fli4l@franke-prem.de>,
Jiri Pirko <jiri@mellanox.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Two net_sched fixes for stable
Date: Tue, 6 Feb 2018 21:11:15 -0800 [thread overview]
Message-ID: <CAM_iQpX4LsGmcGxsQpSF_pfEduZU203H31-FCn2=YJDg=Ro3oQ@mail.gmail.com> (raw)
In-Reply-To: <20180206.152026.385299397181734332.davem@davemloft.net>
On Tue, Feb 6, 2018 at 12:20 PM, David Miller <davem@davemloft.net> wrote:
> From: Cong Wang <xiyou.wangcong@gmail.com>
>>
>> Please let me know how you want to handle this for 4.14.
>
> Ok, I sent this off for 4.15 -stable but I need you to do the
> 4.14 backport.
>
OK. I assume you mean I should send the backports directly
to stable. I will do it.
Thanks.
next prev parent reply other threads:[~2018-02-07 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 19:25 Two net_sched fixes for stable Cong Wang
2018-02-06 20:20 ` David Miller
2018-02-07 5:11 ` Cong Wang [this message]
2018-02-07 15:20 ` David Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM_iQpX4LsGmcGxsQpSF_pfEduZU203H31-FCn2=YJDg=Ro3oQ@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=fli4l@franke-prem.de \
--cc=jiri@mellanox.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).