From: Jeff Garzik <jgarzik@pobox.com>
To: "David S. Miller" <davem@redhat.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Ion Badulescu <ionut@badula.org>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add new DMA_ADDR_T_SIZE define
Date: Wed, 19 Feb 2003 16:48:17 -0500 [thread overview]
Message-ID: <20030219214817.GD4977@gtf.org> (raw)
In-Reply-To: <1045692372.14268.9.camel@rth.ninka.net>
On Wed, Feb 19, 2003 at 02:06:12PM -0800, David S. Miller wrote:
> On Wed, 2003-02-19 at 09:20, Randy.Dunlap wrote:
> > Does this help with being able to printk() a <dma_addr_t>? How?
> > Always use a cast to (u64) or something else?
>
> One should always cast to long long and use %llx. There is no
> printf format appropriate for a 'u64'.
/me wishes gcc would let the user application define printf formats
for arbitrary [non-struct] user data types...
Jeff
next prev parent reply other threads:[~2003-02-19 21:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 16:26 [PATCH] add new DMA_ADDR_T_SIZE define Ion Badulescu
2003-02-19 17:20 ` Randy.Dunlap
2003-02-19 17:28 ` Ion Badulescu
2003-02-19 22:06 ` David S. Miller
2003-02-19 22:04 ` Ion Badulescu
2003-02-19 22:06 ` David S. Miller
2003-02-19 21:48 ` Jeff Garzik [this message]
2003-02-22 10:06 ` Ingo Oeser
2003-02-19 22:01 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 18:11 James Bottomley
2003-02-19 18:20 ` Ion Badulescu
2003-02-19 22:07 ` David S. Miller
2003-02-19 22:41 ` Ion Badulescu
2003-02-19 22:29 ` David S. Miller
2003-02-19 22:53 ` Ion Badulescu
2003-02-19 22:38 ` David S. Miller
2003-02-23 7:02 Albert Cahalan
2003-02-23 7:00 ` David S. Miller
2003-02-23 7:20 ` Albert Cahalan
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=20030219214817.GD4977@gtf.org \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=ionut@badula.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=torvalds@transmeta.com \
/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