All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Joe Perches <joe@perches.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
	Dave Jones <davej@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	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: Re: [PATCH 1/3] kernel.h: Add DO_ONCE statement expression macro
Date: Thu, 21 May 2009 16:36:41 -0700	[thread overview]
Message-ID: <4A15E589.2030003@zytor.com> (raw)
In-Reply-To: <1242948762.3373.143.camel@Joe-Laptop.home>

Joe Perches wrote:
> 
> Add a DO_ONCE statement expression analogous to printk_once
> that executes any arbitrary statement exactly once.
> 

If you're truly going to make that guarantee you should use an atomic
test and set.

	-hpa

  reply	other threads:[~2009-05-21 23:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 23:00 [PATCH 0/3] Introduce and use DO_ONCE statement expression macro Joe Perches
2009-05-21 23:00 ` [PATCH 1/3] kernel.h: Add " Joe Perches
2009-05-21 23:27   ` Randy Dunlap
2009-05-21 23:32     ` Joe Perches
2009-05-21 23:36       ` H. Peter Anvin [this message]
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=4A15E589.2030003@zytor.com \
    --to=hpa@zytor.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=gregkh@suse.de \
    --cc=joe@perches.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.