From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
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 20:35:34 +0200 [thread overview]
Message-ID: <Yk8u9iBPyvv3e+tZ@kroah.com> (raw)
In-Reply-To: <Yk8th5hj6cW7kSPZ@kroah.com>
On Thu, Apr 07, 2022 at 08:29:27PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Apr 07, 2022 at 10:42:15AM -0700, Guenter Roeck wrote:
> > On 4/6/22 06:43, 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.
> > >
> >
> > Trying again ...
> >
> > Test results for v5.10.109-598-gf8a7d8111f45:
> >
> > 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: 453 fail: 24
> > Failed tests:
> > <all alpha>
> > q800:m68040:mac_defconfig:initrd
> > q800:m68040:mac_defconfig:rootfs
> > <all microblaze>
> >
> > Common error is:
> >
> > fs/binfmt_elf.c: In function 'fill_note_info':
> > fs/binfmt_elf.c:2056:53: error: 'regs' undeclared
> >
> > Looks like a bad backport of upstream commit 9ec7d3230717
> > ("coredump/elf: Pass coredump_params into fill_note_info").
> > Only seen on architectures defining CORE_DUMP_USE_REGSET.
>
> Ugh, I'll try to fix this up again, thanks for letting me know...
Ok, having it fail on um made it easy to fix up (hopefully). I'll go
push out a -rc3 with that resolved.
thanks for the testing!
greg k-h
prev parent reply other threads:[~2022-04-07 18:35 UTC|newest]
Thread overview: 16+ 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 19:11 ` Jon Hunter
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
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 [this message]
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=Yk8u9iBPyvv3e+tZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.