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.10 000/597] 5.10.110-rc2 review
Date: Thu, 7 Apr 2022 02:43:47 -0700 [thread overview]
Message-ID: <20220407094347.GA3044306@roeck-us.net> (raw)
In-Reply-To: <20220407093659.GB3041848@roeck-us.net>
On Thu, Apr 07, 2022 at 02:37:01AM -0700, Guenter Roeck wrote:
> On Wed, Apr 06, 2022 at 03:43:51PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.110 release.
> > There are 597 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 Fri, 08 Apr 2022 13:27:53 +0000.
> > Anything received after that time might be too late.
> >
>
> Build results:
> total: 161 pass: 150 fail: 11
> Failed builds:
> alpha:defconfig
> alpha:allmodconfig
> csky:defconfig
> m68k:defconfig
> m68k:allmodconfig
> m68k:sun3_defconfig
> m68k_nommu:m5475evb_defconfig
> microblaze:mmu_defconfig
> nds32:defconfig
> nds32:allmodconfig
> um:defconfig
> Qemu test results:
> total: 477 pass: 448 fail: 29
> Failed tests:
> alpha:defconfig:initrd
> alpha:defconfig:devtmpfs:ide:net,e1000:rootfs
> alpha:defconfig:devtmpfs:sdhci:mmc:net,ne2k_pci:rootfs
> alpha:defconfig:devtmpfs:usb-ohci:net,pcnet:rootfs
> alpha:defconfig:devtmpfs:usb-ehci:net,virtio-net:rootfs
> alpha:defconfig:devtmpfs:pci-bridge:usb-xhci:net,pcnet:rootfs
> alpha:defconfig:devtmpfs:usb-uas-ehci:net,e1000:rootfs
> alpha:defconfig:devtmpfs:usb-uas-xhci:net,e1000:rootfs
> alpha:defconfig:devtmpfs:pci-bridge:scsi[AM53C974]:net,tulip:rootfs
> alpha:defconfig:devtmpfs:scsi[DC395]:net,e1000-82545em:rootfs
> alpha:defconfig:devtmpfs:scsi[MEGASAS]:net,rtl8139:rootfs
> alpha:defconfig:devtmpfs:scsi[MEGASAS2]:net,e1000-82544gc:rootfs
> alpha:defconfig:devtmpfs:scsi[FUSION]:net,usb-ohci:rootfs
> alpha:defconfig:devtmpfs:nvme:net,e1000:rootfs
> q800:m68040:mac_defconfig:initrd
> q800:m68040:mac_defconfig:rootfs
> microblaze:petalogix-s3adsp1800:initrd
> microblaze:petalogix-s3adsp1800:rootfs
> microblaze:petalogix-ml605:initrd
> microblaze:petalogix-ml605:rootfs
> microblazeel:petalogix-s3adsp1800:initrd
> microblazeel:petalogix-s3adsp1800:rootfs
> microblazeel:petalogix-ml605:initrd
> microblazeel:petalogix-ml605:rootfs
> s390:defconfig:nolocktests:smp2:net,default:initrd
> s390:defconfig:nolocktests:smp2:virtio-blk-ccw:net,virtio-net-pci:rootfs
> s390:defconfig:nolocktests:smp2:scsi[virtio-ccw]:net,default:rootfs
> s390:defconfig:nolocktests:virtio-pci:net,virtio-net-pci:rootfs
> s390:defconfig:nolocktests:scsi[virtio-pci]:net,default:rootfs
>
> Errors:
>
> fs/binfmt_elf.c: In function 'fill_note_info':
> fs/binfmt_elf.c:2050:45: error: 'siginfo' undeclared
> fs/binfmt_elf.c:2056:53: error: 'regs' undeclared
>
> Plus there are the same s390 crashes as with -rc1.
>
> No idea what I am missing here, but the failures are exactly the same as for -rc1.
>
Sorry, something went wrong. Please disregard. I still see failures,
but different ones. I'll resend my report after repeating the test.
Guenter
next prev parent reply other threads:[~2022-04-07 9:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 13:43 [PATCH 5.10 000/597] 5.10.110-rc2 review Greg Kroah-Hartman
2022-04-06 22:17 ` Fox Chen
2022-04-06 22:50 ` Shuah Khan
2022-04-06 23:02 ` Florian Fainelli
2022-04-07 7:55 ` Bagas Sanjaya
2022-04-07 8:15 ` Sudip Mukherjee
2022-04-07 9:10 ` Guenter Roeck
2022-04-07 9:35 ` Sudip Mukherjee
2022-04-07 9:40 ` Guenter Roeck
2022-04-07 9:36 ` Guenter Roeck
2022-04-07 9:43 ` Guenter Roeck [this message]
2022-04-07 10:52 ` Naresh Kamboju
2022-04-07 17:42 ` Guenter Roeck
2022-04-07 18:29 ` Greg Kroah-Hartman
2022-04-07 18:35 ` Greg Kroah-Hartman
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=20220407094347.GA3044306@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