From: Matt Turner <mattst88@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [PATCH -mm 3/4] alpha: remove dma_sync_single_range
Date: Wed, 3 Feb 2010 23:06:37 -0500 [thread overview]
Message-ID: <b4198de61002032006t3703baceh9fc9d9f8bd8cc16d@mail.gmail.com> (raw)
In-Reply-To: <1265253206-17744-3-git-send-email-fujita.tomonori@lab.ntt.co.jp>
On Wed, Feb 3, 2010 at 10:13 PM, FUJITA Tomonori
<fujita.tomonori@lab.ntt.co.jp> wrote:
> dma_sync_single_for_cpu/for_device supports a partial sync so there is
> no point to have dma_sync_single_range (also dma_sync_single was
> obsoleted long ago, replaced with dma_sync_single_for_cpu/for_device).
>
> There is no user of dma_sync_single_range() in mainline and only Alpha
> architecture supports dma_sync_single_range(). So it's unlikely that
> someone out of the tree uses it.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Cc: Richard Henderson <rth@twiddle.net>
> Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
> Cc: Matt Turner <mattst88@gmail.com>
> ---
> arch/alpha/include/asm/dma-mapping.h | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/arch/alpha/include/asm/dma-mapping.h b/arch/alpha/include/asm/dma-mapping.h
> index 04eb568..f514ede 100644
> --- a/arch/alpha/include/asm/dma-mapping.h
> +++ b/arch/alpha/include/asm/dma-mapping.h
> @@ -59,7 +59,6 @@ int dma_set_mask(struct device *dev, u64 mask);
>
> #define dma_sync_single_for_cpu(dev, addr, size, dir) ((void)0)
> #define dma_sync_single_for_device(dev, addr, size, dir) ((void)0)
> -#define dma_sync_single_range(dev, addr, off, size, dir) ((void)0)
> #define dma_sync_sg_for_cpu(dev, sg, nents, dir) ((void)0)
> #define dma_sync_sg_for_device(dev, sg, nents, dir) ((void)0)
> #define dma_cache_sync(dev, va, size, dir) ((void)0)
> --
> 1.5.6.5
Acked-by: Matt Turner <mattst88@gmail.com>
Should I vacuum this one up, or should it go in the -mm tree? I don't
guess there's much point in sending Linus pull requests for single
patches.
Matt
next prev parent reply other threads:[~2010-02-04 4:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 3:13 [PATCH -mm 1/4] DMA-API.txt: add dma_sync_single/sg API description FUJITA Tomonori
2010-02-04 3:13 ` [PATCH -mm 2/4] DMA-API.txt: remove dma_sync_single_range description FUJITA Tomonori
2010-02-04 3:21 ` David Miller
2010-02-04 3:13 ` [PATCH -mm 3/4] alpha: remove dma_sync_single_range FUJITA Tomonori
2010-02-04 3:21 ` David Miller
2010-02-04 4:06 ` Matt Turner [this message]
2010-02-04 4:08 ` Andrew Morton
2010-02-04 3:13 ` [PATCH -mm 4/4] um: " FUJITA Tomonori
2010-02-04 3:21 ` David Miller
2010-02-04 3:21 ` [PATCH -mm 1/4] DMA-API.txt: add dma_sync_single/sg API description David Miller
2010-02-04 3:31 ` FUJITA Tomonori
2010-02-04 3:34 ` James Bottomley
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=b4198de61002032006t3703baceh9fc9d9f8bd8cc16d@mail.gmail.com \
--to=mattst88@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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
all inboxes | Powered by JetHome®