From: Greg KH <gregkh@linuxfoundation.org>
To: surenb@google.com, akpm@linux-foundation.org, fweimer@redhat.com,
jannh@google.com, jeffv@google.com, jmorris@namei.org,
keescook@chromium.org, mhocko@suse.com, minchan@kernel.org,
oleg@redhat.com, rientjes@google.com, shakeelb@google.com,
stable@vger.kernel.org, timmurray@google.com,
torvalds@linux-foundation.org
Subject: Re: FAILED: patch "[PATCH] mm/madvise: replace ptrace attach requirement for" failed to apply to 5.10-stable tree
Date: Mon, 15 Mar 2021 12:16:43 +0100 [thread overview]
Message-ID: <YE9CG2S+ufk7YsmG@kroah.com> (raw)
In-Reply-To: <1615806428159123@kroah.com>
On Mon, Mar 15, 2021 at 12:07:08PM +0100, gregkh@linuxfoundation.org wrote:
>
> 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>.
>
> thanks,
>
> greg k-h
>
> ------------------ original commit in Linus's tree ------------------
>
> >From 96cfe2c0fd23ea7c2368d14f769d287e7ae1082e Mon Sep 17 00:00:00 2001
> From: Suren Baghdasaryan <surenb@google.com>
> Date: Fri, 12 Mar 2021 21:08:06 -0800
> Subject: [PATCH] mm/madvise: replace ptrace attach requirement for
> process_madvise
No, sorry, wrong commit, this one works fine in 5.10-stable, my fault...
greg k-h
prev parent reply other threads:[~2021-03-15 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 11:07 FAILED: patch "[PATCH] mm/madvise: replace ptrace attach requirement for" failed to apply to 5.10-stable tree gregkh
2021-03-15 11:16 ` 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=YE9CG2S+ufk7YsmG@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=fweimer@redhat.com \
--cc=jannh@google.com \
--cc=jeffv@google.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=oleg@redhat.com \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=timmurray@google.com \
--cc=torvalds@linux-foundation.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