public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yury Norov <yury.norov@gmail.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Patch for stable
Date: Thu, 26 May 2022 21:24:00 +0200	[thread overview]
Message-ID: <Yo/T0LPar9q8LROO@kroah.com> (raw)
In-Reply-To: <Yo+9KLc6VG8CKeH+@yury-laptop>

On Thu, May 26, 2022 at 10:47:20AM -0700, Yury Norov wrote:
> + Vitaly Kuznetsov <vkuznets@redhat.com>
> + Paolo Bonzini <pbonzini@redhat.com>
> 
> On Thu, May 26, 2022 at 06:49:13PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, May 26, 2022 at 09:42:25AM -0700, Yury Norov wrote:
> > > Hi Greg,
> > > 
> > > Can you please consider taking the patch "KVM: x86: hyper-v: fix type
> > > of valid_bank_mask" into stable?
> > > 
> > > Commit ea8c66fe8d8f4f93df941e52120a3512d7bf5128 upstream.
> > 
> > For what kernel tree(s) should thie be backported?
> 
> For me, Ubuntu LTS is important (4.15 and 5.4). I believe, Vitaly
> and Paolo may know better for Red Hat, and in general.

Did you test this on any of these older kernels?  Please do so and
provide the backported kernels.  Also you can not skip a kernel version
(i.e. it needs to be in all stable kernels back to 5.4 if you want it
there.)

And note that 4.15 is not a supported kernel by us, please work with
Canonical if you want a patch applied to their random kernel tree.

thanks,

greg k-h

      reply	other threads:[~2022-05-26 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 16:42 Patch for stable Yury Norov
2022-05-26 16:49 ` Greg Kroah-Hartman
2022-05-26 17:47   ` Yury Norov
2022-05-26 19:24     ` Greg Kroah-Hartman [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=Yo/T0LPar9q8LROO@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=vkuznets@redhat.com \
    --cc=yury.norov@gmail.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