[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131112230138.GL12854@pd.tnic>
Date: Wed, 13 Nov 2013 00:01:38 +0100
From: Borislav Petkov <bp@...e.de>
To: mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, tglx@...utronix.de, trenn@...e.de,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86/microcode/amd: Tone down printk(), don' t
treat a missing firmware file as an error
(fixed stable@...r).
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@...e.de>
> > AuthorDate: Tue, 12 Nov 2013 17:39:43 +0100
> > Committer: Ingo Molnar <mingo@...nel.org>
> > 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@...e.de>
> > Acked-by: Borislav Petkov <bp@...e.de>
> > Cc: <stable@...nel.org>
>
> Shouldn't that be <stable@...r.kernel.org> ?
Yes, it should:
Final-Recipient: rfc822; stable@...nel.org
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host mail.kernel.org[198.145.19.201] said: 550
5.1.1 <stable@...nel.org>: Recipient address rejected: User unknown in
local recipient table (in reply to RCPT TO command)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists