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.3-rc3
Date: Mon, 20 Mar 2023 13:07:35 -0700 [thread overview]
Message-ID: <14197fd5-26fe-4d1e-9bcc-4012145f0eac@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wiPd8R8-zSqTOtJ9KYeZLBByHug7ny3rgP-ZqzpP_KELg@mail.gmail.com>
On Sun, Mar 19, 2023 at 01:50:21PM -0700, Linus Torvalds wrote:
> So rc3 is fairly big, but that's not hugely usual: it's when a lot of
> the fixes tick up as it takes a while before people find and start
> reporting issues.
>
> And nothing here looks hugely worrisome. The diffstat looks a bit
> unusual in that there are relatively big changes to the scripts and
> selftest directories, but that's mainly due to the git-ignore script
> removal and some kvm selftest cleanups respectively. Nothing scary.
>
> If you ignore those parts, it's a fairly standard "two thirds drivers,
> one third rest" thing. The drivers are all over, but networking, gpu
> and sound are the usual big ones, with the fbdev code showing up
> mainly just because of a coding style fixup to the logo conversion
> scripting (mainly to use proper tab indentation). The qcom
> interconnect driver also shows up for major cleanup and fixes.
>
> Outside of those areas, it's a random collection of fixes: the usual
> arch updates (much - but not all - of it being kvm), some filesystem
> fixes (mainly cifs), core networking, tracing, and some core mm fixes.
>
> Anyway, it's early days still, but nothing here looks particularly odd.
>
> Please test and report any issues you find,
>
No change since last week.
Build results:
total: 153 pass: 146 fail: 7
Failed builds:
alpha:allmodconfig
csky:allmodconfig
m68k:allmodconfig
openrisc:allmodconfig
parisc:allmodconfig
s390:allmodconfig
sparc64:allmodconfig
Qemu test results:
total: 520 pass: 520 fail: 0
Details are available/reported at
https://linux-regtracking.leemhuis.info/regzbot/mainline/.
Guenter
prev parent reply other threads:[~2023-03-20 20:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 20:50 Linus Torvalds
2023-03-20 8:21 ` Build regressions/improvements in v6.3-rc3 Geert Uytterhoeven
2023-03-21 5:38 ` Build regressions/improvements in v6.3-rc3 (drm/msm/) Randy Dunlap
2023-03-21 7:34 ` Geert Uytterhoeven
2023-03-21 15:10 ` Randy Dunlap
2023-03-21 15:33 ` Geert Uytterhoeven
2023-03-20 18:05 ` Linux 6.3-rc3 Nathan Chancellor
2023-03-20 18:26 ` Linus Torvalds
2023-03-20 18:49 ` Linus Torvalds
2023-03-20 18:56 ` Nathan Chancellor
2023-03-20 19:05 ` Linus Torvalds
2023-03-20 18:53 ` Nathan Chancellor
2023-03-20 19:22 ` Nathan Chancellor
2023-03-22 12:44 ` Kalle Valo
2023-03-22 16:36 ` Nathan Chancellor
2023-03-22 20:36 ` Nathan Chancellor
2023-03-24 10:54 ` Kalle Valo
2023-03-24 15:11 ` Nathan Chancellor
2023-03-24 15:23 ` Kalle Valo
2023-03-28 19:07 ` Nathan Chancellor
2023-03-29 8:39 ` Kalle Valo
2023-03-22 16:40 ` Sedat Dilek
2023-03-22 16:55 ` Linus Torvalds
2023-03-22 18:17 ` Nick Desaulniers
2023-03-24 17:16 ` Masahiro Yamada
2023-03-27 16:12 ` Jani Nikula
2023-03-27 17:03 ` Kalle Valo
2023-03-20 20:04 ` Guenter Roeck
2023-03-20 20:30 ` Linus Torvalds
2023-03-20 22:06 ` Nathan Chancellor
2023-03-20 22:48 ` Segher Boessenkool
2023-03-20 23:41 ` Linus Torvalds
2023-03-24 9:41 ` Daniel Vetter
2023-03-20 20:07 ` Guenter Roeck [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=14197fd5-26fe-4d1e-9bcc-4012145f0eac@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
all inboxes | Powered by JetHome®