From: Borislav Petkov <bp@alien8.de>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
linux-edac <linux-edac@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tony Luck <tony.luck@intel.com>, x86-ml <x86@kernel.org>
Subject: Re: [tip: ras/core] x86/mce/AMD: Allow Reserved types to be overwritten in smca_banks[]
Date: Tue, 17 Dec 2019 11:01:02 +0100 [thread overview]
Message-ID: <20191217100102.GC28788@zn.tnic> (raw)
In-Reply-To: <SN6PR12MB2639C1AF7F5EC7F16B22D244F8500@SN6PR12MB2639.namprd12.prod.outlook.com>
On Tue, Dec 17, 2019 at 01:49:13AM +0000, Ghannam, Yazen wrote:
> Can this please be applied to ras/urgent? It fixes a boot issue on some
> recently released AMD systems.
>
> I had the Fixes tag, but I forgot to include CC:<stable>. Sorry about that.
Ok, I've reshuffled ras/core and ras/urgent and pushed them out. I'd
appreciate it if you ran the urgent branch too, on your end. I tested on
everything I have here but my hw doesn't trigger any boot hang issues
anyway. If you have people reporting issues, now would be a good time
for them to test it too.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2019-12-17 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 14:15 [PATCH] x86/mce/AMD: Allow Reserved types to be overwritten in smca_banks[] Yazen Ghannam
2019-12-10 10:07 ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2019-12-17 1:49 ` Ghannam, Yazen
2019-12-17 10:01 ` Borislav Petkov [this message]
2019-12-17 10:01 ` [tip: ras/urgent] x86/MCE/AMD: " tip-bot2 for Yazen Ghannam
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=20191217100102.GC28788@zn.tnic \
--to=bp@alien8.de \
--cc=Yazen.Ghannam@amd.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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).