From: Borislav Petkov <bp@suse.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
hpa@zytor.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, tglx@linutronix.de, trenn@suse.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/microcode/amd: Tone down printk(), don' t treat a missing firmware file as an error
Date: Wed, 13 Nov 2013 00:19:03 +0100 [thread overview]
Message-ID: <20131112231903.GN12854@pd.tnic> (raw)
In-Reply-To: <20131112231008.GC30674@gmail.com>
On Wed, Nov 13, 2013 at 12:10:08AM +0100, Ingo Molnar wrote:
> 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?
I believe I read somewhere him saying that he does. But the
stable@kernel.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.
--
next prev parent reply other threads:[~2013-11-12 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1384274383-43510-1-git-send-email-trenn@suse.de>
[not found] ` <tip-11f918d3e2d3861b6931e97b3aa778e4984935aa@git.kernel.org>
[not found] ` <20131112224511.GJ12854@pd.tnic>
2013-11-12 23:01 ` [tip:x86/urgent] x86/microcode/amd: Tone down printk(), don' t treat a missing firmware file as an error Borislav Petkov
2013-11-12 23:10 ` Ingo Molnar
2013-11-12 23:19 ` Borislav Petkov [this message]
2013-11-13 1:09 ` Thomas Renninger
2013-11-13 1:39 ` Ingo Molnar
2013-11-13 2:11 ` Greg Kroah-Hartman
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=20131112231903.GN12854@pd.tnic \
--to=bp@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=trenn@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox