From: Karl Mehltretter <kmehltretter@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>, Zi Yan <ziy@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 6/7] docs: xarray: Fix xas_try_split() name
Date: Sat, 22 Aug 2026 14:16:50 +0200 [thread overview]
Message-ID: <20260822121651.1559-7-kmehltretter@gmail.com> (raw)
In-Reply-To: <20260822121651.1559-1-kmehltretter@gmail.com>
The iterative split helper is xas_try_split(), not
xas_try_alloc().
Fixes: 3fec86f8aa8c ("xarray: add xas_try_split() to split a multi-index entry")
Assisted-by: Codex:gpt-5.6-sol
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
Documentation/core-api/xarray.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/xarray.rst b/Documentation/core-api/xarray.rst
index c6c91cbd0c3ce..3d2b20c05a937 100644
--- a/Documentation/core-api/xarray.rst
+++ b/Documentation/core-api/xarray.rst
@@ -490,7 +490,7 @@ entry at every index to ``NULL`` and dissolve the tie. A multi-index
entry can be split into entries occupying smaller ranges by calling
xas_split_alloc() without the xa_lock held, followed by taking the lock
and calling xas_split() or calling xas_try_split() with xa_lock. The
-difference between xas_split_alloc()+xas_split() and xas_try_alloc() is
+difference between xas_split_alloc()+xas_split() and xas_try_split() is
that xas_split_alloc() + xas_split() split the entry from the original
order to the new order in one shot uniformly, whereas xas_try_split()
iteratively splits the entry containing the index non-uniformly.
--
2.53.0
next prev parent reply other threads:[~2026-08-22 12:17 UTC|newest]
Thread overview: 22+ 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 ` [PATCH 4/7] docs: swiotlb: Fix maximum mapping size helper Karl Mehltretter
2026-08-22 17:26 ` 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
2026-08-22 12:16 ` Karl Mehltretter [this message]
2026-08-22 12:28 ` [PATCH 6/7] docs: xarray: Fix xas_try_split() name Zi Yan
2026-08-22 17:30 ` Randy Dunlap
2026-08-22 12:16 ` [PATCH 7/7] docs: debugobjects: Fix debug_object_init() name Karl Mehltretter
2026-08-22 17:32 ` Randy Dunlap
2026-08-31 21:34 ` [PATCH 0/7] docs: core-api: Fix stale function names and a broken example 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=20260822121651.1559-7-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.