From: Greg KH <gregkh@linuxfoundation.org>
To: Wei Liu <wei.liu@kernel.org>
Cc: mikelley@microsoft.com, torvalds@linux-foundation.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/hyperv: remove on-stack cpumask from" failed to apply to 5.14-stable tree
Date: Mon, 20 Sep 2021 17:55:08 +0200 [thread overview]
Message-ID: <YUiu3KYIVycHS9CB@kroah.com> (raw)
In-Reply-To: <20210920154447.gess7eb3qho6s2ax@liuwe-devbox-debian-v2>
On Mon, Sep 20, 2021 at 03:44:47PM +0000, Wei Liu wrote:
> Hi Greg,
>
> On Mon, Sep 20, 2021 at 10:56:55AM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.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>.
>
> There is one prerequisite patch for this patch. I can backport both to
> all relevant stable branches, but I would like to know how you would
> like to receive backport patches. Several git bundles to stable@?
> Several two-patch series to stable@? I can also give you several tags /
> branches to pull from if you like.
If they cherry-pick cleanly, just the git ids are all we need.
Otherwise a patch series is great, git bundles are only a last-resort.
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-20 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 8:56 FAILED: patch "[PATCH] x86/hyperv: remove on-stack cpumask from" failed to apply to 5.14-stable tree gregkh
2021-09-20 15:44 ` Wei Liu
2021-09-20 15:55 ` Greg KH [this message]
2021-09-20 16:01 ` Wei Liu
2021-09-20 16:09 ` Wei Liu
2021-09-20 16:19 ` Greg KH
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=YUiu3KYIVycHS9CB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mikelley@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wei.liu@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