From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, slade@sladewatkins.com
Subject: Re: [PATCH 5.18 0000/1094] 5.18.18-rc2 review
Date: Tue, 16 Aug 2022 21:24:45 -0700 [thread overview]
Message-ID: <20220817042445.GC1880847@roeck-us.net> (raw)
In-Reply-To: <20220816124604.978842485@linuxfoundation.org>
On Tue, Aug 16, 2022 at 02:59:27PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.18.18 release.
> There are 1094 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 18 Aug 2022 12:43:14 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 154 pass: 154 fail: 0
Qemu test results:
total: 481 pass: 480 fail: 1
Failed tests:
arm:bletchley-bmc:aspeed_g5_defconfig:notests:usb0:net,nic:aspeed-bmc-facebook-bletchley:rootfs
The failing boot test is new and not a concern. I'll see if I can figure
out why it fails. If it is too difficult to fix (for example because 5.18
simply doesn't support usb on bletchley-bmc), I'll just skip it next time.
Tested-by: Guenter Roeck <linux@roeck-us.net>
Guenter
next prev parent reply other threads:[~2022-08-17 4:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 12:59 [PATCH 5.18 0000/1094] 5.18.18-rc2 review Greg Kroah-Hartman
2022-08-16 14:34 ` Sudip Mukherjee
2022-08-16 14:43 ` Greg Kroah-Hartman
2022-08-16 16:25 ` Naresh Kamboju
2022-08-16 16:41 ` Sudip Mukherjee
2022-08-16 16:57 ` Sudip Mukherjee
2022-08-17 11:39 ` Greg Kroah-Hartman
2022-08-16 19:15 ` Naresh Kamboju
2022-08-17 7:25 ` Maxime Ripard
2022-08-17 0:59 ` Ron Economos
2022-08-17 4:24 ` Guenter Roeck [this message]
2022-08-17 13:34 ` Greg Kroah-Hartman
2022-08-17 15:24 ` Guenter Roeck
2022-08-17 12:57 ` Justin Forbes
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=20220817042445.GC1880847@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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