From: Jens Axboe <axboe@kernel.dk>
To: Jianqiang kang <jianqkang@sina.cn>,
gregkh@linuxfoundation.org, stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
asml.silence@gmail.com, io-uring@vger.kernel.org
Subject: Re: [PATCH 5.15.y] io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop
Date: Thu, 26 Feb 2026 05:37:15 -0700 [thread overview]
Message-ID: <dc3079cf-15ac-416f-993c-9b81dafebeef@kernel.dk> (raw)
In-Reply-To: <20260226062711.426301-1-jianqkang@sina.cn>
On 2/25/26 11:27 PM, Jianqiang kang wrote:
> From: Jens Axboe <axboe@kernel.dk>
>
> [ Upstream commit 10dc959398175736e495f71c771f8641e1ca1907 ]
This, and the one for 6.1 is fine to be applied for stable, but if you
add this one for 5.15 then please also add it for 5.10 as well. Those
two codebases are the same in terms of io_uring, and hence any io_uring/
patch applied either should also go to the other.
--
Jens Axboe
prev parent reply other threads:[~2026-02-26 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 6:27 [PATCH 5.15.y] io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop Jianqiang kang
2026-02-26 12:37 ` Jens Axboe [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=dc3079cf-15ac-416f-993c-9b81dafebeef@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=jianqkang@sina.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--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