From: "Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, "Mickaël Salaün" <mic@digikod.net>,
"Jason Wang" <jasowangio@gmail.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>
Subject: [PATCH 4/7] docs: dma-buf-heaps: fix CMA heap name typo
Date: Mon, 31 Aug 2026 11:31:22 -0300 [thread overview]
Message-ID: <20260831143125.151360-5-ivanrwcm25@gmail.com> (raw)
In-Reply-To: <20260831143125.151360-1-ivanrwcm25@gmail.com>
Line 39 used default-cma-region with hyphens; the registered heap name
is default_cma_region, already named correctly at line 26.
Signed-off-by: Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com>
---
Documentation/userspace-api/dma-buf-heaps.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/userspace-api/dma-buf-heaps.rst b/Documentation/userspace-api/dma-buf-heaps.rst
index f56b743cdb36..92099188893e 100644
--- a/Documentation/userspace-api/dma-buf-heaps.rst
+++ b/Documentation/userspace-api/dma-buf-heaps.rst
@@ -36,7 +36,7 @@ following heaps:
- A heap will be created for each reusable region in the device tree
with the ``shared-dma-pool`` compatible, using the full device tree
node name as its name. The buffer semantics are identical to
- ``default-cma-region``.
+ ``default_cma_region``.
Naming Convention
=================
--
2.43.0
next prev parent reply other threads:[~2026-08-31 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 14:31 [PATCH 0/7] docs/abi: align userspace documentation with implementation Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 1/7] docs: futex2: fix documented errno names for futex_waitv Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 2/7] docs: landlock: fix ENOMSG condition in create_ruleset kernel-doc Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 3/7] docs: gpio: note lineinfo padding must be zero filled Iván Ezequiel Rodriguez
2026-09-01 8:24 ` Bartosz Golaszewski
2026-08-31 14:31 ` Iván Ezequiel Rodriguez [this message]
2026-08-31 14:31 ` [PATCH 5/7] docs: vduse: align documentation with current uapi and driver Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 6/7] docs: ioctl: fix stale NVMe registry entry and note N conflict Iván Ezequiel Rodriguez
2026-08-31 14:31 ` [PATCH 7/7] gpio: cdev: return EOPNOTSUPP when HTE is unavailable Iván Ezequiel Rodriguez
2026-09-01 8:25 ` [PATCH 0/7] docs/abi: align userspace documentation with implementation Bartosz Golaszewski
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=20260831143125.151360-5-ivanrwcm25@gmail.com \
--to=ivanrwcm25@gmail.com \
--cc=brgl@kernel.org \
--cc=corbet@lwn.net \
--cc=jasowangio@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=sumit.semwal@linaro.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