From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.2-rc2
Date: Mon, 2 Jan 2023 14:56:56 -0800 [thread overview]
Message-ID: <20230102225656.GA3532398@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wim8DMRzjyYTJ3UbdqZ26keQyZSU02NZb-JY1=9OpcO1w@mail.gmail.com>
On Sun, Jan 01, 2023 at 02:01:04PM -0800, Linus Torvalds wrote:
> So the week started so slow due to the holidays that I thought I might
> not have any reason to do an rc2 at all, but by the end of the week I
> did end up getting a smattering of pull requests, so here we are. It's
> tiny, even smaller than usual for an rc2, and honestly, I'd expect
> that trend to continue for rc3. A lot of people are still off for
> another week on a well-deserved winter holiday, and so I suspect
> things will continue to be fairly quiet.
>
> Anyway, last week saw mainly some nvme fixes, some i915 drm work, and
> some kvm fixes (and kvm testing fixes). See below for the full
> shortlog, and if you're not still in a food coma from the holidays,
> please do give this all a good testing.
>
Build results:
total: 155 pass: 151 fail: 4
Failed builds:
powerpc:allmodconfig
sh:defconfig
sh:shx3_defconfig
xtensa:allmodconfig
Qemu test results:
total: 500 pass: 498 fail: 2
Failed tests:
arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:net,default:zynq-zc702:rootfs
arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:zynq-zed:rootfs
Same as last week, so I won't go into details for the above failures.
One detail to mention, though, is that sh:rts7751r2dplus_defconfig
no longer builds with older versions of binutils (2.32). Trying to
do so results in the following build error.
`.exit.text' referenced in section `__bug_table' of drivers/char/hw_random/core.o:
defined in discarded section `.exit.text' of drivers/char/hw_random/core.o
To make this more interesting, kernels older than v5.10 do not boot
(at least not in qemu) when images are built with binutils 2.27 or newer.
That is why I had used binutils 2.32 in the first place.
I didn't bother tracking this down but switched to binutils 2.39 when
building v5.10+ images.
Guenter
next prev parent reply other threads:[~2023-01-02 22:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 22:01 Linux 6.2-rc2 Linus Torvalds
2023-01-02 10:20 ` Build regressions/improvements in v6.2-rc2 Geert Uytterhoeven
2023-01-02 22:56 ` Guenter Roeck [this message]
2023-01-03 0:21 ` Linux 6.2-rc2 Linus Torvalds
2023-01-03 1:45 ` Guenter Roeck
2023-01-03 2:13 ` Linus Torvalds
2023-01-03 3:57 ` Guenter Roeck
2023-01-03 4:26 ` Nathan Chancellor
2023-01-03 9:14 ` Thorsten Leemhuis
2023-01-03 10:58 ` Ard Biesheuvel
2023-01-03 11:45 ` Conor Dooley
2023-01-03 12:22 ` Guenter Roeck
2023-01-03 18:26 ` Nathan Chancellor
2023-01-03 18:34 ` Linus Torvalds
2023-01-05 13:44 ` Masahiro Yamada
2023-01-04 10:34 ` Michael Ellerman
2023-01-10 0:32 ` SeongJae Park
2023-01-10 18:39 ` Masahiro Yamada
2023-01-10 19:14 ` SeongJae Park
2023-01-23 9:09 ` Masahiro Yamada
2023-01-23 18:27 ` SeongJae Park
2023-02-06 22:56 ` SeongJae Park
2023-02-08 1:27 ` Masahiro Yamada
2023-01-13 14:59 ` Tom Saeger
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=20230102225656.GA3532398@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).