From: Greg KH <greg@kroah.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: resource_size_t and printk()
Date: Tue, 11 Jul 2006 16:15:37 -0700 [thread overview]
Message-ID: <20060711231537.GC18973@kroah.com> (raw)
In-Reply-To: <44AB3DF7.8080107@drzeus.cx>
On Wed, Jul 05, 2006 at 06:20:07AM +0200, Pierre Ossman wrote:
> Greg KH wrote:
> > On Tue, Jul 04, 2006 at 10:54:54PM +0200, Pierre Ossman wrote:
> >
> >> Hi there!
> >>
> >> Your commit b60ba8343b78b182c03cf239d4342785376c1ad1 has been causing me
> >> a bit of confusion and I thought I'd point out the problem so that you
> >> can resolve it. :)
> >>
> >> resource_size_t is not guaranteed to be a long long, but might be a u64
> >> or u32 depending on your .config. So you need an explicit cast in the
> >> printk:s or you get a lot of junk on the output.
> >>
> >
> > That is exactly correct. Is there somewhere in that patch that I forgot
> > to fix this up properly?
> >
> >
>
> In drivers/pnp/interface.c, theres a couple of these:
>
> @@ -264,7 +264,7 @@ static ssize_t pnp_show_current_resource
> if (pnp_port_flags(dev, i) & IORESOURCE_DISABLED)
> pnp_printf(buffer," disabled\n");
> else
> - pnp_printf(buffer," 0x%lx-0x%lx\n",
> + pnp_printf(buffer," 0x%llx-0x%llx\n",
> pnp_port_start(dev, i),
> pnp_port_end(dev, i));
> }
>
Good catch, care to create a patch to fix these?
thanks,
greg k-h
next prev parent reply other threads:[~2006-07-11 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 20:54 resource_size_t and printk() Pierre Ossman
2006-07-04 21:45 ` Greg KH
2006-07-05 4:20 ` Pierre Ossman
2006-07-11 23:15 ` Greg KH [this message]
2006-07-12 8:18 ` Pierre Ossman
2006-07-12 15:15 ` Randy.Dunlap
2006-07-12 15:33 ` Kyle McMartin
2006-07-12 21:37 ` Greg KH
2006-07-12 22:08 ` Alan Cox
2006-07-13 9:35 ` Pierre Ossman
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=20060711231537.GC18973@kroah.com \
--to=greg@kroah.com \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@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.