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

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Wed, Nov 13, 2013 at 12:10:08AM +0100, Ingo Molnar wrote:
> 
> * Borislav Petkov <bp@suse.de> 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@suse.de>
> > > > AuthorDate: Tue, 12 Nov 2013 17:39:43 +0100
> > > > Committer:  Ingo Molnar <mingo@kernel.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@suse.de>
> > > > Acked-by: Borislav Petkov <bp@suse.de>
> > > > Cc: <stable@kernel.org>
> > > 
> > > Shouldn't that be <stable@vger.kernel.org> ?
> > 
> > Yes, it should:
> > 
> > Final-Recipient: rfc822; stable@kernel.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@kernel.org>: 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@kernel.org> 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@vger.kernel.org>, 
> but still I'm wondering why <stable@kernel.org> seems to be working in 
> practice - maybe Greg is picking up such commits as well, not via an email 
> flow but via scripting?

Yes, my scripts pick up both, as this is a very common mistake (the
address did change after kernel.org got rebuilt, so you were right in
remembering this as the original address to use.)

So no worries, I can handle both.

thanks,

greg k-h