From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org, yi1tang.yang@gmail.com
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: FAILED: patch "[PATCH] io_uring/rw: fix missing ERESTARTSYS conversion in read paths" failed to apply to 6.1-stable tree
Date: Thu, 30 Jul 2026 22:39:40 -0400 [thread overview]
Message-ID: <20260730203600.stable-0001@kernel.org> (raw)
In-Reply-To: <818fbace-d4be-4ae3-937c-5cf95713886d@kernel.dk>
On Thu, Jul 30, 2026 at 04:29:32AM -0600, Jens Axboe wrote:
>> Could you resend the 6.1 version?
>
>Here it is.
Queued for 6.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-31 2:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 13:50 FAILED: patch "[PATCH] io_uring/rw: fix missing ERESTARTSYS conversion in read paths" failed to apply to 6.1-stable tree gregkh
2026-07-29 17:29 ` Jens Axboe
2026-07-29 18:23 ` Jens Axboe
2026-07-29 19:06 ` Jens Axboe
2026-07-30 2:40 ` Sasha Levin
2026-07-30 10:29 ` Jens Axboe
2026-07-31 2:39 ` 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=20260730203600.stable-0001@kernel.org \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=yi1tang.yang@gmail.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