From: Greg KH <gregkh@linuxfoundation.org>
To: dan.carpenter@linaro.org, rientjes@google.com,
stable@vger.kernel.org, vbabka@suse.cz
Subject: Re: FAILED: patch "[PATCH] mm/slab: make __free(kfree) accept error pointers" failed to apply to 6.1-stable tree
Date: Mon, 13 May 2024 15:38:53 +0200 [thread overview]
Message-ID: <2024051337-facelift-bakeshop-cbba@gregkh> (raw)
In-Reply-To: <2024051335-aversion-endearing-7ab9@gregkh>
On Mon, May 13, 2024 at 03:31:35PM +0200, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 6.1-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.1.y
> git checkout FETCH_HEAD
> git cherry-pick -x cd7eb8f83fcf258f71e293f7fc52a70be8ed0128
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2024051335-aversion-endearing-7ab9@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^..
>
> Possible dependencies:
>
> cd7eb8f83fcf ("mm/slab: make __free(kfree) accept error pointers")
> a67d74a4b163 ("mm/slab: Add __free() support for kvfree")
> 54da6a092431 ("locking: Introduce __cleanup() based infrastructure")
Nevermind, I got this to work here and 6.6.y already, sorry for the
noise.
greg k-h
prev parent reply other threads:[~2024-05-13 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 13:31 FAILED: patch "[PATCH] mm/slab: make __free(kfree) accept error pointers" failed to apply to 6.1-stable tree gregkh
2024-05-13 13:38 ` 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=2024051337-facelift-bakeshop-cbba@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@linaro.org \
--cc=rientjes@google.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).