mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [ardb:jump-label-nop-patching-cleanup-v2 6/6] kernel/jump_label.c:336:13: error: static declaration of 'arch_jump_label_transform_static' follows non-static declaration
Date: Thu, 16 Jun 2022 18:50:21 +0800	[thread overview]
Message-ID: <202206161816.11vbdgXt-lkp@intel.com> (raw)

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git jump-label-nop-patching-cleanup-v2
head:   744ed73c1f97ab081fa753030a27d7fe5865f8c4
commit: 744ed73c1f97ab081fa753030a27d7fe5865f8c4 [6/6] jump_label: make initial NOP patching the special case
config: x86_64-rhel-8.3-syz (https://download.01.org/0day-ci/archive/20220616/202206161816.11vbdgXt-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/commit/?id=744ed73c1f97ab081fa753030a27d7fe5865f8c4
        git remote add ardb git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git
        git fetch --no-tags ardb jump-label-nop-patching-cleanup-v2
        git checkout 744ed73c1f97ab081fa753030a27d7fe5865f8c4
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> kernel/jump_label.c:336:13: error: static declaration of 'arch_jump_label_transform_static' follows non-static declaration
     336 | static void arch_jump_label_transform_static(struct jump_entry *entry,
         |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   In file included from include/linux/dynamic_debug.h:6,
                    from include/linux/printk.h:584,
                    from include/linux/kernel.h:29,
                    from arch/x86/include/asm/percpu.h:27,
                    from arch/x86/include/asm/current.h:6,
                    from include/linux/sched.h:12,
                    from include/linux/ratelimit.h:6,
                    from include/linux/dev_printk.h:16,
                    from include/linux/device.h:15,
                    from include/linux/node.h:18,
                    from include/linux/memory.h:19,
                    from kernel/jump_label.c:9:
   include/linux/jump_label.h:223:13: note: previous declaration of 'arch_jump_label_transform_static' with type 'void(struct jump_entry *, enum jump_label_type)'
     223 | extern void arch_jump_label_transform_static(struct jump_entry *entry,
         |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


vim +/arch_jump_label_transform_static +336 kernel/jump_label.c

   334	
   335	#ifndef arch_jump_label_transform_static
 > 336	static void arch_jump_label_transform_static(struct jump_entry *entry,
   337						     enum jump_label_type type)
   338	{
   339		/* nothing to do on most architectures */
   340	}
   341	#endif
   342	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-06-16 10:51 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=202206161816.11vbdgXt-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ardb@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®