linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, bzolnier@gmail.com,
	marek.vasut@gmail.com, tiwai@suse.de, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	ralf@linux-mips.org, mark.fasheh@oracle.com,
	linuxppc-dev@ozlabs.org, linux-ide@vger.kernel.org,
	dan.j.williams@intel.com, linux-ext4@vger.kernel.org,
	dwmw2@infradead.org, mchehab@infradead.org
Subject: Re: powerpc allmodconfig
Date: Thu, 16 Oct 2008 16:21:47 +1100	[thread overview]
Message-ID: <1224134507.8157.551.camel@pasglop> (raw)
In-Reply-To: <20081015.220247.262683261.davem@davemloft.net>

On Wed, 2008-10-15 at 22:02 -0700, David Miller wrote:
> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Wed, 15 Oct 2008 21:33:37 -0700
> 
> > kernel/resource.c: In function '__reserve_region_with_split':
> > kernel/resource.c:554: warning: format '%llx' expects type 'long long unsigned int', but argument 3 has type 'resource_size_t'
> > kernel/resource.c:554: warning: format '%llx' expects type 'long long unsigned int', but argument 4 has type 'resource_size_t'
> > kernel/resource.c:554: warning: format '%llx' expects type 'long long unsigned int', but argument 6 has type 'resource_size_t'
> > kernel/resource.c:554: warning: format '%llx' expects type 'long long unsigned int', but argument 7 has type 'resource_size_t'
> 
> Known issue, Ben wants to add a new variant of %pX in order to print resources so that
> resource_size_t vs. unsigned long stuff doesn't matter like this any more.

Actually, I was told Linus had one and I've been trying to dig it out...

Oh well, I may as well dig my own old one.

Cheers,
Ben.



  reply	other threads:[~2008-10-16  5:23 UTC|newest]

Thread overview: 23+ 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  5:02 ` David Miller
2008-10-16  5:21   ` Benjamin Herrenschmidt [this message]
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 14:57   ` Johannes Berg
2008-10-16 19:49     ` David Miller
2008-10-16 20:02       ` Arjan van de Ven
2008-10-18 12:20         ` Johannes Berg
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
2008-10-16  8:43         ` Takashi Iwai
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=1224134507.8157.551.camel@pasglop \
    --to=benh@kernel.crashing.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=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).