All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Greg KH <greg@kroah.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: resource_size_t and printk()
Date: Tue, 04 Jul 2006 22:54:54 +0200	[thread overview]
Message-ID: <44AAD59E.7010206@drzeus.cx> (raw)

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.

There might be other commits with the same issue. I just noticed this one.

Rgds
Pierre

             reply	other threads:[~2006-07-04 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 20:54 Pierre Ossman [this message]
2006-07-04 21:45 ` resource_size_t and printk() Greg KH
2006-07-05  4:20   ` Pierre Ossman
2006-07-11 23:15     ` Greg KH
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=44AAD59E.7010206@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=greg@kroah.com \
    --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.