From: Karl Mehltretter <kmehltretter@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Petr Tesarik <petr@tesarici.cz>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Michael Kelley <mhklinux@outlook.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/7] docs: swiotlb: Fix maximum mapping size helper
Date: Sat, 22 Aug 2026 14:16:48 +0200 [thread overview]
Message-ID: <20260822121651.1559-5-kmehltretter@gmail.com> (raw)
In-Reply-To: <20260822121651.1559-1-kmehltretter@gmail.com>
The DMA helper is named dma_max_mapping_size(), not
dma_map_mapping_size().
Fixes: c93f261dfc39 ("Documentation/core-api: add swiotlb documentation")
Assisted-by: Codex:gpt-5.6-sol
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
Documentation/core-api/swiotlb.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/swiotlb.rst b/Documentation/core-api/swiotlb.rst
index 9e0fe027dd3bd..303999f09ea03 100644
--- a/Documentation/core-api/swiotlb.rst
+++ b/Documentation/core-api/swiotlb.rst
@@ -107,7 +107,7 @@ A single allocation from swiotlb is limited to IO_TLB_SIZE * IO_TLB_SEGSIZE
bytes, which is 256 KiB with current definitions. When a device's DMA settings
are such that the device might use swiotlb, the maximum size of a DMA segment
must be limited to that 256 KiB. This value is communicated to higher-level
-kernel code via dma_map_mapping_size() and swiotlb_max_mapping_size(). If the
+kernel code via dma_max_mapping_size() and swiotlb_max_mapping_size(). If the
higher-level code fails to account for this limit, it may make requests that
are too large for swiotlb, and get a "swiotlb full" error.
--
2.53.0
next prev parent reply other threads:[~2026-08-22 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 12:16 [PATCH 0/7] docs: core-api: Fix stale function names and a broken example Karl Mehltretter
2026-08-22 12:16 ` [PATCH 1/7] docs: cpu_hotplug: Fix multi-instance removal calls Karl Mehltretter
2026-08-22 17:25 ` Randy Dunlap
2026-08-24 16:57 ` Jonathan Corbet
2026-08-24 18:05 ` Karl Mehltretter
2026-08-24 18:28 ` Jonathan Corbet
2026-08-22 12:16 ` [PATCH 2/7] docs: irq-affinity: Restore grep in example Karl Mehltretter
2026-08-22 17:25 ` Randy Dunlap
2026-08-22 12:16 ` [PATCH 3/7] docs: dma-attributes: Fix dma_alloc_attrs() name Karl Mehltretter
2026-08-22 17:25 ` Randy Dunlap
2026-08-24 9:26 ` Marek Szyprowski
2026-08-22 12:16 ` Karl Mehltretter [this message]
2026-08-22 17:26 ` [PATCH 4/7] docs: swiotlb: Fix maximum mapping size helper Randy Dunlap
2026-08-22 12:16 ` [PATCH 5/7] docs: this_cpu_ops: Fix SRCU helper names Karl Mehltretter
2026-08-22 16:39 ` Paul E. McKenney
2026-08-22 17:28 ` Randy Dunlap
[not found] ` <20260822121651.1559-7-kmehltretter@gmail.com>
2026-08-22 12:28 ` [PATCH 6/7] docs: xarray: Fix xas_try_split() name Zi Yan
2026-08-22 17:30 ` Randy Dunlap
[not found] ` <20260822121651.1559-8-kmehltretter@gmail.com>
2026-08-22 17:32 ` [PATCH 7/7] docs: debugobjects: Fix debug_object_init() name Randy Dunlap
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=20260822121651.1559-5-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=petr@tesarici.cz \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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