public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jack Wang <jack.wang.usish@gmail.com>,
	wanpengli@tencent.com, tglx@linutronix.de,
	stable <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] KVM: x86: Defer vtime accounting 'til after IRQ handling" failed to apply to 5.10-stable tree
Date: Thu, 27 May 2021 15:25:33 +0000	[thread overview]
Message-ID: <YK+57TTRNIhk6xCh@google.com> (raw)
In-Reply-To: <YK9jzz3vOMNJdAo1@kroah.com>

On Thu, May 27, 2021, Greg Kroah-Hartman wrote:
> On Wed, May 26, 2021 at 08:08:09AM +0200, Jack Wang wrote:
> > <gregkh@linuxfoundation.org> 于2021年5月14日周五 下午9:32写道:
> > >
> > >
> > > The patch below does not apply to the 5.10-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>.
> > 
> > If I first apply 866a6dadbb02 ("context_tracking: Move guest exit
> > context tracking to separate helpers")
> > and 88d8220bbf06 ("context_tracking: Move guest exit vtime accounting
> > to separate helpers")
> > 
> > then I can apply this commit cleanly to latest 5.10.y, I suppose it
> > will work for 5.12.

Thanks much!

> That worked, thanks!  Now queued up.

To not mess up in the future, I assume known dependencies should be tagged
"Cc: stable...", even if the dependencies aren't technically bug fixes?
The plan all along was that all three patches would have to be picked up, but
apparently I thought that would happen automagically.

  reply	other threads:[~2021-05-27 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 15:37 FAILED: patch "[PATCH] KVM: x86: Defer vtime accounting 'til after IRQ handling" failed to apply to 5.10-stable tree gregkh
2021-05-26  6:08 ` Jack Wang
2021-05-27  9:18   ` Greg Kroah-Hartman
2021-05-27 15:25     ` Sean Christopherson [this message]
2021-05-27 15:43       ` Greg Kroah-Hartman

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=YK+57TTRNIhk6xCh@google.com \
    --to=seanjc@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack.wang.usish@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wanpengli@tencent.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