All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,liam.howlett@oracle.com,andrewjballance@gmail.com,aliceryhl@google.com,akpm@linux-foundation.org
Subject: [to-be-updated] maple_tree-update-mas_next-docs.patch removed from -mm tree
Date: Thu, 12 Feb 2026 12:34:17 -0800	[thread overview]
Message-ID: <20260212203417.F1FAFC4CEF7@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: maple_tree: update mas_next[_range] docs
has been removed from the -mm tree.  Its filename was
     maple_tree-update-mas_next-docs.patch

This patch was dropped because an updated version will be issued

------------------------------------------------------
From: Alice Ryhl <aliceryhl@google.com>
Subject: maple_tree: update mas_next[_range] docs
Date: Sun, 18 Jan 2026 11:00:41 +0000

If you read the docs, it sounds like the difference between these
functions is whether mas->index and mas->last are updated.  However, if
you read the implementation, you will instead find that the difference is
whether NULL entries are skipped.

Link: https://lkml.kernel.org/r/20260118-mas-next-doc-v1-1-827d9f4924ce@google.com
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Cc: Andrew Ballance <andrewjballance@gmail.com>
Cc: Liam Howlett <liam.howlett@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 lib/maple_tree.c |   10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

--- a/lib/maple_tree.c~maple_tree-update-mas_next-docs
+++ a/lib/maple_tree.c
@@ -5060,13 +5060,14 @@ static bool mas_next_setup(struct ma_sta
 }
 
 /**
- * mas_next() - Get the next entry.
+ * mas_next() - Advance the maple state to the next range, skipping zero entries.
  * @mas: The maple state
  * @max: The maximum index to check.
  *
  * Returns the next entry after @mas->index.
+ * Updates @mas->index and @mas->last to the range.
  * Must hold rcu_read_lock or the write lock.
- * Can return the zero entry.
+ * Skips entries reserved with XA_ZERO_ENTRY.
  *
  * Return: The next entry or %NULL
  */
@@ -5083,11 +5084,12 @@ void *mas_next(struct ma_state *mas, uns
 EXPORT_SYMBOL_GPL(mas_next);
 
 /**
- * mas_next_range() - Advance the maple state to the next range
+ * mas_next_range() - Advance the maple state to the next range.
  * @mas: The maple state
  * @max: The maximum index to check.
  *
- * Sets @mas->index and @mas->last to the range.
+ * Returns the next entry after @mas->index.
+ * Updates @mas->index and @mas->last to the range.
  * Must hold rcu_read_lock or the write lock.
  * Can return the zero entry.
  *
_

Patches currently in -mm which might be from aliceryhl@google.com are



                 reply	other threads:[~2026-02-12 20:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260212203417.F1FAFC4CEF7@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=andrewjballance@gmail.com \
    --cc=liam.howlett@oracle.com \
    --cc=mm-commits@vger.kernel.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 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.