All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tony Luck <tony.luck@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-ia64@vger.kernel.org
Subject: [aegl:resctrl2_patches 9/52] fs/resctrl2/kernfs.c:6:19: sparse: sparse: symbol 'resctrl_file_ops' was not declared. Should it be static?
Date: Fri, 10 Nov 2023 01:09:27 +0800	[thread overview]
Message-ID: <202311092324.LZXnUp3D-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git resctrl2_patches
head:   a6866c2d6be6dd4997cd46120e288fe0b5e16c9b
commit: eca79ecf33e9c18bcfe7c9c39f2cad22092057ab [9/52] resctrl2: Modules can add file(s) in their info/ directory
config: i386-randconfig-062-20230922 (https://download.01.org/0day-ci/archive/20231109/202311092324.LZXnUp3D-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/20231109/202311092324.LZXnUp3D-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/202311092324.LZXnUp3D-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/resctrl2/kernfs.c:6:19: sparse: sparse: symbol 'resctrl_file_ops' was not declared. Should it be static?

vim +/resctrl_file_ops +6 fs/resctrl2/kernfs.c

     5	
   > 6	struct kernfs_ops resctrl_file_ops = {
     7		.atomic_write_len	= PAGE_SIZE,
     8	};
     9	

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

                 reply	other threads:[~2023-11-09 17:21 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=202311092324.LZXnUp3D-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tony.luck@intel.com \
    /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.