From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Chen Wandun <chenwandun@huawei.com>
Subject: Re: [PATCH 5.16 0000/1033] 5.16.3-rc2 review
Date: Wed, 26 Jan 2022 14:04:16 -0800 [thread overview]
Message-ID: <20220126220416.GA3650172@roeck-us.net> (raw)
In-Reply-To: <20220125155447.179130255@linuxfoundation.org>
On Tue, Jan 25, 2022 at 05:33:08PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.16.3 release.
> There are 1033 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, 27 Jan 2022 15:52:30 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 153 pass: 153 fail: 0
Qemu test results:
total: 488 pass: 481 fail: 7
Failed tests:
arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:mem256:net,nic:net,nic:imx6ul-14x14-evk:initrd
arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:sd:mem256:net,nic:net,nic:imx6ul-14x14-evk:rootfs
arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:usb0:mem256:net,nic:net,nic:imx6ul-14x14-evk:rootfs
arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:usb1:mem256:net,nic:net,nic:imx6ul-14x14-evk:rootfs
arm:mcimx7d-sabre:imx_v6_v7_defconfig:nodrm:mem256:net,nic:imx7d-sdb:initrd
arm:mcimx7d-sabre:imx_v6_v7_defconfig:nodrm:usb1:mem256:net,nic:imx7d-sdb:rootfs
arm:mcimx7d-sabre:imx_v6_v7_defconfig:nodrm:sd:mem256:net,nic:imx7d-sdb:rootfs
As reported separately, the failures are due to
Chen Wandun <chenwandun@huawei.com>
mm/page_isolation: unset migratetype directly for non Buddy page
and reverting this patch fixes the problem. The problem is also seen
in the mainline kernel.
Guenter
next prev parent reply other threads:[~2022-01-26 22:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 16:33 Greg Kroah-Hartman
2022-01-25 23:39 ` Shuah Khan
2022-01-26 2:26 ` Justin Forbes
2022-01-26 3:41 ` Rudi Heitbaum
2022-01-26 14:09 ` Ron Economos
2022-01-26 15:59 ` Jeffrin Thalakkottoor
2022-01-26 17:21 ` Fox Chen
2022-01-26 18:13 ` Guenter Roeck
2022-01-26 18:20 ` Greg Kroah-Hartman
2022-01-26 18:23 ` Greg Kroah-Hartman
2022-01-26 21:05 ` Guenter Roeck
2022-01-27 8:17 ` Greg Kroah-Hartman
2022-01-26 22:04 ` Guenter Roeck [this message]
2022-01-27 5:00 ` Scott Bruce
2022-01-27 5:11 ` Daniel Díaz
2022-01-27 6:16 ` Greg Kroah-Hartman
2022-01-27 11:02 ` Naresh Kamboju
2022-01-26 12:17 Ronald Warsow
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=20220126220416.GA3650172@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chenwandun@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®