From: Uladzislau Rezki <urezki@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"Uladzislau Rezki (Sony)" <urezki@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the rcu tree
Date: Thu, 26 Nov 2020 18:28:03 +0100 [thread overview]
Message-ID: <20201126172803.GA16234@pc636> (raw)
In-Reply-To: <20201126151240.GP1437@paulmck-ThinkPad-P72>
> On Thu, Nov 26, 2020 at 05:44:28PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the rcu tree, today's linux-next build (htmldocs) produced
> > these warnings:
> >
> > include/linux/rcupdate.h:872: warning: Excess function parameter 'ptr' description in 'kfree_rcu'
> > include/linux/rcupdate.h:872: warning: Excess function parameter 'rhf' description in 'kfree_rcu'
> >
> > Introduced by commit
> >
> > beba8bdf2f16 ("rcu: Introduce kfree_rcu() single-argument macro")
>
> Heh! The documentation isn't dealing at all well with this situation.
>
> Would one of the docbook experts have some advice, keeping in mind
> that kfree_rcu might have either one or two arguments?
>
Indeed. The question is if the docbook is capable of describing such
macro usage, 1 or 2 args.
--
Vlad Rezki
next prev parent reply other threads:[~2020-11-26 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 6:44 linux-next: build warnings after merge of the rcu tree Stephen Rothwell
2020-11-26 15:12 ` Paul E. McKenney
2020-11-26 17:28 ` Uladzislau Rezki [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-09 4:26 Stephen Rothwell
2024-08-09 6:18 ` Z qiang
2022-11-23 5:32 Stephen Rothwell
2022-11-23 8:19 ` Leizhen (ThunderTown)
2022-11-23 14:27 ` Paul E. McKenney
2020-11-10 6:59 Stephen Rothwell
2020-11-10 15:21 ` Paul E. McKenney
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=20201126172803.GA16234@pc636 \
--to=urezki@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.