From: Sasha Levin <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected], Peter Mann <[email protected]>,
[email protected], [email protected]
Subject: Re: FAILED: Patch "io_uring/rw: fix missing NOWAIT check for O_DIRECT start write" failed to apply to v5.15-stable tree
Date: Sat, 9 Nov 2024 06:55:46 -0500 [thread overview]
Message-ID: <Zy9NwqnNjTOtN3RH@sashalap> (raw)
In-Reply-To: <[email protected]>
On Wed, Nov 06, 2024 at 07:45:54AM -0700, Jens Axboe wrote:
>On 11/5/24 7:12 PM, Sasha Levin wrote:
>> The patch below does not apply to the v5.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 <[email protected]>.
>
>Here's a tested series for 5.15-stable. I'll send the 5.10-stable
>series after this.
I've queued up the 5.10 and 5.15 backports, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2024-11-09 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 2:12 FAILED: Patch "io_uring/rw: fix missing NOWAIT check for O_DIRECT start write" failed to apply to v5.15-stable tree Sasha Levin
2024-11-06 14:45 ` Jens Axboe
2024-11-09 11:55 ` Sasha Levin [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=Zy9NwqnNjTOtN3RH@sashalap \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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