From: Suzuki.Poulose@arm.com (Suzuki K. Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64/cpufeature.h: Add macros for a cpu features testing
Date: Wed, 16 Sep 2015 15:48:09 +0100 [thread overview]
Message-ID: <55F98129.9080609@arm.com> (raw)
In-Reply-To: <CANCZXo4rtkVr-m3p1kyavS6Ruu7Gbwp-qqR9BhEtiZ39+NahvQ@mail.gmail.com>
On 04/09/15 13:19, Alexander Kuleshov wrote:
> 2015-09-04 18:00 GMT+06:00 Suzuki K. Poulose <Suzuki.Poulose@arm.com>:
>> There is generic CPUID feature helper queued for 4.3, which can extract
>> the feature bits
>>
>> cpuid_feature_extract_field(feature, shift)
>>
>> You might want to use it instead. Btw, I have a patch series(waiting for
>> the merge window, before I post), which changes the way we initialise the
>> HWCAP bits.
>
> Hello,
>
> Thanks for feedback first of all. So, I'll wait while your changes will be
> in the mainline kernel and will reconsider the changes.
>
Please find the series here :
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-September/370386.html
Thanks
Suzuki
prev parent reply other threads:[~2015-09-16 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 18:11 [PATCH 1/3] arm64/cpufeature.h: Add macros for a cpu features testing Alexander Kuleshov
2015-09-03 18:12 ` [PATCH 2/3] arm64/setup: Use ID_AA64ISAR0_EL1_.* macros Alexander Kuleshov
2015-09-04 11:26 ` Catalin Marinas
2016-11-07 16:30 ` Suzuki K Poulose
2015-09-03 18:12 ` [PATCH 3/3] arm64/fpsimd: Use ID_AA64PFR0_EL1_.* macros Alexander Kuleshov
2016-11-07 16:31 ` Suzuki K Poulose
2015-09-04 11:25 ` [PATCH 1/3] arm64/cpufeature.h: Add macros for a cpu features testing Catalin Marinas
2015-09-04 12:00 ` Suzuki K. Poulose
2015-09-04 12:19 ` Alexander Kuleshov
2015-09-16 14:48 ` Suzuki K. Poulose [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=55F98129.9080609@arm.com \
--to=suzuki.poulose@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).