Re: [tip:x86/urgent] x86/microcode/amd: Tone down printk(), don' ttreat a missing firmware file as an error

From: Ingo Molnar
Date: Tue Nov 12 2013 - 18:10:21 EST



* Borislav Petkov <bp@xxxxxxx> wrote:

> (fixed stable@vger).
>
> On Tue, Nov 12, 2013 at 11:45:11PM +0100, Borislav Petkov wrote:
> > On Tue, Nov 12, 2013 at 01:58:00PM -0800, tip-bot for Thomas Renninger wrote:
> > > Commit-ID: 11f918d3e2d3861b6931e97b3aa778e4984935aa
> > > Gitweb: http://git.kernel.org/tip/11f918d3e2d3861b6931e97b3aa778e4984935aa
> > > Author: Thomas Renninger <trenn@xxxxxxx>
> > > AuthorDate: Tue, 12 Nov 2013 17:39:43 +0100
> > > Committer: Ingo Molnar <mingo@xxxxxxxxxx>
> > > CommitDate: Tue, 12 Nov 2013 22:03:49 +0100
> > >
> > > x86/microcode/amd: Tone down printk(), don't treat a missing firmware file as an error
> > >
> > > Do it the same way as done in microcode_intel.c: use pr_debug()
> > > for missing firmware files.
> > >
> > > There seem to be CPUs out there for which no microcode update
> > > has been submitted to kernel-firmware repo yet resulting in
> > > scary sounding error messages in dmesg:
> > >
> > > microcode: failed to load file amd-ucode/microcode_amd_fam16h.bin
> > >
> > > Signed-off-by: Thomas Renninger <trenn@xxxxxxx>
> > > Acked-by: Borislav Petkov <bp@xxxxxxx>
> > > Cc: <stable@xxxxxxxxxx>
> >
> > Shouldn't that be <stable@xxxxxxxxxxxxxxx> ?
>
> Yes, it should:
>
> Final-Recipient: rfc822; stable@xxxxxxxxxx
> Action: failed
> Status: 5.0.0
> Diagnostic-Code: X-Postfix; host mail.kernel.org[198.145.19.201] said: 550
> 5.1.1 <stable@xxxxxxxxxx>: Recipient address rejected: User unknown in
> local recipient table (in reply to RCPT TO command)

Hm, that's really weird, I've been using <stable@xxxxxxxxxx> for years and
the commits do get picked up. I also never saw such a mailer failure.

In any case I've changed my pre-cooked alias to <stable@xxxxxxxxxxxxxxx>,
but still I'm wondering why <stable@xxxxxxxxxx> seems to be working in
practice - maybe Greg is picking up such commits as well, not via an email
flow but via scripting?

Thanks,

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/