From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel•org>,
Frederic Weisbecker <frederic@kernel•org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel•org>,
Boqun Feng <boqun.feng@gmail•com>,
Uladzislau Rezki <urezki@gmail•com>
Cc: Zqiang <qiang.zhang1211@gmail•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warnings after merge of the rcu tree
Date: Fri, 9 Aug 2024 14:26:59 +1000 [thread overview]
Message-ID: <20240809142659.5fee6d52@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Hi all,
After merging the rcu tree, today's linux-next build (htmldocs) produced
these warnings:
kernel/rcu/tasks.h:54: warning: Function parameter or struct member 'index' not described in 'rcu_tasks_percpu'
kernel/rcu/tasks.h:127: warning: Function parameter or struct member 'rtpcp_array' not described in 'rcu_tasks'
Introduced by commit
a79e0e72ffa6 ("rcu-tasks: Fix access non-existent percpu rtpcp variable in rcu_tasks_need_gpcb()")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-08-09 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 4:26 Stephen Rothwell [this message]
2024-08-09 6:18 ` linux-next: build warnings after merge of the rcu tree Z qiang
-- strict thread matches above, loose matches on Subject: below --
2022-11-23 5:32 Stephen Rothwell
2022-11-23 8:19 ` Leizhen (ThunderTown)
2022-11-23 14:27 ` Paul E. McKenney
2020-11-26 6:44 Stephen Rothwell
2020-11-26 15:12 ` Paul E. McKenney
2020-11-26 17:28 ` Uladzislau Rezki
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=20240809142659.5fee6d52@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=boqun.feng@gmail$(echo .)com \
--cc=frederic@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=neeraj.upadhyay@kernel$(echo .)org \
--cc=paulmck@kernel$(echo .)org \
--cc=qiang.zhang1211@gmail$(echo .)com \
--cc=urezki@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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