From: Borislav Petkov <bp@alien8.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Seunghun Han <kkamagui@gmail.com>,
Tony Luck <tony.luck@intel.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [V3] x86: mce: fix kernel panic when check_interval is changed
Date: Tue, 6 Mar 2018 12:02:08 +0100 [thread overview]
Message-ID: <20180306110207.GC11535@pd.tnic> (raw)
On Tue, Mar 06, 2018 at 02:57:48AM -0800, Greg Kroah-Hartman wrote:
> It would have been nice to add a cc:stable for this, but I'll try to
> watch it and when it hits Linus's tree I'll queue it up there.
I can still add it - it is the top patch and I haven't sent it yet.
/me goes and adds it.
Voila!
:-)
next reply other threads:[~2018-03-06 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 11:02 Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-06 11:46 [V3] x86: mce: fix kernel panic when check_interval is changed Greg Kroah-Hartman
2018-03-06 10:57 Greg Kroah-Hartman
2018-03-06 10:43 Borislav Petkov
2018-03-02 20:27 Seunghun Han
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=20180306110207.GC11535@pd.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=kkamagui@gmail.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).