linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	X86 ML <x86@kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: linux-next: Tree for May 18 (arch/x86/kernel/cpu/microcode/intel.o)
Date: Wed, 18 May 2022 14:05:28 -0700	[thread overview]
Message-ID: <8ead0da9-9545-b10d-e3db-7df1a1f219e4@infradead.org> (raw)
In-Reply-To: <20220518202934.730a8aba@canb.auug.org.au>



On 5/18/22 03:29, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20220517:
> 

on x86_64:

CONFIG_PROCESSOR_SELECT=y
# CONFIG_CPU_SUP_INTEL is not set   <<<<<
CONFIG_CPU_SUP_AMD=y
# CONFIG_CPU_SUP_HYGON is not set
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_CPU_SUP_ZHAOXIN=y

CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y   <<<<<
CONFIG_MICROCODE_AMD=y

causes:

ld: ld: DWARF error: could not find abbrev number 71
arch/x86/kernel/cpu/microcode/intel.o: in function `__load_ucode_intel':
intel.c:(.text+0xe9b): undefined reference to `intel_cpu_collect_info'
ld: arch/x86/kernel/cpu/microcode/intel.o: in function `reload_ucode_intel':
intel.c:(.text+0x130d): undefined reference to `intel_cpu_collect_info'
ld: arch/x86/kernel/cpu/microcode/intel.o: in function `save_microcode_in_initrd_intel':
intel.c:(.init.text+0x108): undefined reference to `intel_cpu_collect_info'
ld: ld: DWARF error: could not find abbrev number 609515
drivers/platform/x86/intel/ifs/load.o: in function `ifs_load_firmware':
load.c:(.text+0x479): undefined reference to `intel_cpu_collect_info'


-- 
~Randy

  reply	other threads:[~2022-05-18 21:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 10:29 linux-next: Tree for May 18 Stephen Rothwell
2022-05-18 21:05 ` Randy Dunlap [this message]
2022-05-18 21:34   ` linux-next: Tree for May 18 (arch/x86/kernel/cpu/microcode/intel.o) Borislav Petkov
2022-05-18 21:54     ` Randy Dunlap
2022-05-18 22:29       ` Borislav Petkov
2022-05-18 22:40         ` Randy Dunlap
2022-05-19 14:55           ` Borislav Petkov
2022-05-19 14:57             ` [PATCH] platform/x86/intel/ifs: Add CPU_SUP_INTEL dependency Borislav Petkov
2022-05-19 17:47               ` Hans de Goede
2022-05-19 15:03             ` [PATCH] x86/microcode: Add explicit CPU vendor dependency Borislav Petkov

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=8ead0da9-9545-b10d-e3db-7df1a1f219e4@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=x86@kernel.org \
    /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).