public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: "David S. Miller" <davem@redhat.com>
Cc: albert@users.sourceforge.net, linux-kernel@vger.kernel.org,
	rddunlap@osdl.org
Subject: Re: [PATCH] add new DMA_ADDR_T_SIZE define
Date: 23 Feb 2003 02:20:56 -0500	[thread overview]
Message-ID: <1045984856.32116.14.camel@cube> (raw)
In-Reply-To: <20030222.230008.08415849.davem@redhat.com>

On Sun, 2003-02-23 at 02:00, David S. Miller wrote:
>    From: Albert Cahalan <albert@users.sourceforge.net>
>    Date: 23 Feb 2003 02:02:01 -0500
>    
>    Casts are ugly and they hide bugs. There is a fix
>    for this problem: make u64 be "unsigned long long"
>    for every arch. That works for both 32-bit and 64-bit
>    systems. Likewise, choose "unsigned" for u32 even
>    if an "unsigned long" would work for a given arch.
>    
> That merely hides the lack of user defined printf types
> in gcc, it doesn't make the real problem go away.
> What you suggest is merely a bandaid.

Sure. It's an obviously useful bandaid that works
with gcc 2.91, 2.92, 2.95, 2.96, 3.0, 3.2, 3.3, etc.



  reply	other threads:[~2003-02-23  7:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-23  7:02 [PATCH] add new DMA_ADDR_T_SIZE define Albert Cahalan
2003-02-23  7:00 ` David S. Miller
2003-02-23  7:20   ` Albert Cahalan [this message]
  -- 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-19 16:26 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
2003-02-22 10:06       ` Ingo Oeser
2003-02-19 22:01 ` David S. Miller

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=1045984856.32116.14.camel@cube \
    --to=albert@users.sf.net \
    --cc=albert@users.sourceforge.net \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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