From: David Miller <davem@davemloft.net>
To: fujita.tomonori@lab.ntt.co.jp
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
James.Bottomley@suse.de
Subject: Re: [PATCH -mm 2/4] DMA-API.txt: remove dma_sync_single_range description
Date: Wed, 03 Feb 2010 19:21:39 -0800 (PST) [thread overview]
Message-ID: <20100203.192139.95807504.davem@davemloft.net> (raw)
In-Reply-To: <1265253206-17744-2-git-send-email-fujita.tomonori@lab.ntt.co.jp>
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Date: Thu, 4 Feb 2010 12:13:23 +0900
> 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>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2010-02-04 3:21 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 [this message]
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
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=20100203.192139.95807504.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--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
Powered by JetHome