From: Eric Dumazet <eric.dumazet@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: >Re: [RFC] should VM_BUG_ON(cond) really evaluate cond
Date: Sat, 29 Oct 2011 17:43:04 +0200 [thread overview]
Message-ID: <1319902984.2586.35.camel@edumazet-laptop> (raw)
In-Reply-To: <CA+55aFxvcvUopBc-Q6Fp87asTuBohev8Xdm67jcKfy4Z4_BZRg@mail.gmail.com>
Le vendredi 28 octobre 2011 à 07:55 -0700, Linus Torvalds a écrit :
> Maybe we should make it a generic helper macro ("ACCESS_AT_MOST_ONCE()")?
>
> Comments? I think I'm open to tested patches..
>
I am currently travelling, but can do that Monday/Tuesday if nobody
beats me ;)
next prev parent reply other threads:[~2011-10-29 15:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 1:19 [RFC] should VM_BUG_ON(cond) really evaluate cond Eric Dumazet
2011-10-28 1:25 ` Andi Kleen
2011-10-28 1:34 ` Linus Torvalds
2011-10-28 1:44 ` Ben Hutchings
2011-10-28 2:52 ` Eric Dumazet
2011-10-28 3:29 ` Ben Hutchings
2011-10-28 4:43 ` >Re: " Eric Dumazet
2011-10-28 11:37 ` Linus Torvalds
2011-10-28 12:09 ` Eric Dumazet
2011-10-28 12:19 ` Linus Torvalds
2011-10-28 12:40 ` Linus Torvalds
2011-10-28 14:47 ` Eric Dumazet
2011-10-28 14:55 ` Linus Torvalds
2011-10-29 15:43 ` Eric Dumazet [this message]
2011-10-29 17:34 ` Linus Torvalds
2011-10-30 8:52 ` Eric Dumazet
2011-10-30 9:59 ` Andi Kleen
2011-10-30 15:16 ` Eric Dumazet
2011-10-30 17:07 ` Linus Torvalds
2011-10-30 17:41 ` Eric Dumazet
2011-10-30 17:48 ` Linus Torvalds
2011-10-30 17:59 ` Eric Dumazet
2011-10-30 18:09 ` Linus Torvalds
2011-11-02 0:14 ` Eric Dumazet
2011-11-01 4:06 ` Stephen Rothwell
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=1319902984.2586.35.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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