From: Randy Dunlap <rdunlap@infradead.org>
To: Petr Tesarik <ptesarik@suse.com>,
Jonathan Corbet <corbet@lwn.net>,
Robin Murphy <robin.murphy@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Bagas Sanjaya <bagasdotme@gmail.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
iommu@lists.linux.dev
Subject: Re: [PATCH v2 2/8] docs: dma-api: replace consistent with coherent
Date: Sat, 28 Jun 2025 11:57:36 -0700 [thread overview]
Message-ID: <eeaf9f80-7b84-4133-a2c2-be2e9c1e97c9@infradead.org> (raw)
In-Reply-To: <20250627101015.1600042-3-ptesarik@suse.com>
On 6/27/25 3:10 AM, Petr Tesarik wrote:
> For consistency, always use the term "coherent" when talking about memory
> that is not subject to CPU caching effects. The term "consistent" is a
> relic of a long-removed PCI DMA API (pci_alloc_consistent() and
> pci_free_consistent() functions).
>
> Signed-off-by: Petr Tesarik <ptesarik@suse.com>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/core-api/dma-api-howto.rst | 36 ++++++++++++------------
> Documentation/core-api/dma-api.rst | 14 ++++-----
> mm/dmapool.c | 6 ++--
> 3 files changed, 28 insertions(+), 28 deletions(-)
--
~Randy
next prev parent reply other threads:[~2025-06-28 18:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250627101022eucas1p2f3715c9c9439ca986217e380d4d3e254@eucas1p2.samsung.com>
2025-06-27 10:10 ` [PATCH v2 0/8] update DMA API documentation Petr Tesarik
2025-06-27 10:10 ` [PATCH v2 1/8] docs: dma-api: use "DMA API" consistently throughout the document Petr Tesarik
2025-06-28 18:56 ` Randy Dunlap
2025-06-27 10:10 ` [PATCH v2 2/8] docs: dma-api: replace consistent with coherent Petr Tesarik
2025-06-28 18:57 ` Randy Dunlap [this message]
2025-06-27 10:10 ` [PATCH v2 3/8] docs: dma-api: remove remnants of PCI DMA API Petr Tesarik
2025-06-28 18:58 ` Randy Dunlap
2025-06-27 10:10 ` [PATCH v2 4/8] docs: dma-api: add a kernel-doc comment for dma_pool_zalloc() Petr Tesarik
2025-06-28 19:04 ` Randy Dunlap
2025-07-01 11:38 ` Petr Tesarik
2025-07-01 12:54 ` Jonathan Corbet
2025-07-01 15:46 ` Petr Tesarik
2025-06-27 10:10 ` [PATCH v2 5/8] docs: dma-api: remove duplicate description of the DMA pool API Petr Tesarik
2025-06-28 19:01 ` Randy Dunlap
2025-06-27 10:10 ` [PATCH v2 6/8] docs: dma-api: clarify DMA addressing limitations Petr Tesarik
2025-06-28 18:58 ` Randy Dunlap
2025-06-27 10:10 ` [PATCH v2 7/8] docs: dma-api: update streaming DMA physical address constraints Petr Tesarik
2025-06-28 18:59 ` Randy Dunlap
2025-06-30 1:32 ` Bagas Sanjaya
2025-06-27 10:10 ` [PATCH v2 8/8] docs: dma-api: clean up documentation of dma_map_sg() Petr Tesarik
2025-06-28 19:00 ` Randy Dunlap
2025-06-27 17:03 ` [PATCH v2 0/8] update DMA API documentation Marek Szyprowski
2025-07-01 19:53 ` Jonathan Corbet
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=eeaf9f80-7b84-4133-a2c2-be2e9c1e97c9@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=iommu@lists.linux.dev \
--cc=kbusch@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=ptesarik@suse.com \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).