From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Suzuki.Poulose@arm.com, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, Jason Baron <jbaron@akamai.com>,
Dave P Martin <Dave.Martin@arm.com>
Subject: Re: [PATCH 1/2] jump_labels: Allow array initialisers
Date: Tue, 30 Aug 2016 10:24:18 +0100 [thread overview]
Message-ID: <20160830092417.GE5163@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1472145992-10660-2-git-send-email-catalin.marinas@arm.com>
On Thu, Aug 25, 2016 at 06:26:31PM +0100, Catalin Marinas wrote:
> diff --git a/Documentation/static-keys.txt b/Documentation/static-keys.txt
> index 477927becacb..fd490f8b1cfa 100644
> --- a/Documentation/static-keys.txt
> +++ b/Documentation/static-keys.txt
> @@ -15,6 +15,8 @@ The updated API replacements are:
>
> DEFINE_STATIC_KEY_TRUE(key);
> DEFINE_STATIC_KEY_FALSE(key);
> +DEFINE_STATIC_KEY_ARRAY_TRUE(keys, count);
> +DEFINE_STATIC_KEY_ARRAY_FALSE(keys, count);
> static_branch_likely()
> static_branch_unlikely()
>
> @@ -140,6 +142,12 @@ static_branch_inc(), will change the branch back to true. Likewise, if the
> key is initialized false, a 'static_branch_inc()', will change the branch to
> true. And then a 'static_branch_dec()', will again make the branch false.
>
> +Where an array of keys is required, it can be defined as:
> +
> + DEFINE_STATIC_KEY_ARRAY_TRUE(keys, count);
> +
> +or:
> + DEFINE_STATIC_KEY_ARRAY_FALSE(keys, count);
Nitpick to myself: for consistency, we need an empty line between "or:"
and "DEFINE_STATIC_KEY_ARRAY_FALSE" (I fixed it locally).
--
Catalin
next prev parent reply other threads:[~2016-08-30 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 17:26 [PATCH 0/2] arm64: Use static keys for CPU features Catalin Marinas
2016-08-25 17:26 ` [PATCH 1/2] jump_labels: Allow array initialisers Catalin Marinas
2016-08-30 9:24 ` Catalin Marinas [this message]
2016-08-25 17:26 ` [PATCH 2/2] arm64: Use static keys for CPU features Catalin Marinas
2016-08-26 9:22 ` Suzuki K Poulose
2016-09-02 15:52 ` Catalin Marinas
2016-09-02 16:07 ` 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=20160830092417.GE5163@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=Dave.Martin@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=corbet@lwn.net \
--cc=jbaron@akamai.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).