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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Nov 2013 00:19:03 +0100
From:	Borislav Petkov <bp@...e.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.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

On Wed, Nov 13, 2013 at 12:10:08AM +0100, Ingo Molnar wrote:
> Hm, that's really weird, I've been using <stable@...nel.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@...r.kernel.org>, but still I'm wondering why
> <stable@...nel.org> seems to be working in practice - maybe Greg
> is picking up such commits as well, not via an email flow but via
> scripting?

I believe I read somewhere him saying that he does. But the
stable@...nel.org thing as an email address doesn't work. I'd guess he
greps commit messages for "stable@" or so...

-- 
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/