From: Yury Norov <yury.norov@gmail.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-kernel@vger.kernel.org, ardb@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH V3 0/2] uapi: Add support for GENMASK_U128()
Date: Fri, 2 Aug 2024 10:34:21 -0700 [thread overview]
Message-ID: <Zq0YnYAM9RoforVV@yury-ThinkPad> (raw)
In-Reply-To: <1781c39a-2280-49ed-aaaa-b1684744615e@arm.com>
On Fri, Aug 02, 2024 at 07:00:43AM +0530, Anshuman Khandual wrote:
>
>
> On 8/1/24 20:13, Yury Norov wrote:
> > On Thu, Aug 1, 2024 at 12:16 AM Anshuman Khandual
> > <anshuman.khandual@arm.com> wrote:
> >>
> >> This adds support for GENMASK_U128() and some corresponding tests as well.
> >> GENMASK_U128() generated 128 bit masks will be required later on the arm64
> >> platform for enabling FEAT_SYSREG128 and FEAT_D128 features.
> >>
> >> Because GENMAKS_U128() depends on __int128 data type being supported in the
> >> compiler, its usage needs to be protected with CONFIG_ARCH_SUPPORTS_INT128.
> >>
> >> Cc: Andrew Morton <akpm@linux-foundation.org>
> >> Cc: Yury Norov <yury.norov@gmail.com>
> >> Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> >> Cc: Arnd Bergmann <arnd@arndb.de>>
> >> Cc: linux-kernel@vger.kernel.org
> >> Cc: linux-arch@vger.kernel.org
> >
> > For the patches:
> >
> > Reviewed-by: Yury Norov <yury.norov@gmail.com>
>
> Thanks Yury.
>
> >
> > This series doesn't include a real use-case for the new macros. Do you
> > have some?
> > I can take it via my branch, but I need at least one use-case to not
> > merge dead code.
>
> I have recently posted the following patch for arm64 platform although
> most of the subsequent work is still in progress. But for now there
> are some corresponding tests for this new GENMASK_U128() ABI as well.
> Hence it will be really great to have these two patches merged first.
> Thank you.
>
> https://lore.kernel.org/all/20240801054436.612024-1-anshuman.khandual@arm.com/
If you're going to merge the above patch in 6.12, you'd normally send
it together with GENMASK_U128 preparation series, get an ACK from me
and Rasmus for bitops part and move through arm64 tree.
Whatever, I've merged it in bitmap-for-next for testing. Please keep
me posted for any following patches.
Thanks,
Yury
prev parent reply other threads:[~2024-08-02 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 7:16 [PATCH V3 0/2] uapi: Add support for GENMASK_U128() Anshuman Khandual
2024-08-01 7:16 ` [PATCH V3 1/2] uapi: Define GENMASK_U128 Anshuman Khandual
2024-08-16 6:28 ` Anshuman Khandual
2024-08-17 13:57 ` Yury Norov
2024-08-19 3:18 ` Anshuman Khandual
2024-08-19 7:13 ` Arnd Bergmann
2024-08-20 1:25 ` Anshuman Khandual
2024-08-20 6:35 ` Arnd Bergmann
2024-08-01 7:16 ` [PATCH V3 2/2] lib/test_bits.c: Add tests for GENMASK_U128() Anshuman Khandual
2024-08-20 3:36 ` Anshuman Khandual
2024-08-01 14:43 ` [PATCH V3 0/2] uapi: Add support " Yury Norov
2024-08-02 1:30 ` Anshuman Khandual
2024-08-02 17:34 ` Yury Norov [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=Zq0YnYAM9RoforVV@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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