From: Cong Wang <cwang@twopensource.com>
To: "Vitaly E. Lavrov" <lve@guap.ru>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH] tc filter not show last u32 filter
Date: Tue, 21 Apr 2015 13:25:38 -0700 [thread overview]
Message-ID: <CAHA+R7N+m0GPgvcxYXb0GbrApdTCq7RZSLj2c5Fi6b3Q8UAbTQ@mail.gmail.com> (raw)
In-Reply-To: <5536ADFC.8070601@guap.ru>
On Tue, Apr 21, 2015 at 1:07 PM, Vitaly E. Lavrov <lve@guap.ru> wrote:
>
> A similar patch is already exists in the
> git.kernel.org/linux-stable.git/master (commit
> b057df24a7536cce6c372efe9d0e3d1558afedf4)
> and linux-4.0.y.
>
> The patch can be applied to branches of the kernel 3.14, 3.18 and 3.19. Why
> is this not done at once?
>
That commit should already have been backported to all stable kernels, so why
do we need a different one?
prev parent reply other threads:[~2015-04-21 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 17:53 [RFC PATCH] tc filter not show last u32 filter Vitaly E. Lavrov
2015-04-21 18:17 ` Sergei Shtylyov
2015-04-21 20:07 ` Vitaly E. Lavrov
2015-04-21 20:25 ` Cong Wang [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHA+R7N+m0GPgvcxYXb0GbrApdTCq7RZSLj2c5Fi6b3Q8UAbTQ@mail.gmail.com \
--to=cwang@twopensource.com \
--cc=lve@guap.ru \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
/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).