linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: bzolnier@gmail.com, marek.vasut@gmail.com, tiwai@suse.de,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org, ralf@linux-mips.org,
	mark.fasheh@oracle.com, linuxppc-dev@ozlabs.org,
	linux-ide@vger.kernel.org, akpm@linux-foundation.org,
	linux-ext4@vger.kernel.org, dwmw2@infradead.org,
	dan.j.williams@intel.com, mchehab@infradead.org,
	arjan@infradead.org
Subject: Re: powerpc allmodconfig
Date: Thu, 16 Oct 2008 12:49:23 -0700 (PDT)	[thread overview]
Message-ID: <20081016.124923.222595655.davem@davemloft.net> (raw)
In-Reply-To: <1224169039.735.57.camel@johannes.berg>

From: Johannes Berg <johannes@sipsolutions.net>
Date: Thu, 16 Oct 2008 16:57:19 +0200

> On Wed, 2008-10-15 at 22:02 -0700, David Miller wrote:
> > 
> > 
> > > net/sched/sch_generic.c: In function 'dev_watchdog':
> > > net/sched/sch_generic.c:224: warning: unused variable 'drivername'
> > 
> > Sucky, if WARN_ONCE() evaluates to nothing the sprintf() string buffer
> > on the stack looks unused.
> 
> I've complained about this to Arjan before, we actually lose all
> messages passed to WARN() or WARN_ONCE() on platforms that use bug traps
> for warnings too.

Ok I see how that works, yes, it should be fixed.

If the platform defines a __WARN (which powerpc does) the
whole format string and printf args go unevaluated, it's
because of the following sequence in asm-generic/bug.h:

#ifndef __WARN
#ifndef __ASSEMBLY__
extern void warn_on_slowpath(const char *file, const int line);
extern void warn_slowpath(const char *file, const int line,
		const char *fmt, ...) __attribute__((format(printf, 3, 4)));
#define WANT_WARN_ON_SLOWPATH
#endif
#define __WARN() warn_on_slowpath(__FILE__, __LINE__)
#define __WARN_printf(arg...) warn_slowpath(__FILE__, __LINE__, arg)
#else
#define __WARN_printf(arg...) __WARN()
#endif

  reply	other threads:[~2008-10-16 19:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  4:33 powerpc allmodconfig Andrew Morton
2008-10-16  4:56 ` Benjamin Herrenschmidt
2008-10-16 14:38   ` [PATCH] ibm_newemac: Fix new MAL feature handling Josh Boyer
2008-10-17 12:56     ` Arnd Bergmann
2008-10-17 13:09       ` Josh Boyer
2008-10-20 23:43     ` Benjamin Herrenschmidt
2008-10-21  5:17       ` Jeff Garzik
2008-10-16  5:02 ` powerpc allmodconfig David Miller
2008-10-16  5:21   ` Benjamin Herrenschmidt
2008-10-16  6:08   ` Dan Williams
2008-10-16  6:55     ` Brice Goglin
2008-10-16  6:58       ` David Miller
2008-10-16 16:22         ` Jesse Brandeburg
2008-10-16  7:31   ` Geert Uytterhoeven
2008-10-16  7:36     ` David Miller
2008-10-16  7:58       ` Geert Uytterhoeven
2008-10-16  7:53   ` Andreas Schwab
2008-10-16 14:57   ` Johannes Berg
2008-10-16 19:49     ` David Miller [this message]
2008-10-16 20:02       ` Arjan van de Ven
2008-10-18 12:20         ` Johannes Berg
2008-10-17 11:09   ` Ingo Molnar
2008-10-16  5:57 ` Takashi Iwai
2008-10-16  7:38   ` Adrian Bunk
2008-10-16  7:57     ` Takashi Iwai
2008-10-16  8:21       ` Adrian Bunk
2008-10-16  8:43         ` Takashi Iwai
2008-10-16 10:03           ` Adrian Bunk
2008-10-16  9:34 ` Mark Brown

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=20081016.124923.222595655.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=bzolnier@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=marek.vasut@gmail.com \
    --cc=mark.fasheh@oracle.com \
    --cc=mchehab@infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=tiwai@suse.de \
    /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).