public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maksim Davydov <davydov-max@yandex-team.ru>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davydov-max@yandex-team.ru,
	den-plotnikov@yandex-team.ru, tony.luck@intel.com,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, hpa@zytor.com, peterz@infradead.org,
	juri.lelli@redhat.com, vincent.guittot@linaro.org
Subject: Re: [PATCH] x86/split_lock: add split lock counter
Date: Sat, 16 Dec 2023 11:27:36 +0800	[thread overview]
Message-ID: <202312161122.4Y1qkw0S-lkp@intel.com> (raw)
In-Reply-To: <20231215140113.57173-1-davydov-max@yandex-team.ru>

Hi Maksim,

kernel test robot noticed the following build warnings:

[auto build test WARNING on tip/x86/core]
[also build test WARNING on tip/master tip/sched/core linus/master tip/auto-latest v6.7-rc5 next-20231215]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Maksim-Davydov/x86-split_lock-add-split-lock-counter/20231215-220639
base:   tip/x86/core
patch link:    https://lore.kernel.org/r/20231215140113.57173-1-davydov-max%40yandex-team.ru
patch subject: [PATCH] x86/split_lock: add split lock counter
config: um-defconfig (https://download.01.org/0day-ci/archive/20231216/202312161122.4Y1qkw0S-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231216/202312161122.4Y1qkw0S-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/202312161122.4Y1qkw0S-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from fs/proc/base.c:101:
>> arch/x86/include/asm/cpu.h:36:31: warning: 'struct cpuinfo_x86' declared inside parameter list will not be visible outside of this definition or declaration
      36 | int mwait_usable(const struct cpuinfo_x86 *);
         |                               ^~~~~~~~~~~
   arch/x86/include/asm/cpu.h:42:37: warning: 'struct cpuinfo_x86' declared inside parameter list will not be visible outside of this definition or declaration
      42 | extern void __init sld_setup(struct cpuinfo_x86 *c);
         |                                     ^~~~~~~~~~~
   arch/x86/include/asm/cpu.h:85:32: warning: 'struct cpuinfo_x86' declared inside parameter list will not be visible outside of this definition or declaration
      85 | void init_ia32_feat_ctl(struct cpuinfo_x86 *c);
         |                                ^~~~~~~~~~~


vim +36 arch/x86/include/asm/cpu.h

bb6e89df9028b2 Thomas Gleixner        2022-04-15  35  
1c9d16e3591109 Borislav Petkov        2011-02-11 @36  int mwait_usable(const struct cpuinfo_x86 *);
6d652ea1d05639 Jaswinder Singh Rajput 2009-01-07  37  

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

  parent reply	other threads:[~2023-12-16  3:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 14:01 [PATCH] x86/split_lock: add split lock counter Maksim Davydov
2023-12-15 18:16 ` Dave Hansen
2023-12-16 10:56   ` Maksim Davydov
2024-01-02 15:14     ` Dave Hansen
2023-12-16  2:21 ` kernel test robot
2023-12-16  3:27 ` kernel test robot [this message]
2023-12-16  5:59 ` kernel test robot

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=202312161122.4Y1qkw0S-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=davydov-max@yandex-team.ru \
    --cc=den-plotnikov@yandex-team.ru \
    --cc=hpa@zytor.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=vincent.guittot@linaro.org \
    --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