From: Greg KH <greg@kroah.com>
To: Indan Zupancic <indan@nul.nu>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: bpf_jit: fix BPF_S_ALU_AND_K compilation
Date: Sat, 31 Mar 2012 08:13:27 -0700 [thread overview]
Message-ID: <20120331151327.GA25059@kroah.com> (raw)
In-Reply-To: <40f4b91c5200771f223966f368095c63.squirrel@webmail.greenhost.nl>
On Sat, Mar 31, 2012 at 08:52:09PM +1100, Indan Zupancic wrote:
> Hello,
>
> Finally, after much searching I found one little bug.
>
> [PATCH] net: bpf_jit: fix BPF_S_ALU_AND_K compilation
>
> Small typo resulted in bad code generation for certain
> values of K for the BPF_S_ALU_AND_K instruction.
>
> Signed-off-by: Indan Zupancic <indan@nul.nu>
> ---
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2012-03-31 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 9:52 [PATCH] net: bpf_jit: fix BPF_S_ALU_AND_K compilation Indan Zupancic
2012-03-31 10:23 ` Eric Dumazet
2012-03-31 15:13 ` Greg KH [this message]
2012-03-31 23:47 ` Indan Zupancic
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=20120331151327.GA25059@kroah.com \
--to=greg@kroah.com \
--cc=eric.dumazet@gmail.com \
--cc=indan@nul.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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