From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: azizcan.d@mileniumsec.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] io_uring/poll: ensure EPOLL_ONESHOT is propagated for" failed to apply to 5.15-stable tree
Date: Sat, 2 May 2026 08:27:10 +0200 [thread overview]
Message-ID: <2026050207-dirtiness-reapply-f841@gregkh> (raw)
In-Reply-To: <a1b41674-0593-422b-93bb-edc3993d829c@kernel.dk>
On Fri, May 01, 2026 at 08:40:31PM -0600, Jens Axboe wrote:
> On 5/1/26 5:09 AM, 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>.
> >
> > 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-5.15.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 1967f0b1cafdde37aa9e08e6021c14bcc484b7a5
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026050100-washday-snowdrift-2968@gregkh' --subject-prefix 'PATCH 5.15.y' HEAD^..
>
> Not needed.
Note that the Fixes: line implies that it is needed:
Fixes: 4464853277d0 ("io_uring: pass in EPOLL_URING_WAKE for eventfd signaling and wakeups")
as that has been in the following releases:
5.10.162 5.15.90 6.1.3 6.2
which is why this, and the 5.10.y FAILED email was sent out. Is that
marking incorrect?
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-02 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 11:09 FAILED: patch "[PATCH] io_uring/poll: ensure EPOLL_ONESHOT is propagated for" failed to apply to 5.15-stable tree gregkh
2026-05-02 2:40 ` Jens Axboe
2026-05-02 2:46 ` Jens Axboe
2026-05-02 6:27 ` Greg KH [this message]
2026-05-02 14:00 ` Jens Axboe
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=2026050207-dirtiness-reapply-f841@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=azizcan.d@mileniumsec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox