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 11:51:57 -0800 [thread overview]
Message-ID: <20100212115157.02124608.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100212145601W.fujita.tomonori@lab.ntt.co.jp>
On Fri, 12 Feb 2010 15:04:52 +0900
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> Adds the following macros:
>
> DECLARE_DMA_UNMAP_ADDR(ADDR_NAME)
> DECLARE_DMA_UNMAP_LEN(LEN_NAME)
> dma_unmap_addr(PTR, ADDR_NAME)
> dma_unmap_addr_set(PTR, ADDR_NAME, VAL)
> dma_unmap_len(PTR, LEN_NAME)
> dma_unmap_len_set(PTR, LEN_NAME, VAL)
>
> The API corresponds to the pci_unmap state API. We'll move to this new
> generic API from the PCI specific API in the long term. As
> include/asm-generic/pci-dma-compat.h does, the pci_unmap API simply
> calls the new generic API for some time.
>
grumble.
>
> +#ifdef CONFIG_NEED_DMA_MAP_STATE
> +#define DECLARE_DMA_UNMAP_ADDR(ADDR_NAME) dma_addr_t ADDR_NAME;
> +#define DECLARE_DMA_UNMAP_LEN(LEN_NAME) __u32 LEN_NAME;
Adding the semicolons is dopey.
(And these are "definitions", not "declarations" but I'm close to
giving up on that fight).
> +#define dma_unmap_addr(PTR, ADDR_NAME) ((PTR)->ADDR_NAME)
> +#define dma_unmap_addr_set(PTR, ADDR_NAME, VAL) (((PTR)->ADDR_NAME) = (VAL))
> +#define dma_unmap_len(PTR, LEN_NAME) ((PTR)->LEN_NAME)
> +#define dma_unmap_len_set(PTR, LEN_NAME, VAL) (((PTR)->LEN_NAME) = (VAL))
> +#else
> +#define DECLARE_DMA_MAP_ADDR(ADDR_NAME)
> +#define DECLARE_DMA_UNMAP_LEN(LEN_NAME)
> +#define dma_unmap_addr(PTR, ADDR_NAME) (0)
> +#define dma_unmap_addr_set(PTR, ADDR_NAME, VAL) do { } while (0)
> +#define dma_unmap_len(PTR, LEN_NAME) (0)
> +#define dma_unmap_len_set(PTR, LEN_NAME, VAL) do { } while (0)
> +#endif
> +
> #endif
> diff --git a/include/linux/pci-dma.h b/include/linux/pci-dma.h
> index cfd63ab..235a61e 100644
> --- a/include/linux/pci-dma.h
> +++ b/include/linux/pci-dma.h
> @@ -1,20 +1,11 @@
> #ifndef _LINUX_PCI_DMA_H
> #define _LINUX_PCI_DMA_H
>
> -#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:
./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.
next prev parent reply other threads:[~2010-02-12 19:52 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 [this message]
2010-02-13 2:49 ` FUJITA Tomonori
2010-02-13 4:44 ` Andrew Morton
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=20100212115157.02124608.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 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.