All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,tglx@kernel.org,peterz@infradead.org,rdunlap@infradead.org,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] rbtree-fixup-kernel-doc-names.patch removed from -mm tree
Date: Mon, 03 Aug 2026 21:05:53 -0700	[thread overview]
Message-ID: <20260804040553.A135C1F000E9@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: rbtree: fixup kernel-doc names
has been removed from the -mm tree.  Its filename was
     rbtree-fixup-kernel-doc-names.patch

This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Randy Dunlap <rdunlap@infradead.org>
Subject: rbtree: fixup kernel-doc names
Date: Tue, 21 Jul 2026 22:07:59 -0700

Use the correct function parameter name in rb_next_match().  Use the
struct keyword when describing struct latch_tree_ops.

Prevents the following kernel-doc warnings:

Warning: ./include/linux/rbtree.h:510 function parameter 'node' not
 described in 'rb_next_match'
Warning: ./include/linux/rbtree.h:510 Excess function parameter 'tree'
 description in 'rb_next_match'
Warning: ./include/linux/rbtree_latch.h:63 cannot understand function
 prototype: 'struct latch_tree_ops'

Link: https://lore.kernel.org/20260722050759.3892887-1-rdunlap@infradead.org
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 include/linux/rbtree.h       |    2 +-
 include/linux/rbtree_latch.h |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

--- a/include/linux/rbtree.h~rbtree-fixup-kernel-doc-names
+++ a/include/linux/rbtree.h
@@ -500,7 +500,7 @@ rb_find_first(const void *key, const str
 /**
  * rb_next_match() - find the next @key in @tree
  * @key: key to match
- * @tree: tree to search
+ * @node: tree to search
  * @cmp: operator defining node order
  *
  * Returns the next node matching @key, or NULL.
--- a/include/linux/rbtree_latch.h~rbtree-fixup-kernel-doc-names
+++ a/include/linux/rbtree_latch.h
@@ -47,7 +47,7 @@ struct latch_tree_root {
 };
 
 /**
- * latch_tree_ops - operators to define the tree order
+ * struct latch_tree_ops - operators to define the tree order
  * @less: used for insertion; provides the (partial) order between two elements.
  * @comp: used for lookups; provides the order between the search key and an element.
  *
_

Patches currently in -mm which might be from rdunlap@infradead.org are



                 reply	other threads:[~2026-08-04  4:05 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=20260804040553.A135C1F000E9@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=tglx@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.