From: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>
Subject: Re: Patches for 5.15-stable
Date: Sat, 21 Jan 2023 23:28:44 -0500 [thread overview]
Message-ID: <Y8y7fMAmJtB1559f@sashalap> (raw)
In-Reply-To: <be4f98fe-2e66-f7df-5f59-acc2ed7cccdb@kernel.dk>
On Sat, Jan 21, 2023 at 10:52:10AM -0700, Jens Axboe wrote:
>Hi,
>
>Two parts here:
>
>1) The wakeup fix that went into 5.10-stable, but hadn't been done for
> 5.15-stable yet. It was the last 3 patches in the 5.10-stable backport
> for io_uring
>
>2) Other patches that were marked for stable or should go to stable, but
> initially failed.
>
>This gets us to basically parity on the regression test front for 5.15,
>and have all been runtime tested.
>
>Please queue up for the next 5.15-stable, thanks!
I've queued up this and the other backports you've sent today, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-01-22 4:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 17:52 Patches for 5.15-stable Jens Axboe
2023-01-22 4:28 ` Sasha Levin [this message]
2023-01-22 4:34 ` Jens Axboe
2023-01-22 14:46 ` Greg Kroah-Hartman
2023-01-22 15:06 ` Jens Axboe
2023-01-22 17:48 ` 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=Y8y7fMAmJtB1559f@sashalap \
--to=sashal@kernel.org \
--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