From: kernel test robot <lkp@intel.com>
To: Chun-Hung Tseng <henrybear327@gmail.com>, paulmck@kernel.org
Cc: kbuild-all@lists.01.org, josh@joshtriplett.org,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
jiangshanlai@gmail.com, joel@joelfernandes.org,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
Chun-Hung Tseng <henrybear327@gmail.com>,
Jim Huang <jserv@ccns.ncku.edu.tw>
Subject: Re: [PATCH] rcu: replace _________p1 with __UNIQUE_ID(rcu)
Date: Tue, 14 Sep 2021 06:57:41 +0800 [thread overview]
Message-ID: <202109140643.Ej76cAlN-lkp@intel.com> (raw)
In-Reply-To: <20210912204131.93206-1-henrybear327@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]
Hi Chun-Hung,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on rcu/dev]
[also build test WARNING on v5.15-rc1 next-20210913]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Chun-Hung-Tseng/rcu-replace-_________p1-with-__UNIQUE_ID-rcu/20210913-044418
base: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev
reproduce: make htmldocs
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
include/linux/rcupdate.h:379: warning: expecting prototype for unrcu_pointer(). Prototype was for __unrcu_pointer() instead
vim +379 include/linux/rcupdate.h
53ecfba259f54b Paul E. McKenney 2010-09-13 366
76c8eaafe4f061 Paul E. McKenney 2021-04-21 367 /**
76c8eaafe4f061 Paul E. McKenney 2021-04-21 368 * unrcu_pointer - mark a pointer as not being RCU protected
76c8eaafe4f061 Paul E. McKenney 2021-04-21 369 * @p: pointer needing to lose its __rcu property
76c8eaafe4f061 Paul E. McKenney 2021-04-21 370 *
76c8eaafe4f061 Paul E. McKenney 2021-04-21 371 * Converts @p from an __rcu pointer to a __kernel pointer.
76c8eaafe4f061 Paul E. McKenney 2021-04-21 372 * This allows an __rcu pointer to be used with xchg() and friends.
76c8eaafe4f061 Paul E. McKenney 2021-04-21 373 */
6744ef711df006 Chun-Hung Tseng 2021-09-13 374 #define __unrcu_pointer(p, local) \
76c8eaafe4f061 Paul E. McKenney 2021-04-21 375 ({ \
6744ef711df006 Chun-Hung Tseng 2021-09-13 376 typeof(*p) *local = (typeof(*p) *__force)(p); \
76c8eaafe4f061 Paul E. McKenney 2021-04-21 377 rcu_check_sparse(p, __rcu); \
6744ef711df006 Chun-Hung Tseng 2021-09-13 378 ((typeof(*p) __force __kernel *)(local)); \
76c8eaafe4f061 Paul E. McKenney 2021-04-21 @379 })
6744ef711df006 Chun-Hung Tseng 2021-09-13 380 #define unrcu_pointer(p) __unrcu_pointer(p, __UNIQUE_ID(rcu))
76c8eaafe4f061 Paul E. McKenney 2021-04-21 381
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 8252 bytes --]
next prev parent reply other threads:[~2021-09-13 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 20:41 Chun-Hung Tseng
2021-09-13 22:57 ` kernel test robot [this message]
2021-09-13 23:04 ` Paul E. McKenney
2021-09-13 23:17 ` Paul E. McKenney
2021-09-15 8:42 ` Henry Tseng
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=202109140643.Ej76cAlN-lkp@intel.com \
--to=lkp@intel.com \
--cc=henrybear327@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=jserv@ccns.ncku.edu.tw \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®