From: Philip Li <philip.li@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kernel test robot <lkp@intel.com>, <llvm@lists.linux.dev>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: arch/x86/kernel/cpu/amd.c:1289:6: warning: no previous prototype for function 'amd_check_microcode'
Date: Tue, 29 Aug 2023 13:31:33 +0800 [thread overview]
Message-ID: <ZO2CtepNj3jTAYCF@rli9-mobl> (raw)
In-Reply-To: <20230829044745.GAZO14cRtwAnfERdR9@fat_crate.local>
On Tue, Aug 29, 2023 at 06:47:45AM +0200, Borislav Petkov wrote:
> On Tue, Aug 29, 2023 at 12:07:59PM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 1c59d383390f970b891b503b7f79b63a02db2ec5
>
> It doesn't trigger here:
Sorry Boris for this invalid report to cost your time. We will fix the code
issue asap to understand why this one is sent out when head is good.
>
> $ git describe
> v6.5-1207-g1c59d383390f
>
> $ make ARCH=i386 CC=clang-16 HOSTCC=clang-16 allnoconfig
>
> $ make W=1 ARCH=i386 CC=clang-16 HOSTCC=clang-16 arch/x86/kernel/cpu/
>
> ...
> CC arch/x86/kernel/cpu/intel_pconfig.o
> CC arch/x86/kernel/cpu/tsx.o
> CC arch/x86/kernel/cpu/amd.o
> CC arch/x86/kernel/cpu/hygon.o
> CC arch/x86/kernel/cpu/centaur.o
> ...
>
> > commit: 522b1d69219d8f083173819fde04f994aa051a98 x86/cpu/amd: Add a Zenbleed fix
> > date: 6 weeks ago
>
> Likely an old report.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
prev parent reply other threads:[~2023-08-29 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 4:07 arch/x86/kernel/cpu/amd.c:1289:6: warning: no previous prototype for function 'amd_check_microcode' kernel test robot
2023-08-29 4:47 ` Borislav Petkov
2023-08-29 5:31 ` Philip Li [this message]
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=ZO2CtepNj3jTAYCF@rli9-mobl \
--to=philip.li@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).