From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: cpufreq@vger.kernel.org, Dave Jones <davej@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
x86@vger.kernel.org, Len Brown <len.brown@intel.com>,
Mike Travis <travis@sgi.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: [PATCH 0/3] Introduce and use DO_ONCE statement expression macro
Date: Thu, 21 May 2009 16:00:21 -0700 [thread overview]
Message-ID: <cover.1242943463.git.joe@perches.com> (raw)
The printk_once macro in kernel.h is limited to printk
This generalizes the functionality of printk_once and
allows statements like DO_ONCE(pr_info("foo\n"))
and DO_ONCE(initialize(foo));
Joe Perches (3):
kernel.h: Add DO_ONCE statement expression macro
arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c: Use DO_ONCE & spelling fix
kernel.h: Remove unused printk_once
arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c | 4 ++--
include/linux/kernel.h | 27 ++++++++++++---------------
2 files changed, 14 insertions(+), 17 deletions(-)
next reply other threads:[~2009-05-21 23:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 23:00 Joe Perches [this message]
2009-05-21 23:00 ` [PATCH 1/3] kernel.h: Add DO_ONCE statement expression macro Joe Perches
2009-05-21 23:27 ` Randy Dunlap
2009-05-21 23:32 ` Joe Perches
2009-05-21 23:36 ` H. Peter Anvin
2009-05-21 23:41 ` Alan Cox
2009-05-22 0:27 ` Al Viro
2009-05-22 1:09 ` Joe Perches
2009-05-25 6:45 ` Rusty Russell
2009-05-26 2:42 ` Andrew Morton
2009-05-21 23:00 ` [PATCH 2/3] arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c: Use DO_ONCE & spelling fix Joe Perches
2009-05-21 23:26 ` Dave Jones
2009-05-21 23:34 ` Joe Perches
2009-05-21 23:47 ` Dave Jones
2009-05-21 23:52 ` Joe Perches
2009-05-21 23:00 ` [PATCH 3/3] kernel.h: Remove unused printk_once Joe Perches
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=cover.1242943463.git.joe@perches.com \
--to=joe@perches.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=x86@vger.kernel.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).