From: Peter Zijlstra <peterz@infradead.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, corbet@lwn.net, jbaron@akamai.com,
Suzuki.Poulose@arm.com
Subject: Re: [PATCH v2 1/2] jump_labels: Allow array initialisers
Date: Tue, 6 Sep 2016 20:50:42 +0200 [thread overview]
Message-ID: <20160906185042.GN10153@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160906181146.GD29382@arm.com>
On Tue, Sep 06, 2016 at 07:11:46PM +0100, Will Deacon wrote:
> On Mon, Sep 05, 2016 at 06:25:47PM +0100, Catalin Marinas wrote:
> > The static key API is currently designed around single variable
> > definitions. There are cases where an array of static keys is desirable,
> > so extend the API to allow this rather than using the internal static
> > key implementation directly.
> >
> > Suggested-by: Dave P Martin <Dave.Martin@arm.com>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Jason Baron <jbaron@akamai.com>
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> > ---
> > Documentation/static-keys.txt | 9 +++++++++
> > include/linux/jump_label.h | 12 ++++++++++++
> > 2 files changed, 21 insertions(+)
>
> This looks pretty straightforward to me, and I'd like to take it via
> the arm64 tree given that your subsequent patch depends on it.
>
> Peter -- are you ok with this?
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2016-09-06 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 17:25 [PATCH v2 0/2] arm64: Use static keys for CPU features Catalin Marinas
2016-09-05 17:25 ` [PATCH v2 1/2] jump_labels: Allow array initialisers Catalin Marinas
2016-09-06 18:11 ` Will Deacon
2016-09-06 18:50 ` Peter Zijlstra [this message]
2016-09-05 17:25 ` [PATCH v2 2/2] arm64: Use static keys for CPU features Catalin Marinas
2016-09-07 16:59 ` Jason Baron
2016-09-08 13:40 ` Catalin Marinas
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=20160906185042.GN10153@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Suzuki.Poulose@arm.com \
--cc=catalin.marinas@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).