From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, GONG Ruiqi <gongruiqi1@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 3098/3098] arch/x86/kernel/cpu/bpf-rvi.c:129:25: warning: no previous prototype for 'bpf_arch_flags'
Date: Tue, 4 Nov 2025 06:45:32 +0800 [thread overview]
Message-ID: <202511040644.p8pfMDIP-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: a29fc03bd0ddaf7388cf31604ef5bd9807585109
commit: c7103b690d364f20ccabd4acc558fa4a4b293364 [3098/3098] bpf: Add bpf_arch_flags kunc for x86
config: x86_64-randconfig-001-20251104 (https://download.01.org/0day-ci/archive/20251104/202511040644.p8pfMDIP-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251104/202511040644.p8pfMDIP-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/202511040644.p8pfMDIP-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/cpu/bpf-rvi.c:129:25: warning: no previous prototype for 'bpf_arch_flags' [-Wmissing-prototypes]
129 | __bpf_kfunc const char *bpf_arch_flags(enum arch_flags_type t, int i)
| ^~~~~~~~~~~~~~
vim +/bpf_arch_flags +129 arch/x86/kernel/cpu/bpf-rvi.c
128
> 129 __bpf_kfunc const char *bpf_arch_flags(enum arch_flags_type t, int i)
130 {
131 switch (t) {
132 case X86_CAP:
133 return x86_cap_flags[i];
134 case X86_BUG:
135 return x86_bug_flags[i];
136 case X86_POWER:
137 return x86_power_flags[i];
138 case X86_POWER_SIZE:
139 return (void *)ARRAY_SIZE(x86_power_flags);
140 default:
141 return NULL;
142 }
143 }
144
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-03 22:46 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=202511040644.p8pfMDIP-lkp@intel.com \
--to=lkp@intel.com \
--cc=gongruiqi1@huawei.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.