public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, James.Bottomley@suse.de,
	davem@davemloft.net, jbarnes@virtuousgeek.org, arnd@arndb.de
Subject: Re: [PATCH -mm] dma-mapping.h: add the dma_unmap state API
Date: Fri, 12 Feb 2010 20:44:05 -0800	[thread overview]
Message-ID: <20100212204405.a7f45db3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100213114842D.fujita.tomonori@lab.ntt.co.jp>

On Sat, 13 Feb 2010 11:49:09 +0900 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:

> On Fri, 12 Feb 2010 11:51:57 -0800
> Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > > -#ifdef CONFIG_NEED_DMA_MAP_STATE
> > > -#define DECLARE_PCI_UNMAP_ADDR(ADDR_NAME)        dma_addr_t ADDR_NAME;
> > > -#define DECLARE_PCI_UNMAP_LEN(LEN_NAME)          __u32 LEN_NAME;
> > 
> > But we already screwed up the semicolon thing.  If you grep the tree you'll
> > see that about half of the users of this macro added their own semicolon:
> 
> Yeah, I know. PCI-DMA-mapping.txt says:
> 
> NOTE: DO NOT put a semicolon at the end of the DECLARE_*() macro.
> 
> 
> But there are some other DECLARE_ macros that don't have the
> semicolons so users could be easily confused.

yup.  Users already got confused.

> #define DEFINE_DMA_MAP_ADDR(ADDR_NAME) dma_addr_t ADDR_NAME
> 
> looks better?

yes.  People expect to have to put the semicolon in there, so they do.

> 
> > ./drivers/net/cxgb3/sge.c:              DECLARE_PCI_UNMAP_ADDR(addr);
> > ./drivers/net/skge.h:   DECLARE_PCI_UNMAP_ADDR(mapaddr);
> > ./drivers/net/qla3xxx.h:         DECLARE_PCI_UNMAP_ADDR(mapaddr);
> > ./drivers/net/qla3xxx.h:         DECLARE_PCI_UNMAP_ADDR(mapaddr);
> > ./drivers/net/tg3.h:    DECLARE_PCI_UNMAP_ADDR(mapping)
> > 
> > 
> > Perhaps someone will clean all that up sometime.
> 
> I plan to replace these PCI API with the new generic API so I can take
> care of them together.

cool.

  reply	other threads:[~2010-02-13  4:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  6:04 [PATCH -mm] dma-mapping.h: add the dma_unmap state API FUJITA Tomonori
2010-02-12 19:51 ` Andrew Morton
2010-02-13  2:49   ` FUJITA Tomonori
2010-02-13  4:44     ` Andrew Morton [this message]
2010-02-13  6:13       ` FUJITA Tomonori

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=20100212204405.a7f45db3.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=James.Bottomley@suse.de \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jbarnes@virtuousgeek.org \
    --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