All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] compile warnings due to change of pci resource element type
Date: Fri, 04 Mar 2005 15:49:45 +0000	[thread overview]
Message-ID: <42288399.9060609@osdl.org> (raw)
In-Reply-To: <42287935.30573.366952@localhost>

Stephen Biggs wrote:
> Trying to comple the latest version (2.6.11-rc5-mm1) gives a huge amount 
> of warnings in a lot of files due to printf formats (and a couple of 
> other minor issues) that have %lx instead of %llx for the "start" element 
> in the pci_resource struct whose type was changed from u32 to u64.
> 
> These are relatively easy to fix and need to be fixed because of 
> potential stack issues with var arg functions like printk and friends.
> 
> My question is: should I do this or is someone else working on this, 
> perhaps a better fix than simply changing the majority of occurrences of 
> "%lx" to "%llx"?

I read messages on lkml that the pci resource patch was being dropped
temporarily to fix some issues.... Perhaps its patch submitter will
be fixing those, I dunno.

-- 
~Randy
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  reply	other threads:[~2005-03-04 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 13:05 [KJ] compile warnings due to change of pci resource element type Stephen Biggs
2005-03-04 15:49 ` Randy.Dunlap [this message]
2005-03-04 16:57 ` Greg KH
2005-03-05  9:33 ` Stephen Biggs
2005-03-05 10:07 ` Alexey Dobriyan
2005-03-05 16:04 ` Nish Aravamudan
2005-03-05 17:51 ` Stephen Biggs
2005-03-05 17:54 ` Randy.Dunlap

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=42288399.9060609@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=kernel-janitors@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.