All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: lukas.bulwahn@gmail.com
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, tglx@linutronix.de, x86@kernel.org,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [regression] microcode files missing in initramfs imgages from dracut (was Re: [PATCH] x86: Clean up remaining references to CONFIG_MICROCODE_AMD)
Date: Thu, 23 Nov 2023 05:07:47 +0100	[thread overview]
Message-ID: <27dc9607-fed3-4eb2-8c09-d8caf669cc1e@leemhuis.info> (raw)
In-Reply-To: <c67bd324-cec0-4fe4-b3b1-fc1d1e4f2967@leemhuis.info>

[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]

On 12.11.23 16:03, Linux regression tracking (Thorsten Leemhuis) wrote:
> 
>> Commit e6bcfdd75d53 ("x86/microcode: Hide the config knob") removes config
>> MICROCODE_AMD, but left some references that have no effect on any kernel
>> build around.
>>
>> Clean up those remaining config references. No functional change.
>> [...]
> 
> That patch became 4d2b748305e96f ("x86/microcode: Remove remaining
> references to CONFIG_MICROCODE_AMD"). Not totally sure, but from briefly
> looking into things it seems likely that it causes a regression with
> dracut that was just reported here:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=218136

Linus doesn't consider this to be something that needs to be fixed (see
the "from a user perspective things should still continue to work."
later in this thread), so remove this from the tracking:

#regzbot resolve: Linus considers this nothing that needs fixing
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

      parent reply	other threads:[~2023-11-23  4:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 14:12 [PATCH] x86: Clean up remaining references to CONFIG_MICROCODE_AMD Lukas Bulwahn
2023-08-26 12:10 ` [tip: x86/microcode] x86/microcode: Remove " tip-bot2 for Lukas Bulwahn
2023-11-12 15:03 ` [regression] microcode files missing in initramfs imgages from dracut (was Re: [PATCH] x86: Clean up remaining references to CONFIG_MICROCODE_AMD) Linux regression tracking (Thorsten Leemhuis)
2023-11-12 18:10   ` Borislav Petkov
2023-11-22  9:15     ` Linux regression tracking (Thorsten Leemhuis)
2023-11-22 11:58       ` Borislav Petkov
2023-11-22 13:24         ` [PATCH] x86: Add a "x86" ELF note namespace Borislav Petkov
2023-11-22 14:07           ` Borislav Petkov
2023-11-22 15:34         ` [regression] microcode files missing in initramfs imgages from dracut (was Re: [PATCH] x86: Clean up remaining references to CONFIG_MICROCODE_AMD) Linux regression tracking (Thorsten Leemhuis)
2023-11-22 15:57           ` Borislav Petkov
2023-11-22 20:35             ` Linus Torvalds
2023-11-22 20:51               ` Borislav Petkov
2023-11-22 21:08                 ` Linus Torvalds
2023-11-22 21:35                   ` Borislav Petkov
2023-11-23 11:20                   ` Borislav Petkov
2023-11-24  8:49                     ` Antonio Feijoo
2023-11-24 12:15                       ` Borislav Petkov
2023-11-24 13:15                         ` Antonio Feijoo
2023-11-24 13:33                           ` Borislav Petkov
2023-11-28 13:17                             ` Borislav Petkov
2023-11-22 13:45       ` Lukas Bulwahn
2023-11-23  4:07   ` Linux regression tracking #update (Thorsten Leemhuis) [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=27dc9607-fed3-4eb2-8c09-d8caf669cc1e@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mingo@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --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 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.