linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: mark.rutland@arm.com, marc.zyngier@arm.com,
	linux-kernel@vger.kernel.org, will.deacon@arm.com,
	catalin.marinas@arm.com, Vadim.Lomovtsev@caviumnetworks.com,
	James Morse <james.morse@arm.com>,
	Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH v3 1/5] arm64: cpufeature: Add scope for capability check
Date: Fri, 22 Apr 2016 12:05:48 +0100	[thread overview]
Message-ID: <571A058C.9000507@arm.com> (raw)
In-Reply-To: <1461250597-16712-2-git-send-email-suzuki.poulose@arm.com>

On 21/04/16 15:56, Suzuki K Poulose wrote:
> Add scope parameter to the arm64_cpu_capabilities::matches(), so that
> this can be reused for checking the capability on a given CPU vs the
> system wide. The system uses the default scope associated with the
> capability for initialising the CPU_HWCAPs and ELF_HWCAPs.
>
> Cc: James Morse <james.morse@arm.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Andre Przywara <andre.przywara@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>

  -71,7 +71,9 @@ DECLARE_BITMAP(cpu_hwcaps, ARM64_NCAPS);
>
>   /* meta feature for alternatives */
>   static bool __maybe_unused
> -cpufeature_pan_not_uao(const struct arm64_cpu_capabilities *entry);
> +cpufeature_pan_not_uao(const struct arm64_cpu_capabilities *entry, int __unused);
> +
> +static u64 __raw_read_system_reg(u32 sys_id);


I missed getting rid of the above forward declaration, will respin the series.

Thanks
Suzuki

  reply	other threads:[~2016-04-22 11:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 14:56 [PATCH v3 0/5] arm64: Fix behavior of maxcpus=n Suzuki K Poulose
2016-04-21 14:56 ` [PATCH v3 1/5] arm64: cpufeature: Add scope for capability check Suzuki K Poulose
2016-04-22 11:05   ` Suzuki K Poulose [this message]
2016-04-21 14:56 ` [PATCH v3 2/5] arm64: Allow a capability to be checked on a single CPU Suzuki K Poulose
2016-04-21 14:56 ` [PATCH v3 3/5] irqchip/gic: Restore CPU interface checking Suzuki K Poulose
2016-04-21 14:56 ` [PATCH v3 4/5] arm64: Verify CPU errata work arounds on hotplugged CPU Suzuki K Poulose
2016-04-21 14:56 ` [PATCH v3 5/5] arm64: Fix behavior of maxcpus=N 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=571A058C.9000507@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=Vadim.Lomovtsev@caviumnetworks.com \
    --cc=andre.przywara@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).