From: David Woodhouse <dwmw2@infradead.org>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: Andrew Morton <akpm@zip.com.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org, ralf@uni-koblenz.de
Subject: Re: [patch] printk and dma_addr_t
Date: Fri, 15 Feb 2002 21:51:16 +0000 [thread overview]
Message-ID: <3438.1013809876@redhat.com> (raw)
In-Reply-To: <20020215153717.F1211@altus.drgw.net>
In-Reply-To: <20020215153717.F1211@altus.drgw.net> <20020213.013557.74564240.davem@redhat.com> <E16awZq-0004s4-00@the-village.bc.nu> <3C6A3F66.75D57124@zip.com.au>
hozer@drgw.net said:
> I need something like this for the MTD patch I've got that supports
> 64 bit buswidths on 32 bit machines and needs to printk the data on
> error.
> I found that #define CFI_FMT '%lx' or whatever to be more
> straightforward, and easier to understand.
I got annoyed with the original implementation that turned up in CVS, with
a completely separate printk line #ifdef CFI_WORD_64, and I changed it to
always cast to (long long) before printing. Although I half suspect I'll
end up redoing it again before actually sending it to Linus.
--
dwmw2
next prev parent reply other threads:[~2002-02-15 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 9:20 [patch] printk and dma_addr_t Andrew Morton
2002-02-13 9:40 ` Alan Cox
2002-02-13 9:33 ` Andrew Morton
2002-02-13 9:34 ` Jeff Garzik
2002-02-13 9:38 ` Andrew Morton
2002-02-13 9:35 ` David S. Miller
2002-02-13 10:23 ` Alan Cox
2002-02-13 10:26 ` Andrew Morton
2002-02-15 21:37 ` Troy Benjegerdes
2002-02-15 21:51 ` David Woodhouse [this message]
2002-02-13 11:36 ` David S. Miller
2002-02-13 17:38 ` Richard Gooch
[not found] <0C01A29FBAE24448A792F5C68F5EA47D2172BC@nasdaq.ms.ensim.com>
2002-02-13 19:11 ` Paul Menage
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=3438.1013809876@redhat.com \
--to=dwmw2@infradead.org \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=hozer@drgw.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@uni-koblenz.de \
/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.