From: Greg KH <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: laijs@linux.alibaba.com, pbonzini@redhat.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] kvm: check tlbs_dirty directly" failed to apply to 4.14-stable tree
Date: Mon, 22 Feb 2021 12:00:50 +0100 [thread overview]
Message-ID: <YDOO4kmRVXHnOdr8@kroah.com> (raw)
In-Reply-To: <YC2SRG41YJD29sq5@debian>
On Wed, Feb 17, 2021 at 10:01:40PM +0000, Sudip Mukherjee wrote:
> Hi Greg,
>
> On Mon, Jan 11, 2021 at 09:49:44AM +0100, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.14-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 is the backport, will apply to all branches till 4.4-stable.
THanks for these, all now queued up.
greg k-h
prev parent reply other threads:[~2021-02-22 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 8:49 FAILED: patch "[PATCH] kvm: check tlbs_dirty directly" failed to apply to 4.14-stable tree gregkh
2021-02-17 22:01 ` Sudip Mukherjee
2021-02-22 11:00 ` Greg KH [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=YDOO4kmRVXHnOdr8@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=laijs@linux.alibaba.com \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.