From: Greg KH <gregkh@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linyunsheng@huawei.com, brouer@redhat.com,
ilias.apalodimas@linaro.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] page_pool: fix inconsistency for page_pool_ring_[un]lock()" failed to apply to 5.15-stable tree
Date: Tue, 30 May 2023 08:23:41 +0100 [thread overview]
Message-ID: <2023053021-perfected-cathouse-bb40@gregkh> (raw)
In-Reply-To: <20230529190034.5e20c2dc@kernel.org>
On Mon, May 29, 2023 at 07:00:34PM -0700, Jakub Kicinski wrote:
> On Sun, 28 May 2023 17:55:22 +0100 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>.
>
> Do you track the missing backports?
Nope, once I email this off, it goes off of my radar. But I know Sasha
sometimes tries to fix them up, as do others as it's an easy TODO list
for people who want to help out.
> We fumbled the Fixes tag on
> this one, turns out it's not needed further back than it applies.
> In such cases is it useful to let you know or just silently ignore
> the failure notification?
It's good to say "this isn't needed" so that others don't spend time on
it, so thanks!
greg k-h
prev parent reply other threads:[~2023-05-30 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 16:55 FAILED: patch "[PATCH] page_pool: fix inconsistency for page_pool_ring_[un]lock()" failed to apply to 5.15-stable tree gregkh
2023-05-30 2:00 ` Jakub Kicinski
2023-05-30 7: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=2023053021-perfected-cathouse-bb40@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brouer@redhat.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=linyunsheng@huawei.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 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.