From: Greg KH <gregkh@linuxfoundation.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: matthew.auld@intel.com, matthew.brost@intel.com,
nirmoy.das@intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/xe/vm: move xa_alloc to prevent UAF" failed to apply to 6.11-stable tree
Date: Tue, 8 Oct 2024 17:31:57 +0200 [thread overview]
Message-ID: <2024100817-quarrel-retread-b7a3@gregkh> (raw)
In-Reply-To: <au2yg6xpydfomljjfmll6j6h6mwpzm73kojc5zjck3im6grson@e3ajgznra66s>
On Tue, Oct 08, 2024 at 09:29:49AM -0500, Lucas De Marchi wrote:
> On Mon, Oct 07, 2024 at 07:45:27PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 6.11-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>.
> >
> > To reproduce the conflict and resubmit, you may use the following commands:
> >
> > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.11.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 74231870cf4976f69e83aa24f48edb16619f652f
>
> did this change for sending patches to stable? Is this an alternative
> only for using --in-reply-to to a failed patch or can
> `git cherry-pick -x` be used as alternative to the
> "commit 74231870cf4976f69e83aa24f48edb16619f652f upstream." in the body?
I'll take either/any/some kind of hint as to what the commit id is. If
you want to hand-write it, wonderful, if you want to use git to
automatically include it like here, even better, it's your choice.
greg k-h
prev parent reply other threads:[~2024-10-08 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 17:45 FAILED: patch "[PATCH] drm/xe/vm: move xa_alloc to prevent UAF" failed to apply to 6.11-stable tree gregkh
2024-10-08 14:29 ` Lucas De Marchi
2024-10-08 15:31 ` 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=2024100817-quarrel-retread-b7a3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=nirmoy.das@intel.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;
as well as URLs for NNTP newsgroup(s).