All of lore.kernel.org
 help / color / mirror / Atom feed
From: ast@plumgrid.com (Alexei Starovoitov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: bpf: fix signedness bug in loading 64-bit immediate
Date: Fri, 08 May 2015 08:30:05 -0700	[thread overview]
Message-ID: <554CD67D.8040408@plumgrid.com> (raw)
In-Reply-To: <20150508151704.GF25587@arm.com>

On 5/8/15 8:17 AM, Will Deacon wrote:
>
> Ok, I plan to apply the patch below for 4.1.

great catch. Looks good to me.
Xi, could you send a separate patch for test_bpf update to net-next?
Thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Alexei Starovoitov <ast@plumgrid.com>
To: Will Deacon <will.deacon@arm.com>, Xi Wang <xi.wang@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Zi Shen Lim <zlim.lnx@gmail.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>
Subject: Re: [PATCH] arm64: bpf: fix signedness bug in loading 64-bit immediate
Date: Fri, 08 May 2015 08:30:05 -0700	[thread overview]
Message-ID: <554CD67D.8040408@plumgrid.com> (raw)
In-Reply-To: <20150508151704.GF25587@arm.com>

On 5/8/15 8:17 AM, Will Deacon wrote:
>
> Ok, I plan to apply the patch below for 4.1.

great catch. Looks good to me.
Xi, could you send a separate patch for test_bpf update to net-next?
Thanks!


  reply	other threads:[~2015-05-08 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  5:39 [PATCH] arm64: bpf: fix signedness bug in loading 64-bit immediate Xi Wang
2015-05-08  5:39 ` Xi Wang
2015-05-08  8:38 ` Will Deacon
2015-05-08  8:38   ` Will Deacon
2015-05-08  8:45   ` Xi Wang
2015-05-08  8:45     ` Xi Wang
2015-05-08 15:17     ` Will Deacon
2015-05-08 15:17       ` Will Deacon
2015-05-08 15:30       ` Alexei Starovoitov [this message]
2015-05-08 15:30         ` Alexei Starovoitov

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=554CD67D.8040408@plumgrid.com \
    --to=ast@plumgrid.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.