public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Suzuki.Poulose@arm•com (Suzuki K. Poulose)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] arm64: cpufeature: Fix sign of feature bits
Date: Tue, 26 Jan 2016 11:24:26 +0000	[thread overview]
Message-ID: <56A7576A.5050304@arm.com> (raw)
In-Reply-To: <1453805896-4397-1-git-send-email-suzuki.poulose@arm.com>

On 26/01/16 10:58, Suzuki K Poulose wrote:
> ARM ARM is getting updated with the guidelines on how to treat the
> feature values for their sign. This series fixes the handling of sign
> based on the new update. Also make the capabilities aware of the sign
> of the feature to use the appropriate helper for extracting the values.
>
> See Patch2 for more details on the rules.

This series applies on top of the "Early CPU feature verification"  :

  http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/401727.html

I can send a version based on 4.5-rc1 if this can be picked up for 4.5

Thanks
Suzuki

  parent reply	other threads:[~2016-01-26 11:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 10:58 [PATCH 0/4] arm64: cpufeature: Fix sign of feature bits Suzuki K Poulose
2016-01-26 10:58 ` [PATCH 1/4] arm64: cpufeature: Correct feature register tables Suzuki K Poulose
2016-01-26 10:58 ` [PATCH 2/4] arm64: cpufeature: Fix the sign of feature bits Suzuki K Poulose
2016-01-26 10:58 ` [PATCH 3/4] arm64: capabilities: Handle sign of the feature bit Suzuki K Poulose
2016-01-26 10:58 ` [PATCH 4/4] arm64: Rename cpuid_feature field extract routines Suzuki K Poulose
2016-02-03 14:06   ` Catalin Marinas
2016-02-03 14:16     ` Marc Zyngier
2016-01-26 11:24 ` Suzuki K. Poulose [this message]
2016-02-09 17:24 ` [PATCH 0/4] arm64: cpufeature: Fix sign of feature bits Will Deacon

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=56A7576A.5050304@arm.com \
    --to=suzuki.poulose@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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