All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Puranjay Mohan <puranjay@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Paul E. McKenney" <paulmck@kernel.org>
Subject: [paulmck-rcu:puranjay.2026.06.23a 60/62] Warning: kernel/rcu/tree.c:3636 cannot understand function prototype: '/*  * Racy, memory-ordering-free test of whether the normal or expedited grace  * period recorded in *gsp has completed.  Callers that need the full  * memory-ordering guarantees must ...
Date: Wed, 24 Jun 2026 09:49:27 +0800	[thread overview]
Message-ID: <202606240930.Z4Ut2p23-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git puranjay.2026.06.23a
head:   6daa08cf676d7c1ff53101073fdedbf3a6762370
commit: 790b44c0b205abf2a20f00b880109046b74de583 [60/62] rcu: Detect expedited grace period completion in rcu_pending()
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20260624/202606240930.Z4Ut2p23-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260624/202606240930.Z4Ut2p23-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606240930.Z4Ut2p23-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: kernel/rcu/tree.c:3636 cannot understand function prototype: '/*  * Racy, memory-ordering-free test of whether the normal or expedited grace  * period recorded in *gsp has completed.  Callers that need the full  * memory-ordering guarantees must use poll_state_synchronize_rcu_full();'

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-06-24  1:50 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=202606240930.Z4Ut2p23-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paulmck@kernel.org \
    --cc=puranjay@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.