From: Pavel Begunkov <asml.silence@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH stable-5.15 0/5] io_uring backports
Date: Mon, 17 Oct 2022 14:08:57 +0100 [thread overview]
Message-ID: <3b067018-3b79-9be4-455d-e48ae91afee8@gmail.com> (raw)
In-Reply-To: <Y00iTiwiIGaIoGhm@kroah.com>
On 10/17/22 10:37, Greg KH wrote:
> On Sun, Oct 16, 2022 at 10:42:53PM +0100, Pavel Begunkov wrote:
>> io_uring backports for stable 5.15
>
> How about 5.19?
Looks there were no conflicts for 5.19 and you applied them
yesterday.
And thanks for queuing all backports!
> If you wait a week or so, 5.19 will be end-of-life, so maybe we can just
> not worry about it :)
--
Pavel Begunkov
next prev parent reply other threads:[~2022-10-17 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 21:42 [PATCH stable-5.15 0/5] io_uring backports Pavel Begunkov
2022-10-16 21:42 ` [PATCH stable-5.15 1/5] io_uring/af_unix: defer registered files gc to io_uring release Pavel Begunkov
2022-10-16 21:42 ` [PATCH stable-5.15 2/5] io_uring: correct pinned_vm accounting Pavel Begunkov
2022-10-16 21:42 ` [PATCH stable-5.15 3/5] io_uring/rw: fix short rw error handling Pavel Begunkov
2022-10-16 21:42 ` [PATCH stable-5.15 4/5] io_uring/rw: fix error'ed retry return values Pavel Begunkov
2022-10-16 21:42 ` [PATCH stable-5.15 5/5] io_uring/rw: fix unexpected link breakage Pavel Begunkov
2022-10-17 9:37 ` [PATCH stable-5.15 0/5] io_uring backports Greg KH
2022-10-17 13:08 ` Pavel Begunkov [this message]
2022-10-17 14:24 ` Greg KH
2022-10-17 9:44 ` Greg KH
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=3b067018-3b79-9be4-455d-e48ae91afee8@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--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