All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kuleshov <kuleshovmail@gmail.com>
To: "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
	Will Deacon <Will.Deacon@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] arm64/cpufeature.h: Add macros for a cpu features testing
Date: Fri, 4 Sep 2015 18:19:22 +0600	[thread overview]
Message-ID: <CANCZXo4rtkVr-m3p1kyavS6Ruu7Gbwp-qqR9BhEtiZ39+NahvQ@mail.gmail.com> (raw)
In-Reply-To: <55E987CA.4090302@arm.com>

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.

Thank you.

WARNING: multiple messages have this Message-ID (diff)
From: kuleshovmail@gmail.com (Alexander Kuleshov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64/cpufeature.h: Add macros for a cpu features testing
Date: Fri, 4 Sep 2015 18:19:22 +0600	[thread overview]
Message-ID: <CANCZXo4rtkVr-m3p1kyavS6Ruu7Gbwp-qqR9BhEtiZ39+NahvQ@mail.gmail.com> (raw)
In-Reply-To: <55E987CA.4090302@arm.com>

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.

Thank you.

  reply	other threads:[~2015-09-04 12:19 UTC|newest]

Thread overview: 20+ 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:11 ` Alexander Kuleshov
2015-09-03 18:12 ` [PATCH 2/3] arm64/setup: Use ID_AA64ISAR0_EL1_.* macros Alexander Kuleshov
2015-09-03 18:12   ` Alexander Kuleshov
2015-09-04 11:26   ` Catalin Marinas
2015-09-04 11:26     ` Catalin Marinas
2016-11-07 16:30   ` Suzuki K Poulose
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
2015-09-03 18:12   ` Alexander Kuleshov
2016-11-07 16:31   ` Suzuki K Poulose
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 11:25   ` Catalin Marinas
2015-09-04 12:00 ` Suzuki K. Poulose
2015-09-04 12:00   ` Suzuki K. Poulose
2015-09-04 12:19   ` Alexander Kuleshov [this message]
2015-09-04 12:19     ` Alexander Kuleshov
2015-09-16 14:48     ` Suzuki K. Poulose
2015-09-16 14:48       ` Suzuki K. Poulose

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=CANCZXo4rtkVr-m3p1kyavS6Ruu7Gbwp-qqR9BhEtiZ39+NahvQ@mail.gmail.com \
    --to=kuleshovmail@gmail.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Suzuki.Poulose@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.