From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jason Baron <jbaron@redhat.com>
Subject: Re: [PATCH 5/9] jump label: Add register_jump_label_key/unregister_jump_label_key
Date: Fri, 15 Oct 2010 22:58:10 +0200 [thread overview]
Message-ID: <1287176290.1998.114.camel@laptop> (raw)
In-Reply-To: <20101015201036.923619508@goodmis.org>
On Fri, 2010-10-15 at 16:09 -0400, Steven Rostedt wrote:
>
> static inline void jump_label_lock(void) {}
> static inline void jump_label_unlock(void) {}
> +static inline void register_jump_label_key(unsigned long key) {}
> +static inline void unregister_jump_label_key(unsigned long key) {}
>
shouldn't we call that jump_label_register_key() and co?
next prev parent reply other threads:[~2010-10-15 20:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 20:09 [PATCH 0/9] [GIT PULL] jump label: various updates Steven Rostedt
2010-10-15 20:09 ` [PATCH 1/9] jump label/x86: Move arch_init_ideal_nop5 later Steven Rostedt
2010-10-15 20:09 ` [PATCH 2/9] tracing/x86: No need to disable interrupts when calling arch_init_ideal_nop5 Steven Rostedt
2010-10-15 20:09 ` [PATCH 3/9] jump label: Fix module __init section race Steven Rostedt
2010-10-16 2:09 ` Steven Rostedt
2010-10-16 6:23 ` Ingo Molnar
2010-10-16 16:23 ` Steven Rostedt
2010-10-18 14:14 ` Jason Baron
2010-10-15 20:09 ` [PATCH 4/9] jump label: Fix deadlock b/w jump_label_mutex vs. text_mutex Steven Rostedt
2010-10-15 20:55 ` Peter Zijlstra
2010-10-16 2:16 ` Steven Rostedt
2010-10-16 2:25 ` Steven Rostedt
2010-10-16 4:21 ` Steven Rostedt
2010-10-15 20:09 ` [PATCH 5/9] jump label: Add register_jump_label_key/unregister_jump_label_key Steven Rostedt
2010-10-15 20:58 ` Peter Zijlstra [this message]
2010-10-16 2:11 ` Steven Rostedt
2010-10-15 21:03 ` Peter Zijlstra
2010-10-15 21:09 ` Steven Rostedt
2010-10-15 21:13 ` Peter Zijlstra
2010-10-18 12:05 ` Peter Zijlstra
2010-10-18 14:03 ` Jason Baron
2010-10-18 14:07 ` Peter Zijlstra
2010-10-15 20:09 ` [PATCH 6/9] jump label: Move jump table to r/w section Steven Rostedt
2010-10-15 20:09 ` [PATCH 7/9] jump label: Add docs Steven Rostedt
2010-10-15 20:09 ` [PATCH 8/9] jump label: Make arch_jump_label_text_poke_early() optional Steven Rostedt
2010-10-15 21:06 ` Peter Zijlstra
2010-10-15 21:08 ` Steven Rostedt
2010-10-15 21:22 ` David Daney
2010-10-15 21:35 ` Steven Rostedt
2010-10-15 21:38 ` David Daney
2010-10-16 1:08 ` Steven Rostedt
2010-10-30 10:40 ` [tip:perf/urgent] " tip-bot for Steven Rostedt
2010-10-15 20:09 ` [PATCH 9/9] jump label: Add MIPS support Steven Rostedt
2010-10-15 20:17 ` [PATCH 0/9] [GIT PULL] jump label: various updates Steven Rostedt
2010-10-16 1:10 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2010-10-04 18:56 [PATCH v2 0/2] jump label: Add MIPS architecture support David Daney
2010-10-04 18:56 ` [PATCH v2 1/2] jump label: Make arch_jump_label_text_poke_early() optional David Daney
2010-10-04 18:56 ` [PATCH v2 2/2] jump label: Add MIPS support David Daney
2010-10-06 23:00 ` Ralf Baechle
2010-10-07 1:26 ` David Daney
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=1287176290.1998.114.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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).