From: George Spelvin <lkml@SDF.ORG>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>, George Spelvin <lkml@sdf.org>,
Masahiro Yamada <masahiroy@kernel.org>,
clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] int128: fix __uint128_t compiler test in Kconfig
Date: Tue, 10 Mar 2020 10:55:52 +0000 [thread overview]
Message-ID: <20200310105552.GA24925@SDF.ORG> (raw)
In-Reply-To: <20200310101250.22374-2-masahiroy@kernel.org>
Thank you! As your 1/2 commit message explained, the best way to fix
this was not entirely obvious.
FWIW, this series
Tested-by: George Spelvin <lkml@sdf.org>
next prev parent reply other threads:[~2020-03-10 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 10:12 [PATCH 1/2] kconfig: introduce m32-flag and m64-flag Masahiro Yamada
2020-03-10 10:12 ` [PATCH 2/2] int128: fix __uint128_t compiler test in Kconfig Masahiro Yamada
2020-03-10 10:55 ` George Spelvin [this message]
2020-03-10 15:46 ` [PATCH 1/2] kconfig: introduce m32-flag and m64-flag Nathan Chancellor
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=20200310105552.GA24925@SDF.ORG \
--to=lkml@sdf.org \
--cc=ardb@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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