linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] arm64: cpufeature: constify and refactor feature array
Date: Wed, 31 Aug 2016 11:31:07 +0100	[thread overview]
Message-ID: <1472639470-28224-1-git-send-email-ard.biesheuvel@linaro.org> (raw)

This is v2 of the series that constifies and refactors the cpufeatures data
structures, in a way that allows certain pieces to be referenced directly by
external code. This was triggered by the discussion around Suzuki's CTR
emulation series [0]

Changes since v1/RFC:
- replace 'if (<cond>) { BUG(); }' with 'BUG_ON(<cond>);' (#2)
- don't dereference NULL return value of bsearch() (#2)
- rename global ctrel0_ftr_reg to arm64_ftr_reg_ctrel0 (#3)
- add Suzuki's R-b (#1, #2, #3)

[0] http://marc.info/?l=linux-arm-kernel&m=147152604303792&w=2

Ard Biesheuvel (3):
  arm64: cpufeature: constify arm64_ftr_bits structures
  arm64: cpufeature: constify arm64_ftr_regs array
  arm64: cpufeature: expose arm64_ftr_reg struct for CTR_EL0

 arch/arm64/include/asm/cpufeature.h | 15 +--
 arch/arm64/kernel/cpufeature.c      | 99 ++++++++++----------
 2 files changed, 58 insertions(+), 56 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-08-31 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 10:31 Ard Biesheuvel [this message]
2016-08-31 10:31 ` [PATCH v2 1/3] arm64: cpufeature: constify arm64_ftr_bits structures Ard Biesheuvel
2016-08-31 10:31 ` [PATCH v2 2/3] arm64: cpufeature: constify arm64_ftr_regs array Ard Biesheuvel
2016-08-31 10:31 ` [PATCH v2 3/3] arm64: cpufeature: expose arm64_ftr_reg struct for CTR_EL0 Ard Biesheuvel

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=1472639470-28224-1-git-send-email-ard.biesheuvel@linaro.org \
    --to=ard.biesheuvel@linaro.org \
    --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).