From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
shuah@kernel.org, patches@kernelci.org,
ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org,
stable@vger.kernel.org
Subject: Re: [PATCH 4.4 000/308] 4.4.223-rc2 review
Date: Fri, 8 May 2020 14:10:40 -0700 [thread overview]
Message-ID: <ada628d9-fd10-acd4-94fe-cdcf1caf43fc@roeck-us.net> (raw)
In-Reply-To: <20200508142854.087405740@linuxfoundation.org>
On 5/8/20 7:32 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.223 release.
> There are 308 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 Sun, 10 May 2020 14:26:28 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 169 pass: 156 fail: 13
Failed builds:
<all mips>
Qemu test results:
total: 332 pass: 272 fail: 60
Failed tests:
arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:mem256:imx6ul-14x14-evk:initrd
arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:sd:mem256:imx6ul-14x14-evk:rootfs
arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:usb1:mem256:imx6ul-14x14-evk:rootfs
<all mips>
Bisecting the arm boot failure points to commit 9b86858f37d682 ("regulator:
Try to resolve regulators supplies on registration"). Reverting this commit fixes
the problem.
The mips build failure is caused by commit d0e89dd815b712 ("MIPS: math-emu:
Fix m{add,sub}.s shifts"). It removes the define of SPXSRSXn, but that define
is still used in v4.4.y. Reverting the offending patch fixes the problem.
Guenter
next prev parent reply other threads:[~2020-05-08 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 14:32 Greg Kroah-Hartman
2020-05-08 18:55 ` Guenter Roeck
2020-05-08 21:10 ` Guenter Roeck [this message]
2020-05-09 6:52 ` Greg Kroah-Hartman
2020-05-09 11:24 ` Naresh Kamboju
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=ada628d9-fd10-acd4-94fe-cdcf1caf43fc@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®