From: Arjan van de Ven <arjan@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: johannes@sipsolutions.net, akpm@linux-foundation.org,
dan.j.williams@intel.com, tiwai@suse.de,
linux-ext4@vger.kernel.org, netdev@vger.kernel.org,
linux-ide@vger.kernel.org, bzolnier@gmail.com,
marek.vasut@gmail.com, dwmw2@infradead.org,
mark.fasheh@oracle.com, ralf@linux-mips.org,
mchehab@infradead.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: powerpc allmodconfig
Date: Thu, 16 Oct 2008 13:02:37 -0700 [thread overview]
Message-ID: <20081016130237.4984967c@infradead.org> (raw)
In-Reply-To: <20081016.124923.222595655.davem@davemloft.net>
On Thu, 16 Oct 2008 12:49:23 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> #endif
> #define __WARN() warn_on_slowpath(__FILE__, __LINE__)
> #define __WARN_printf(arg...) warn_slowpath(__FILE__, __LINE__, arg)
> #else
> #define __WARN_printf(arg...) __WARN()
the easiest way I suppose would be to do
#define __WARN_printf(arg..) do { printk(arg); __WARN(); } while (0)
any obvious problems with this ?
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-10-16 20:02 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
[not found] ` <20081015.220247.262683261.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-10-16 5:21 ` Benjamin Herrenschmidt
2008-10-16 14:57 ` Johannes Berg
[not found] ` <1224169039.735.57.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-10-16 19:49 ` David Miller
2008-10-16 20:02 ` Arjan van de Ven [this message]
2008-10-18 12:20 ` Johannes Berg
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-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
[not found] ` <20081016082157.GC23630-re2QNgSbS3j4D6uPqz5PAwR5/fbUUdgG@public.gmane.org>
2008-10-16 8:43 ` Takashi Iwai
[not found] ` <s5hod1lorpm.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
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=20081016130237.4984967c@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--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).