From: Heiko Carstens <hca@linux.ibm.com>
To: Huilong Deng <denghuilong@cdjrlc.com>
Cc: borntraeger@de.ibm.com, yury.norov@gmail.com,
geert@linux-m68k.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/bitops: Return true/false (not 1/0) from bool functions
Date: Mon, 18 Oct 2021 12:42:11 +0200 [thread overview]
Message-ID: <YW1PgzE2w/8Qg5Eb@osiris> (raw)
In-Reply-To: <20211017092057.24179-1-denghuilong@cdjrlc.com>
On Sun, Oct 17, 2021 at 05:20:57PM +0800, Huilong Deng wrote:
> Signed-off-by: Huilong Deng <denghuilong@cdjrlc.com>
> ---
> arch/s390/include/asm/bitops.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
prev parent reply other threads:[~2021-10-18 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 9:20 [PATCH] s390/bitops: Return true/false (not 1/0) from bool functions Huilong Deng
2021-10-18 10:42 ` Heiko Carstens [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=YW1PgzE2w/8Qg5Eb@osiris \
--to=hca@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=denghuilong@cdjrlc.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=yury.norov@gmail.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).