From: kernel test robot <lkp@intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [reinette:resctrl/controls_rfc_v2 81/88] include/linux/resctrl.h:65:71: warning: declaration of 'struct rdt_resource' will not be visible outside of this function
Date: Wed, 05 Aug 2026 00:50:04 +0800 [thread overview]
Message-ID: <202608050040.qNdyOPko-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/reinette/linux.git resctrl/controls_rfc_v2
head: fbed64f80515241bc6da124585328fd5047a4a13
commit: 0e63339f4b31df77e01c52f8c33f31d2a55008f8 [81/88] fs/resctrl: Introduce iterator for enabled controls
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260805/202608050040.qNdyOPko-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260805/202608050040.qNdyOPko-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/202608050040.qNdyOPko-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/proc/base.c:98:
>> include/linux/resctrl.h:65:71: warning: declaration of 'struct rdt_resource' will not be visible outside of this function [-Wvisibility]
65 | resctrl_enabled_ctrl_iter_next(struct resctrl_ctrl_iter *iter, struct rdt_resource *r);
| ^
1 warning generated.
vim +65 include/linux/resctrl.h
63
64 struct resctrl_ctrl *
> 65 resctrl_enabled_ctrl_iter_next(struct resctrl_ctrl_iter *iter, struct rdt_resource *r);
66
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-04 16: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=202608050040.qNdyOPko-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=reinette.chatre@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.