From: Andi Kleen <andi@firstfloor.org>
To: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"arjan@linux.intel.com" <arjan@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"torvalds@osdl.org" <torvalds@osdl.org>,
"akpm@osdl.org" <akpm@osdl.org>
Subject: Re: [PATCH] Eliminate thousands of warnings in WARN_ON with gcc 3.2 build
Date: Thu, 23 Apr 2009 14:18:01 +0200 [thread overview]
Message-ID: <20090423121801.GM13896@one.firstfloor.org> (raw)
In-Reply-To: <20090423115846.GA21823@axis.com>
On Thu, Apr 23, 2009 at 01:58:46PM +0200, Jesper Nilsson wrote:
> >
> > #ifdef WANT_WARN_ON_SLOWPATH
> > -void warn_slowpath(const char *file, int line, const char *fmt, ...)
> > +void warn_slowpath_fmt(const char *file, int line, const char *fmt, ...)
> > {
> > va_list args;
> > char function[KSYM_SYMBOL_LEN];
> > @@ -358,7 +358,7 @@
> > if (board)
> > printk(KERN_WARNING "Hardware name: %s\n", board);
> >
> > - if (fmt) {
> > + if (*fmt) {
>
> Is this completely safe? If somebody is stupid enough to call
> WARN(condition, NULL); this won't work as it did before.
> OTOH, it would still be useless in debugging...
Noone in tree does according to grep. I would also argue
anyone doing that to be really broken.
>
> Acked-by: Jesper Nilsson <jesper.nilsson@axis.com>
Thanks.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-23 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 22:11 [PATCH] Eliminate thousands of warnings in WARN_ON with gcc 3.2 build Andi Kleen
2009-04-23 11:58 ` Jesper Nilsson
2009-04-23 12:18 ` Andi Kleen [this message]
2009-04-23 12:02 ` Johannes Weiner
2009-04-23 12:23 ` Andi Kleen
2009-04-23 14:38 ` Johannes Weiner
2009-04-23 15:10 ` Andi Kleen
2009-04-23 15:07 ` Arjan van de Ven
2009-04-23 15:23 ` Andi Kleen
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=20090423121801.GM13896@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=jesper.nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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