public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: paulmck@kernel.org, kernel test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [paulmck-rcu:fastexp.2022.04.01a] BUILD REGRESSION d9f3e7d671416fdf5b61f094765754269b652db0
Date: Mon, 04 Apr 2022 13:40:41 +0530	[thread overview]
Message-ID: <87fsmtmfpa.fsf@linux.ibm.com> (raw)
In-Reply-To: <20220402161148.GK4285@paulmck-ThinkPad-P17-Gen-1>

"Paul E. McKenney" <paulmck@kernel.org> writes:

> On Sat, Apr 02, 2022 at 11:43:01PM +0800, kernel test robot wrote:
>> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git fastexp.2022.04.01a
>> branch HEAD: d9f3e7d671416fdf5b61f094765754269b652db0  EXP rcu: Move expedited grace period (GP) work to RT kthread_worker
>> 
>> Error/Warning reports:
>> 
>> https://lore.kernel.org/lkml/202204021454.WDwBbwVL-lkp@intel.com
>> 
>> Error/Warning: (recently discovered and may have been fixed)
>> 
>> arch/powerpc/include/asm/book3s/64/pgtable-64k.h:60:1: error: no return statement in function returning non-void
>
> Adding Aneesh on CC.  My kneejerk reaction would be to add a
> "return 0" to this function, but there might be a reason why it
> looks like this:

yes, that should work. Do you want me to send a patch for this? Or will
it get folded with other changes?

>
> 	/*
> 	 * This should never get called
> 	 */
> 	static inline int get_hugepd_cache_index(int index)
> 	{
> 		BUG();
> 	}
>
> Working on the other problem with RCU's Kconfig options.
>

-aneesh

  reply	other threads:[~2022-04-04  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02 15:43 [paulmck-rcu:fastexp.2022.04.01a] BUILD REGRESSION d9f3e7d671416fdf5b61f094765754269b652db0 kernel test robot
2022-04-02 16:11 ` Paul E. McKenney
2022-04-04  8:10   ` Aneesh Kumar K.V [this message]
2022-04-04 15:10     ` 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=87fsmtmfpa.fsf@linux.ibm.com \
    --to=aneesh.kumar@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=paulmck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox