From: Andrew Morton <akpm@linux-foundation.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, tony.luck@intel.com,
linux-ia64@vger.kernel.org, arnd@arndb.de, joerg.roedel@amd.com
Subject: Re: [PATCH -tip 2/5] x86: use asm-generic/dma-mapping-common.h
Date: Thu, 28 May 2009 00:20:32 -0700 [thread overview]
Message-ID: <20090528002032.737f3e67.akpm@linux-foundation.org> (raw)
In-Reply-To: <1242359705-2117-3-git-send-email-fujita.tomonori@lab.ntt.co.jp>
On Fri, 15 May 2009 12:55:02 +0900 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Acked-by: Joerg Roedel <joerg.roedel@amd.com>
>
> ...
>
> /* Make sure we keep the same behaviour */
> static inline int dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
> {
> @@ -53,178 +55,6 @@ extern int dma_set_mask(struct device *dev, u64 mask);
> extern void *dma_generic_alloc_coherent(struct device *dev, size_t size,
> dma_addr_t *dma_addr, gfp_t flag);
>
> -static inline dma_addr_t
> -dma_map_single(struct device *hwdev, void *ptr, size_t size,
> - enum dma_data_direction dir)
> -{
> - struct dma_map_ops *ops = get_dma_ops(hwdev);
> - dma_addr_t addr;
> -
> - kmemcheck_mark_initialized(ptr, size);
This patch attempts to delete kmemcheck stuff which isn't presently in
linux-next.
So I went ahead and ported the patch, but it'll break if/when kmemcheck
returns.
next prev parent reply other threads:[~2009-05-28 7:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 3:55 [PATCH -tip v2 0/5] add common functions for struct dma_map_ops FUJITA Tomonori
2009-05-15 3:55 ` [PATCH -tip 1/5] add asm-generic/dma-mappig-common.h FUJITA Tomonori
2009-05-15 12:05 ` Arnd Bergmann
2009-05-15 3:55 ` [PATCH -tip 2/5] x86: use asm-generic/dma-mapping-common.h FUJITA Tomonori
2009-05-28 7:20 ` Andrew Morton [this message]
2009-05-28 7:44 ` FUJITA Tomonori
2009-05-15 3:55 ` [PATCH -tip 3/5] ia64: " FUJITA Tomonori
2009-05-15 3:55 ` [PATCH -tip 4/5] ia64: add CONFIG_DMA_API_DEBUG support FUJITA Tomonori
2009-05-15 3:55 ` [PATCH -tip 5/5] dma-debug: fix compiler warnings on IA64 FUJITA Tomonori
2009-05-22 10:54 ` [PATCH -tip v2 0/5] add common functions for struct dma_map_ops FUJITA Tomonori
2009-05-22 10:56 ` Joerg Roedel
2009-05-22 11:17 ` FUJITA Tomonori
2009-05-28 7:20 ` Andrew Morton
2009-05-28 7:44 ` FUJITA Tomonori
2009-05-28 8:58 ` Ingo Molnar
2009-05-28 21:37 ` Luck, Tony
2009-05-28 22:57 ` FUJITA Tomonori
[not found] <20090620155605.GD12901@elte.hu>
[not found] ` <20090622135717T.fujita.tomonori@lab.ntt.co.jp>
[not found] ` <1245650501.18751.0.camel@penberg-laptop>
[not found] ` <20090622203333U.fujita.tomonori@lab.ntt.co.jp>
[not found] ` <19f34abd0906220459w39271e29x99d578d0a49d593b@mail.gmail.com>
[not found] ` <19f34abd0906220543v64b5418di8b97d36214d093cc@mail.gmail.com>
[not found] ` <20090622124916.GA30553@elte.hu>
[not found] ` <1245676212.15580.68.camel@pc1117.cambridge.arm.com>
2009-06-22 13:22 ` [PATCH -tip 2/5] x86: use asm-generic/dma-mapping-common.h Pekka Enberg
2009-06-22 15:24 ` Catalin Marinas
2009-06-22 16:13 ` Pekka Enberg
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=20090528002032.737f3e67.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=joerg.roedel@amd.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.com \
/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