LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	kernel test robot <lkp@intel.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: oe-kbuild-all@lists.linux.dev, linuxppc-dev@lists.ozlabs.org,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [powerpc:fixes-test 10/12] include/linux/static_call.h:223:9: warning: data definition has no type or storage class
Date: Sat, 11 Jul 2026 18:50:40 +0530	[thread overview]
Message-ID: <8e6869e6-4d7b-4cbe-93f4-d3ee242fea6a@linux.ibm.com> (raw)
In-Reply-To: <621a46b3-74a3-4a1f-b81f-f50ea18a541e@kernel.org>

Hi Christophe,

On 7/11/26 1:10 PM, Christophe Leroy (CS GROUP) wrote:
> 
> 
> Le 11/07/2026 à 03:52, kernel test robot a écrit :
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/ 
>> linux.git fixes-test
>> head:   afc2830892a128a13a65f677271a0a48aeb61b5e
>> commit: 4747e17fe063720a30b1c0075bae3e8f8acd26f4 [10/12] powerpc/32: 
>> Use HAVE_PREEMPT_DYNAMIC_CALL instead of HAVE_PREEMPT_DYNAMIC_KEY
>> config: powerpc-randconfig-001-20260711 (https://download.01.org/0day- 
>> ci/archive/20260711/202607110847.u4TL0RJC-lkp@intel.com/config)
>> compiler: powerpc-linux-gcc (GCC) 11.5.0
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/ 
>> archive/20260711/202607110847.u4TL0RJC-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/202607110847.u4TL0RJC- 
>> lkp@intel.com/
>>
>> All warnings (new ones prefixed by >>):
>>
>>     In file included from include/linux/tracepoint.h:22,
>>                      from include/trace/syscall.h:5,
>>                      from include/linux/syscalls.h:95,
>>                      from include/linux/syscalls_api.h:1,
>>                      from kernel/sched/core.c:16:
>>>> include/linux/static_call.h:223:9: warning: data definition has no 
>>>> type or storage class
>>       223 |         ARCH_ADD_TRAMP_KEY(name)
> 
> Looks like powerpc is missing ARCH_ADD_TRAMP() macro, introduced by 
> commit 73f44fe19d35 ("static_call: Allow module use without exposing 
> static_call_key") for x86. I missed it when adding inline static calls 
> with commit f50b45626e05 ("powerpc/static_call: Implement inline static 
> calls").
> 
> I will have to fix that before we can activate HAVE_PREEMPT_DYNAMIC_CALL.
> 
> Christophe
> 

One more thing to note,

Below series would remove all the EXPORT_STATIC_CALL_TRAMP
instances in scheduler.
That series make sense given that none/voluntary can't be selected now.

https://lore.kernel.org/all/20260703133358.698078-1-mark.rutland@arm.com/


      reply	other threads:[~2026-07-11 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11  1:52 [powerpc:fixes-test 10/12] include/linux/static_call.h:223:9: warning: data definition has no type or storage class kernel test robot
2026-07-11  7:40 ` Christophe Leroy (CS GROUP)
2026-07-11 13:20   ` Shrikanth Hegde [this message]

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=8e6869e6-4d7b-4cbe-93f4-d3ee242fea6a@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lkp@intel.com \
    --cc=maddy@linux.ibm.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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