public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jack Wang <jinpuwang@gmail.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [stable-4.14 0/3] some backport for stable
Date: Fri, 6 Mar 2020 08:59:27 -0500	[thread overview]
Message-ID: <20200306135927.GR21491@sasha-vm> (raw)
In-Reply-To: <20200305163007.25659-1-jinpuwang@gmail.com>

On Thu, Mar 05, 2020 at 05:30:04PM +0100, Jack Wang wrote:
>Hi Greg, hi Sasha,
>
>Please consider following backport for next stable release.
>
>First patch for vhost_net has been tested with our in house regression tests
>with VM migration with kernel 4.14.171, but should be also applied to older
>stable tree.
>
>mce patch is to fix a call trace in EPYC Rome server during boot.
>
>EDAC one is to fix a regression backported to at least 4.14 and 4.19, should be
>applied to both tree, kernel 5.4/5.5 already have the patch.
>
>Regards,
>Jack Wang from IONOS SE.
>
>Eugenio Pérez (1):
>  vhost: Check docket sk_family instead of call getname
>
>Yazen Ghannam (2):
>  x86/mce: Handle varying MCA bank counts
>  EDAC/amd64: Set grain per DIMM
>
> arch/x86/kernel/cpu/mcheck/mce-inject.c | 14 +++++++-------
> arch/x86/kernel/cpu/mcheck/mce.c        | 22 +++++++---------------
> drivers/edac/amd64_edac.c               |  1 +
> drivers/vhost/net.c                     | 13 ++-----------
> 4 files changed, 17 insertions(+), 33 deletions(-)

Queued up. I took the EDAC commit to 4.19 as well.

-- 
Thanks,
Sasha

      parent reply	other threads:[~2020-03-06 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 16:30 [stable-4.14 0/3] some backport for stable Jack Wang
2020-03-05 16:30 ` [stable-4.14 1/3] vhost: Check docket sk_family instead of call getname Jack Wang
2020-03-05 16:30 ` [stable-4.14 2/3] x86/mce: Handle varying MCA bank counts Jack Wang
2020-03-05 16:30 ` [stable-4.14 3/3] EDAC/amd64: Set grain per DIMM Jack Wang
2020-03-06 13:59 ` Sasha Levin [this message]

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=20200306135927.GR21491@sasha-vm \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jinpuwang@gmail.com \
    --cc=stable@vger.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