All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Greg KH <greg@kroah.com>
Cc: oe-kbuild-all@lists.linux.dev, Peter Zijlstra <peterz@infradead.org>
Subject: [peterz-queue:core/guards2 19/55] kernel/events/core.c:11388:1: warning: 'static' is not at beginning of declaration
Date: Wed, 26 Jul 2023 22:06:59 +0800	[thread overview]
Message-ID: <202307262155.0Fj30YQG-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git core/guards2
head:   bef4845ab42c7a28ab63629ea1e619cbe51cccad
commit: 251e48298d67e2562346cb08683a6fd470095aec [19/55] perf/core: Fix narrow startup race when creating the perf nr_addr_filters sysfs file
config: arm-randconfig-r046-20230726 (https://download.01.org/0day-ci/archive/20230726/202307262155.0Fj30YQG-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230726/202307262155.0Fj30YQG-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/202307262155.0Fj30YQG-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/events/core.c:11388:1: warning: 'static' is not at beginning of declaration [-Wold-style-declaration]
   11388 | const static struct attribute_group *pmu_dev_groups[] = {
         | ^~~~~


vim +/static +11388 kernel/events/core.c

 11387	
 11388	const static struct attribute_group *pmu_dev_groups[] = {
 11389		&pmu_dev_attr_group,
 11390		NULL,
 11391	};
 11392	

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

                 reply	other threads:[~2023-07-26 14:07 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=202307262155.0Fj30YQG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=greg@kroah.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.