From: Greg KH <gregkh@linuxfoundation.org>
To: Muchun Song <songmuchun@bytedance.com>
Cc: Marco Elver <elver@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Xiongchun duan <duanxiongchun@bytedance.com>,
Dmitry Vyukov <dvyukov@google.com>,
Alexander Potapenko <glider@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux- stable <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] mm: kfence: fix objcgs vector allocation" failed to apply to 5.15-stable tree
Date: Fri, 29 Apr 2022 11:07:11 +0200 [thread overview]
Message-ID: <Ymuqv5O17fN8/nQE@kroah.com> (raw)
In-Reply-To: <CAMZfGtVOyUW0x1Hp689tV=Sr2O=H=jWRFpyJyRxVi5mHb=x8xA@mail.gmail.com>
On Fri, Apr 29, 2022 at 04:06:59PM +0800, Muchun Song wrote:
> On Fri, Apr 29, 2022 at 3:10 PM Marco Elver <elver@google.com> wrote:
> >
> > On Fri, Apr 29, 2022 at 12:15PM +0800, Muchun Song wrote:
> > > On Thu, Apr 28, 2022 at 11:36 PM <gregkh@linuxfoundation.org> wrote:
> > > >
> > > >
> > > > The patch below does not apply to the 5.15-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>.
> > > >
> > >
> > > I have fixed all conflicts and the attachment is the new patch for 5.15.
> > >
> > > Thanks.
> >
> > I wanted to test, but unfortunately this doesn't apply to 5.15.36.
>
> My bad. I was based on v5.15.33. I have made a new version
> for v5.15.36 (see attachment) and tested it.
>
> Thanks.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-04-29 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 15:36 FAILED: patch "[PATCH] mm: kfence: fix objcgs vector allocation" failed to apply to 5.15-stable tree gregkh
2022-04-29 4:15 ` [External] " Muchun Song
2022-04-29 7:10 ` Marco Elver
2022-04-29 8:06 ` Muchun Song
2022-04-29 9:07 ` 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=Ymuqv5O17fN8/nQE@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=duanxiongchun@bytedance.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=roman.gushchin@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=stable@vger.kernel.org \
--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 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.