From: jbaron@redhat.com (Jason Baron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3] ARM: add jump label support
Date: Wed, 29 Feb 2012 10:47:04 -0500 [thread overview]
Message-ID: <20120229154704.GA2372@redhat.com> (raw)
In-Reply-To: <20120229152320.GA6337@debian>
On Wed, Feb 29, 2012 at 08:54:06PM +0530, Rabin Vincent wrote:
> On Wed, Feb 15, 2012 at 10:30:44PM +0530, Rabin Vincent wrote:
> > Add the arch-specific code to support jump labels for ARM and Thumb-2.
> >
> > This code will only be activated on compilers that are capable of
> > building it. It has been tested with GCC 4.6 patched with the patch
> > from GCC bug 48637.
> >
> > Cc: Jason Baron <jbaron@redhat.com>
> > Signed-off-by: Rabin Vincent <rabin@rab.in>
> > ---
> ...
> > +static __always_inline bool arch_static_branch(struct jump_label_key *key)
>
> Hmm, there's now a patch in linux-next ("static keys: Introduce 'struct
> static_key', static_key_true()/false() and static_key_slow_[inc|dec]()")
> via the -tip tree which would cause this not to build anymore since
> struct jump_label_key was renamed to struct static_key.
>
> I'm not sure how this could be handled to keep this compiling both in
> the arm tree separately and in linux-next. I guess the easiest is to
> delay this until the next cycle, since it's not applied yet.
hmm...Maybe the rename patches could be pulled into the arm tree
somehow? Waiting a cycle works too...
Thanks,
-Jason
next prev parent reply other threads:[~2012-02-29 15:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 13:35 [PATCHv2 0/6] ARM: jump label support Rabin Vincent
2012-01-28 13:35 ` [PATCHv2 1/6] ARM: ftrace: remove useless memory checks Rabin Vincent
2012-02-20 16:16 ` Russell King - ARM Linux
2012-02-22 14:13 ` Rabin Vincent
2012-02-22 21:28 ` Russell King - ARM Linux
2012-02-24 16:48 ` Rabin Vincent
2012-02-27 11:21 ` Russell King - ARM Linux
2012-01-28 13:35 ` [PATCHv2 2/6] ARM: ftrace: use canonical Thumb-2 wide instruction format Rabin Vincent
2012-01-30 16:54 ` Dave Martin
2012-01-28 13:35 ` [PATCHv2 3/6] ARM: extract out insn generation code from ftrace Rabin Vincent
2012-01-28 13:35 ` [PATCHv2 4/6] ARM: extract out code patch function from kprobes Rabin Vincent
2012-01-30 17:00 ` Dave Martin
2012-02-07 16:07 ` [PATCHv3] " Rabin Vincent
2012-01-31 18:32 ` [PATCHv2 4/6] " Tixy
2012-01-28 13:35 ` [PATCHv2 5/6] jump label: detect %c support for ARM Rabin Vincent
2012-02-07 16:18 ` Rabin Vincent
2012-02-07 18:04 ` Jason Baron
2012-02-20 17:21 ` Russell King - ARM Linux
2012-02-22 13:32 ` Rabin Vincent
2012-01-28 13:35 ` [PATCHv2 6/6] ARM: add jump label support Rabin Vincent
2012-02-15 17:00 ` [PATCHv3] " Rabin Vincent
2012-02-29 15:24 ` Rabin Vincent
2012-02-29 15:47 ` Jason Baron [this message]
2012-01-31 8:23 ` [PATCHv2 0/6] ARM: " Jon Medhurst (Tixy)
2012-01-31 11:11 ` Dave Martin
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=20120229154704.GA2372@redhat.com \
--to=jbaron@redhat.com \
--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).