From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-5.15-2026-07 14/14] arch/x86/kernel/cpu/amd.c:1280:6: warning: no previous prototype for 'amd_check_microcode'
Date: Thu, 16 Jul 2026 16:58:57 +0800 [thread overview]
Message-ID: <202607161630.Gsq3zELS-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android14-5.15-2026-07
head: d6257262e20fd4430f6e0605ae8a556507eeb90c
commit: be824fdb827dc06f77a31122949fe1bc011e3e1e [14/14] x86/cpu/amd: Add a Zenbleed fix
config: i386-allnoconfig (https://download.01.org/0day-ci/archive/20260716/202607161630.Gsq3zELS-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/20260716/202607161630.Gsq3zELS-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/202607161630.Gsq3zELS-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/cpu/amd.c:1280:6: warning: no previous prototype for 'amd_check_microcode' [-Wmissing-prototypes]
1280 | void amd_check_microcode(void)
| ^~~~~~~~~~~~~~~~~~~
vim +/amd_check_microcode +1280 arch/x86/kernel/cpu/amd.c
1279
> 1280 void amd_check_microcode(void)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-16 8:59 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=202607161630.Gsq3zELS-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.