From: Greg KH <gregkh@linuxfoundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: [PATCH 6.12.y] mm, slab: clean up slab->obj_exts always
Date: Fri, 9 May 2025 08:23:12 +0200 [thread overview]
Message-ID: <2025050957-pronto-overnight-20ed@gregkh> (raw)
In-Reply-To: <CAJuCfpGoto6chqWSN_FET4isyLfioKzxadEQbLyKYzXTwCo+FA@mail.gmail.com>
On Thu, May 08, 2025 at 06:14:26PM +0000, Suren Baghdasaryan wrote:
> On Thu, May 8, 2025 at 5:15 PM Sasha Levin <sashal@kernel.org> wrote:
> >
> > On Thu, May 08, 2025 at 05:04:45PM +0000, Suren Baghdasaryan wrote:
> > >On Thu, May 8, 2025 at 4:18 PM Sasha Levin <sashal@kernel.org> wrote:
> > >>
> > >> [ Sasha's backport helper bot ]
> > >>
> > >> Hi,
> > >>
> > >> Summary of potential issues:
> > >> ⚠️ Found matching upstream commit but patch is missing proper reference to it
> > >
> > >Not sure why "patch is missing proper reference to it". I see (cherry
> > >picked from commit be8250786ca94952a19ce87f98ad9906448bc9ef) in place.
> > >Did I miss something?
> >
> > It tries to find one of the references described in the docs for
> > submitting stuff to stable@:
> >
> > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#option-3
>
> Ah, I see now what I missed. Thanks!
> Would you be able to add the reference or should I repost the backports?
No need, it's already in the queue for the next round of stable releases
in a few hours.
greg k-h
prev parent reply other threads:[~2025-05-09 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 7:55 FAILED: patch "[PATCH] mm, slab: clean up slab->obj_exts always" failed to apply to 6.12-stable tree gregkh
2025-05-05 23:26 ` [PATCH 6.12.y] mm, slab: clean up slab->obj_exts always Suren Baghdasaryan
2025-05-08 16:18 ` Sasha Levin
2025-05-08 17:04 ` Suren Baghdasaryan
2025-05-08 17:15 ` Sasha Levin
2025-05-08 18:14 ` Suren Baghdasaryan
2025-05-09 6:23 ` 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=2025050957-pronto-overnight-20ed@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
/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