From: John David Anglin <dave.anglin@bell.net>
To: Liam Beguin <liambeguin@gmail.com>,
James.Bottomley@HansenPartnership.com, deller@gmx.de
Cc: linux-parisc@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v1 1/1] parisc: add support for cmpxchg on u8 pointers
Date: Sun, 19 Jul 2020 10:37:27 -0400 [thread overview]
Message-ID: <76ee667c-49e3-3a96-4d25-81141af94dee@bell.net> (raw)
In-Reply-To: <20200718201021.23918-1-liambeguin@gmail.com>
Looks good to me.
On 2020-07-18 4:10 p.m., Liam Beguin wrote:
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Liam Beguin <liambeguin@gmail.com>
Tested-by: Dave Anglin <dave.anglin@bell.net>
> ---
> arch/parisc/include/asm/cmpxchg.h | 2 ++
> arch/parisc/lib/bitops.c | 12 ++++++++++++
> 2 files changed, 14 insertions(+)
--
John David Anglin dave.anglin@bell.net
prev parent reply other threads:[~2020-07-19 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 20:10 [PATCH v1 1/1] parisc: add support for cmpxchg on u8 pointers Liam Beguin
2020-07-19 14:37 ` John David Anglin [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=76ee667c-49e3-3a96-4d25-81141af94dee@bell.net \
--to=dave.anglin@bell.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=deller@gmx.de \
--cc=liambeguin@gmail.com \
--cc=linux-parisc@vger.kernel.org \
--cc=lkp@intel.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).