From: "Darrick J. Wong" <djwong@kernel.org>
To: Tamir Duberstein <tamird@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] XArray: minor documentation improvements
Date: Wed, 9 Oct 2024 14:25:40 -0700 [thread overview]
Message-ID: <20241009212540.GG21836@frogsfrogsfrogs> (raw)
In-Reply-To: <20241009205237.48881-2-tamird@gmail.com>
On Wed, Oct 09, 2024 at 04:52:38PM -0400, Tamir Duberstein wrote:
> - Replace "they" with "you" where "you" is used in the preceding
> sentence fragment.
> - Use "erasing" rather than "storing `NULL`" when describing multi-index
> entries. Split this into a separate sentence.
> - Add "call" parentheses on "xa_store" for consistency and
> linkification.
>
> Signed-off-by: Tamir Duberstein <tamird@gmail.com>
/me reads about XA_FLAGS_ALLOC and is ok with this now.
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> V1 -> V2: s/use/you/ (Darrick J. Wong)
>
> Documentation/core-api/xarray.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/core-api/xarray.rst b/Documentation/core-api/xarray.rst
> index 77e0ece2b1d6..75c83b37e88f 100644
> --- a/Documentation/core-api/xarray.rst
> +++ b/Documentation/core-api/xarray.rst
> @@ -42,8 +42,8 @@ call xa_tag_pointer() to create an entry with a tag, xa_untag_pointer()
> to turn a tagged entry back into an untagged pointer and xa_pointer_tag()
> to retrieve the tag of an entry. Tagged pointers use the same bits that
> are used to distinguish value entries from normal pointers, so you must
> -decide whether they want to store value entries or tagged pointers in
> -any particular XArray.
> +decide whether you want to store value entries or tagged pointers in any
> +particular XArray.
>
> The XArray does not support storing IS_ERR() pointers as some
> conflict with value entries or internal entries.
> @@ -52,8 +52,8 @@ An unusual feature of the XArray is the ability to create entries which
> occupy a range of indices. Once stored to, looking up any index in
> the range will return the same entry as looking up any other index in
> the range. Storing to any index will store to all of them. Multi-index
> -entries can be explicitly split into smaller entries, or storing ``NULL``
> -into any entry will cause the XArray to forget about the range.
> +entries can be explicitly split into smaller entries. Erasing any entry
> +will cause the XArray to forget about the range.
>
> Normal API
> ==========
> @@ -64,7 +64,7 @@ allocated ones. A freshly-initialised XArray contains a ``NULL``
> pointer at every index.
>
> You can then set entries using xa_store() and get entries
> -using xa_load(). xa_store will overwrite any entry with the
> +using xa_load(). xa_store() will overwrite any entry with the
> new entry and return the previous entry stored at that index. You can
> use xa_erase() instead of calling xa_store() with a
> ``NULL`` entry. There is no difference between an entry that has never
> --
> 2.47.0
>
>
next prev parent reply other threads:[~2024-10-09 21:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 19:36 [PATCH] XArray: minor documentation improvements Tamir Duberstein
2024-10-09 20:44 ` Darrick J. Wong
2024-10-09 20:51 ` Tamir Duberstein
2024-10-09 20:52 ` [PATCH v2] " Tamir Duberstein
2024-10-09 21:25 ` Darrick J. Wong [this message]
2024-10-09 21:59 ` Jonathan Corbet
2024-10-09 22:16 ` Tamir Duberstein
2024-10-09 22:22 ` Randy Dunlap
2024-10-10 14:11 ` Tamir Duberstein
2024-10-10 14:12 ` [PATCH v3] " Tamir Duberstein
2024-10-10 21:34 ` Randy Dunlap
2024-10-10 21:39 ` Tamir Duberstein
2024-10-10 21:41 ` [PATCH v4] " Tamir Duberstein
2024-10-10 21:50 ` Randy Dunlap
2024-10-10 22:41 ` Matthew Wilcox
2024-10-16 12:51 ` Tamir Duberstein
2024-10-24 19:52 ` Tamir Duberstein
2024-10-17 0:34 ` Bagas Sanjaya
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=20241009212540.GG21836@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).