linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Sasha Levin <sashal@kernel.org>
Cc: gregkh@linuxfoundation.org, jschoenh@amazon.de,
	Yazen.Ghannam@amd.com, hpa@zytor.com, linux-edac@vger.kernel.org,
	mingo@kernel.org, stable@vger.kernel.org, tglx@linutronix.de,
	tony.luck@intel.com, x86@kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/mce: Fix possibly incorrect severity calculation on AMD" failed to apply to 4.19-stable tree
Date: Thu, 2 Jan 2020 10:11:34 +0100	[thread overview]
Message-ID: <20200102091133.GA22772@zn.tnic> (raw)
In-Reply-To: <20200102011411.GF16372@sasha-vm>

On Wed, Jan 01, 2020 at 08:14:11PM -0500, Sasha Levin wrote:
> On Mon, Dec 30, 2019 at 04:56:21PM +0100, Borislav Petkov wrote:
> > On Sun, Dec 29, 2019 at 04:55:16PM +0100, gregkh@linuxfoundation.org wrote:
> > > The patch below does not apply to the 4.19-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@vger.kernel.org>.
> > 
> > Here's a backport for all 4.x stable series. It only needed a
> > file-rename.
> 
> This ended up getting picked up by AUTOSEL which did the right thing
> with regards to filename changes as confirmed with the provided
> backport, thank you :)

Can Greg find out whether AUTOSEL did the right thing and then if so, not
send those mails?

:-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

  reply	other threads:[~2020-01-02  9:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-29 15:55 FAILED: patch "[PATCH] x86/mce: Fix possibly incorrect severity calculation on AMD" failed to apply to 4.19-stable tree gregkh
2019-12-30 15:56 ` Borislav Petkov
2020-01-02  1:14   ` Sasha Levin
2020-01-02  9:11     ` Borislav Petkov [this message]
2020-01-02 12:29       ` Sasha Levin
2020-01-02 15:33         ` Borislav Petkov

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=20200102091133.GA22772@zn.tnic \
    --to=bp@suse.de \
    --cc=Yazen.Ghannam@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jschoenh@amazon.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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).