[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4gUSswBdmda9_=A_Ls-EPh4kH1LewJHZSWKuM5-sHdyUg@mail.gmail.com>
Date: Tue, 29 May 2018 13:17:44 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: Borislav Petkov <bp@...e.de>, "Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>,
"Raj, Ashok" <ashok.raj@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3 V2] x86/mce: Fix incorrect "Machine check from unknown
source" message
On Tue, May 29, 2018 at 11:54 AM, Luck, Tony <tony.luck@...el.com> wrote:
> On Tue, May 29, 2018 at 07:53:14PM +0200, Borislav Petkov wrote:
[..]
> P.S. What happened to my "part 3/3" (updating the Skylake quirk)
> ... does that belong in somebody else's tree?
I have no qualms taking it through the nvdimm tree with the rest of
the pending memcpy_mcsafe() updates. Just need an x86 maintainer ack.
Powered by blists - more mailing lists