public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "J.R. Mauro" <jrm8005@gmail.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: -git10 staging build warnings
Date: Tue, 21 Oct 2008 11:32:10 -0700	[thread overview]
Message-ID: <20081021183210.GA13391@kroah.com> (raw)
In-Reply-To: <3aaafc130810211114p785cecabyb94d45096e6c65b5@mail.gmail.com>

On Tue, Oct 21, 2008 at 02:14:58PM -0400, J.R. Mauro wrote:
> On Tue, Oct 21, 2008 at 2:07 PM, Greg KH <greg@kroah.com> wrote:
> > On Tue, Oct 21, 2008 at 10:41:45AM -0700, Randy Dunlap wrote:
> >> i386:
> >>
> >> drivers/staging/sxg/sxg.c:462: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'unsigned int'
> >> drivers/staging/sxg/sxg.c:479: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'unsigned int'
> >> drivers/staging/sxg/sxg.c:540: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'unsigned int'
> >> drivers/staging/sxg/sxg.c:571: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'unsigned int'
> 
> Greg, does this have anything to do with the fix-gcc-warnings patch I
> sent you a while back?

I don't know, I don't see that one in my "to-apply" queue, so either I
missed it, or it's already applied :)

I've now fixed this in my tree, it was a simple change.

thanks,

greg k-h

  reply	other threads:[~2008-10-21 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 17:41 -git10 staging build warnings Randy Dunlap
2008-10-21 18:07 ` Greg KH
2008-10-21 18:14   ` J.R. Mauro
2008-10-21 18:32     ` Greg KH [this message]
2008-10-21 19:00 ` Greg KH

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=20081021183210.GA13391@kroah.com \
    --to=greg@kroah.com \
    --cc=jrm8005@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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