public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
	"H. Peter Anvin" <hpa@zytor•com>,
	Peter Zijlstra <peterz@infradead•org>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Linus <torvalds@linux-foundation•org>,
	Andrew Morton <akpm@linux-foundation•org>
Subject: Re: linux-next: origin tree build warning
Date: Sun, 13 Dec 2009 23:24:03 -0800	[thread overview]
Message-ID: <1260775443.18538.16.camel@Joe-Laptop.home> (raw)
In-Reply-To: <20091214102415.10bdcf24.sfr@canb.auug.org.au>

On Mon, 2009-12-14 at 10:24 +1100, Stephen Rothwell wrote:
> Today's linux-next build (x86_64 allmodconfig) produced this warning:
> 
> arch/x86/mm/mmio-mod.c: In function 'print_pte':
> Caused by commit 3a0340be06a9356eb61f6804107480acbe62c069 ("x86:
> mmio-mod.c: Use pr_fmt").  Was this even build tested?  The patch doesn't
> even match the commit message.

Dunno how that happened, it was tested here
with #define pr_fmt(fmt) "mmiotrace: " fmt

Here's the diff necessary to make it work.

Signed-off-by: Joe Perches <joe@perches•com>

diff --git a/arch/x86/mm/mmio-mod.c b/arch/x86/mm/mmio-mod.c
index 4c765e9..34a3291 100644
--- a/arch/x86/mm/mmio-mod.c
+++ b/arch/x86/mm/mmio-mod.c
@@ -20,7 +20,7 @@
  * Derived from the read-mod example from relay-examples by Tom Zanussi.
  */
 
-#define pr_fmt(fmt) "mmiotrace: "
+#define pr_fmt(fmt) "mmiotrace: " fmt
 
 #define DEBUG 1
 

  reply	other threads:[~2009-12-14  7:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13 23:24 linux-next: origin tree build warning Stephen Rothwell
2009-12-14  7:24 ` Joe Perches [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27  0:09 Stephen Rothwell
2010-01-18  4:05 Stephen Rothwell
2010-01-18  4:14 ` Stephen Rothwell
2010-01-18  4:29   ` Wu, Fengguang
2010-01-18  5:40     ` Stephen Rothwell
2010-01-19  0:12       ` Stephen Rothwell
2010-01-19 21:05         ` Greg KH
2010-01-19 21:11           ` Greg KH
2010-01-19 23:47             ` Stephen Rothwell
     [not found] <20100101112914.41bc5f77.sfr@canb.auug.org.au>
2010-01-01  0:34 ` Linus Torvalds
2010-01-01  1:02   ` Stephen Rothwell
2010-01-01  1:16     ` Rafael J. Wysocki
2009-12-17  0:10 Stephen Rothwell
2009-12-16  3:52 Stephen Rothwell
2009-11-29 23:01 Stephen Rothwell
2009-10-30  3:30 Stephen Rothwell
2009-10-11 23:56 Stephen Rothwell
2009-08-25  0:11 Stephen Rothwell
2009-08-25  2:37 ` David Miller
2009-06-23  0:36 Stephen Rothwell
2009-06-22  1:01 [ofa-general] " Stephen Rothwell
2009-06-22  3:11 ` FUJITA Tomonori
2009-06-19  1:13 Stephen Rothwell
2009-06-19  8:45 ` Kristoffer Ericson
2009-06-19  0:27 Stephen Rothwell
2009-06-19  0:28 ` Stephen Rothwell
2009-06-11  1:27 Stephen Rothwell
2009-04-29  4:49 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=1260775443.18538.16.camel@Joe-Laptop.home \
    --to=joe@perches$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=peterz@infradead$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tglx@linutronix$(echo .)de \
    --cc=torvalds@linux-foundation$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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