mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	x86@kernel.org
Subject: Re: [PATCH -next] x86_32: fix printk formats
Date: Fri, 13 Feb 2009 22:19:26 +0530	[thread overview]
Message-ID: <3f9a31f40902130849k7d9efb50v48a600aa16f41811@mail.gmail.com> (raw)
In-Reply-To: <4995A20A.2060802@oracle.com>

On Fri, Feb 13, 2009 at 10:08 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> Ingo Molnar wrote:
>> * Randy Dunlap <randy.dunlap@oracle.com> wrote:
>>
>>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>>
>>> Fix printk format warnings and also change 2 %ld to %lu for unsigned long
>>> variables.
>>>
>>> arch/x86/mm/init_32.c:727: warning: format '%u' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
>>> arch/x86/mm/init_32.c:735: warning: format '%u' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
>>>
>>> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
>>> ---
>>>  arch/x86/mm/init_32.c |    8 ++++----
>>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> Already fixed in the x86 tree, but thanks.
>
> OK, but this still shows up in linux-next of 20090213.
> Did the fix just miss the today's pull or is there a git #branch issue
> or what?
>

Ahh, because I fixed for :
 arch/x86/mm/init_32.c:696: warning: format '%u' expects type
'unsigned int', but

This part was remaining.

Thanks Randy,
--
JSR

      reply	other threads:[~2009-02-13 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12  8:44 linux-next: Tree for February 12 Stephen Rothwell
2009-02-12 10:42 ` next-20090212: drivers/watchdog/ks8695_wdt.c:68: error: 'CLOCK_TICK_RATE' undeclared (first use in this function) Alexey Dobriyan
2009-02-12 16:44 ` linux-next: Tree for February 12 (ide) Randy Dunlap
2009-02-17 14:19   ` Bartlomiej Zolnierkiewicz
2009-02-18 17:17     ` Randy Dunlap
2009-02-18 18:58       ` Bartlomiej Zolnierkiewicz
2009-02-12 17:38 ` [PATCH] wireless: fix for CONFIG_NL80211=n Randy Dunlap
2009-02-12 18:19 ` [PATCH -next] media/zoran: fix printk format Randy Dunlap
2009-02-12 18:43 ` [PATCH -next] x86_32: fix printk formats Randy Dunlap
2009-02-13  8:25   ` Ingo Molnar
2009-02-13 16:38     ` Randy Dunlap
2009-02-13 16:49       ` Jaswinder Singh Rajput [this message]

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=3f9a31f40902130849k7d9efb50v48a600aa16f41811@mail.gmail.com \
    --to=jaswinderlinux@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=x86@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

all inboxes | Powered by JetHome®