From: Alice Ryhl <aliceryhl@google.com>
To: Hang Shu <m18080292938@163.com>
Cc: ojeda@kernel.org, "Hang Shu" <hangshu847@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: correct documentation comment for rbtree cursor peek_next method
Date: Thu, 6 Nov 2025 11:32:16 +0000 [thread overview]
Message-ID: <aQyHQFYGTodXADNU@google.com> (raw)
In-Reply-To: <20251106112015.214867-1-m18080292938@163.com>
On Thu, Nov 06, 2025 at 11:20:14AM +0000, Hang Shu wrote:
> From: Hang Shu <hangshu847@gmail.com>
>
> The peek_next method's doc comment incorrectly stated it accesses the
> "previous" node when it actually accesses the next node. This commit
> fixes the documentation to accurately reflect the method's behavior.
>
> Signed-off-by: Hang Shu <hangshu847@gmail.com>
Thanks.
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
This should probably have a fixes tag:
Fixes: 98c14e40e07a ("rust: rbtree: add cursor")
Alice
next prev parent reply other threads:[~2025-11-06 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 11:20 [PATCH] rust: correct documentation comment for rbtree cursor peek_next method Hang Shu
2025-11-06 11:32 ` Alice Ryhl [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-07 2:47 Hang Shu
2025-11-07 9:17 ` Alice Ryhl
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=aQyHQFYGTodXADNU@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=hangshu847@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=m18080292938@163.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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