All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	lkml <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@uni-koblenz.de>
Subject: Re: [patch] printk and dma_addr_t
Date: Wed, 13 Feb 2002 01:38:52 -0800	[thread overview]
Message-ID: <3C6A342C.E2123369@zip.com.au> (raw)
In-Reply-To: <E16avu8-0004lh-00@the-village.bc.nu> <3C6A331A.2D793119@mandrakesoft.com>

Jeff Garzik wrote:
> 
> Alan Cox wrote:
> >
> > > dma_addr_t type.   So the above usage will become
> > >
> > >       printk("stuff: " DMA_ADDR_T_FMT " %s", a, s);
> >
> > Vomit. How about adding a dma_addr_t %code to the printk function ?
> 
> heh, my comment on the patch was, "about as good as you can do without
> teaching printk and gcc about the type"

we could do:

	char *format_dma_addr_t(char *buf, dma_addr_t a);

-

  reply	other threads:[~2002-02-13  9:40 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 [this message]
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
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=3C6A342C.E2123369@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --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.