mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Borislav Petkov (AMD)" <bp@alien8.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	x86@kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Nikolay Borisov <nik.borisov@suse.com>
Subject: [tip:x86/bugs 2/4] drivers/base/cpu.c:512:9: warning: no previous prototype for 'cpu_show_not_affected'
Date: Thu, 10 Aug 2023 19:12:39 +0800	[thread overview]
Message-ID: <202308101956.oRj1ls7s-lkp@intel.com> (raw)

Hi Borislav,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/bugs
head:   cbe8ded48b939b9d55d2c5589ab56caa7b530709
commit: 0fddfe338210aa018137c03030c581f5ea4be282 [2/4] driver core: cpu: Unify redundant silly stubs
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20230810/202308101956.oRj1ls7s-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230810/202308101956.oRj1ls7s-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/202308101956.oRj1ls7s-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/base/cpu.c:512:9: warning: no previous prototype for 'cpu_show_not_affected' [-Wmissing-prototypes]
     512 | ssize_t cpu_show_not_affected(struct device *dev,
         |         ^~~~~~~~~~~~~~~~~~~~~
   drivers/base/cpu.c:537:16: warning: no previous prototype for 'cpu_show_gds' [-Wmissing-prototypes]
     537 | ssize_t __weak cpu_show_gds(struct device *dev,
         |                ^~~~~~~~~~~~


vim +/cpu_show_not_affected +512 drivers/base/cpu.c

   510	
   511	#ifdef CONFIG_GENERIC_CPU_VULNERABILITIES
 > 512	ssize_t cpu_show_not_affected(struct device *dev,
   513				      struct device_attribute *attr, char *buf)
   514	{
   515		return sysfs_emit(buf, "Not affected\n");
   516	}
   517	

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

             reply	other threads:[~2023-08-10 11:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 11:12 kernel test robot [this message]
2023-08-10 11:34 ` [tip: x86/bugs] driver core: cpu: Make cpu_show_not_affected() static tip-bot2 for Borislav Petkov (AMD)

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=202308101956.oRj1ls7s-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nik.borisov@suse.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=x86@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®