From: Jens Axboe <axboe@kernel.dk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Patches for 5.15-stable
Date: Sun, 22 Jan 2023 08:06:31 -0700 [thread overview]
Message-ID: <eaf582d3-82da-b6cf-76e0-55b4f2597f8b@kernel.dk> (raw)
In-Reply-To: <Y81MNeUGrntM0FKW@kroah.com>
On 1/22/23 7:46 AM, Greg Kroah-Hartman wrote:
> 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!
>
> Note, some of the io_uring patches you sent for 5.10 and 5.15 have
> commits in the tree that are marked as "fixing" these commits. I tried
> to backport them as well, but got a lot of failures, which is why you
> got those emails. If they are not relevant, please feel free to ignore,
> but if they are needed, maybe we also need them as well?
I'll go over those failures and send any in that are needed.
--
Jens Axboe
next prev parent reply other threads:[~2023-01-22 15:06 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
2023-01-22 4:34 ` Jens Axboe
2023-01-22 14:46 ` Greg Kroah-Hartman
2023-01-22 15:06 ` Jens Axboe [this message]
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=eaf582d3-82da-b6cf-76e0-55b4f2597f8b@kernel.dk \
--to=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