From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH V2 0/2] uapi: Add support for GENMASK_U128()
Date: Fri, 26 Jul 2024 09:04:12 +0530 [thread overview]
Message-ID: <980dac50-8b7d-4bef-98a3-e410949737a9@arm.com> (raw)
In-Reply-To: <20240725140543.9601ffdb94b5a6103dfd906f@linux-foundation.org>
On 7/26/24 02:35, Andrew Morton wrote:
> On Thu, 25 Jul 2024 11:18:06 +0530 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.
>
> If this will be required for ongoing ARM development prior to the 6.11
> release then it would make sense for these changes to be carried in the
> relevant ARM tree.
Hello Andrew,
These changes are not required prior to 6.11, hence being taken via the mm
tree is fine.
- Anshuman
next prev parent reply other threads:[~2024-07-26 3:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 5:48 [PATCH V2 0/2] uapi: Add support for GENMASK_U128() Anshuman Khandual
2024-07-25 5:48 ` [PATCH V2 1/2] uapi: Define GENMASK_U128 Anshuman Khandual
2024-07-30 18:15 ` Yury Norov
2024-07-31 3:44 ` Anshuman Khandual
2024-07-31 16:38 ` Yury Norov
2024-07-31 17:16 ` Arnd Bergmann
2024-07-25 5:48 ` [PATCH V2 2/2] lib/test_bits.c: Add tests for GENMASK_U128() Anshuman Khandual
2024-07-30 18:20 ` Yury Norov
2024-07-31 4:11 ` Anshuman Khandual
2024-07-25 21:05 ` [PATCH V2 0/2] uapi: Add support " Andrew Morton
2024-07-26 3:34 ` Anshuman Khandual [this message]
2024-07-30 4:29 ` Anshuman Khandual
2024-07-30 12:29 ` Arnd Bergmann
2024-07-31 2:39 ` Anshuman Khandual
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=980dac50-8b7d-4bef-98a3-e410949737a9@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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