linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: Hiroshi Doyu <hdoyu@nvidia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [RFC 1/1] driver core: Add dev_*_ratelimited() family
Date: Sat, 12 May 2012 13:32:03 +0200	[thread overview]
Message-ID: <1336822324.14918.9.camel@thorin> (raw)
In-Reply-To: <20120512.135227.1196366807162247040.hdoyu@nvidia.com>

Hi!

On Sam, 2012-05-12 at 12:52 +0200, Hiroshi Doyu wrote:
[...]
> An unclosed "if" statement in the MACRO seems a bit risky, but I don't
> have any better/simple solution for this, ATM. Is there any alternative?

No, the "do { ... } while (0)" is actually the only one and widely used
- not only in the Linux kernel.

[....]

	Bernd
-- 
Bernd Petrovitsch                  Email : bernd@petrovitsch.priv.at
                     LUGA : http://www.luga.at


  reply	other threads:[~2012-05-12 12:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12 10:52 [RFC 1/1] driver core: Add dev_*_ratelimited() family Hiroshi Doyu
2012-05-12 11:32 ` Bernd Petrovitsch [this message]
2012-05-12 15:31 ` Joe Perches
2012-05-14  5:00   ` Hiroshi Doyu
2012-05-14  5:25     ` Joe Perches
2012-05-14  5:40       ` Hiroshi Doyu
2012-05-14  6:05         ` Joe Perches
2012-05-14  7:45           ` Hiroshi Doyu
2012-05-14  7:47             ` [PATCH 1/2] " Hiroshi DOYU
2012-05-14  7:47               ` [PATCH 2/2] memory: tegra{20,30}-mc: Use dev_err_ratelimited() Hiroshi DOYU
2012-05-14 10:07                 ` [v2 1/1] " Hiroshi DOYU
2012-05-14 18:33                   ` Stephen Warren
2012-05-14 18:57                     ` Hiroshi Doyu
2012-05-14 19:09                     ` Greg Kroah-Hartman

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=1336822324.14918.9.camel@thorin \
    --to=bernd@petrovitsch.priv.at \
    --cc=hdoyu@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@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).