From: Michel Lespinasse <michel@lespinasse.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Michel Lespinasse <walken@google.com>,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH] rbtree: repair some kernel-doc whining
Date: Wed, 2 Jun 2021 13:50:08 -0700 [thread overview]
Message-ID: <20210602205008.GA8615@lespinasse.org> (raw)
In-Reply-To: <20210602062542.8188-1-rdunlap@infradead.org>
On Tue, Jun 01, 2021 at 11:25:42PM -0700, Randy Dunlap wrote:
> Clean up some kernel-doc warnings and use the documented
> Return: notation for function return values.
>
> rbtree_latch.h:64: warning: cannot understand function prototype: 'struct latch_
> tree_ops '
> rbtree.h:343: warning: Function parameter or member 'node' not described in 'rb_
> next_match'
> rbtree.h:343: warning: Excess function parameter 'tree' description in 'rb_next_
> match'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Michel Lespinasse <walken@google.com>
> Cc: Davidlohr Bueso <dbueso@suse.de>
> ---
> include/linux/rbtree.h | 14 +++++++-------
> include/linux/rbtree_latch.h | 2 +-
> 2 files changed, 8 insertions(+), 8 deletions(-)
Looks fine to me, thanks!
Acked-By: Michel Lespinasse <michel@lespinasse.org>
--
Michel "walken" Lespinasse
prev parent reply other threads:[~2021-06-02 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 6:25 [PATCH] rbtree: repair some kernel-doc whining Randy Dunlap
2021-06-02 20:50 ` Michel Lespinasse [this message]
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=20210602205008.GA8615@lespinasse.org \
--to=michel@lespinasse.org \
--cc=dbueso@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=walken@google.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 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.