mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: resource_size_t and printk()
Date: Wed, 12 Jul 2006 08:15:35 -0700	[thread overview]
Message-ID: <20060712081535.296ea579.rdunlap@xenotime.net> (raw)
In-Reply-To: <44B4B041.9050808@drzeus.cx>

On Wed, 12 Jul 2006 10:18:09 +0200 Pierre Ossman wrote:

> Greg KH wrote:
> > Good catch, care to create a patch to fix these?
> >   
> 
> Included.

ugh :(

I know it's more wordy, but we usually use
(unsigned long long), not just (long long).

Wish we had an abbreviation for that.

---
~Randy

  reply	other threads:[~2006-07-12 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 20:54 Pierre Ossman
2006-07-04 21:45 ` 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 [this message]
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=20060712081535.296ea579.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®