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.0-rc7
Date: Sun, 25 Sep 2022 18:17:04 -0700 [thread overview]
Message-ID: <20220926011704.GA617511@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjc_CDPy5WbN=e_FtPrd0Yn2Wp4JcdRByeyDoM9azK1mA@mail.gmail.com>
On Sun, Sep 25, 2022 at 02:14:40PM -0700, Linus Torvalds wrote:
> So I was thinking rc7 might end up larger than usual due to travel
> hitting rc6, but it doesn't really seem to have happened.
>
> Yeah, maybe it's marginally bigger than the historical average for
> this time of the release cycle, but it definitely isn't some outlier,
> and it looks fairly normal. Which is all good, and makes me think that
> the final release will happen right on schedule next weekend, unless
> something unexpected happens. Knock wood.
>
> Incidentally, rc7 is also (I think) the first time we have a clean
> 'make allmodconfig' build with no warnings from clang, since the
> patches for frame size problems in the amd display code got merged.
> The stack frame size is still pretty big (and the code isn't exactly
> pretty), but now it's below the level we warn about.
>
> So that's nice to see.
>
> Anyway, full shortlog below - a lot of it is GPU and network drivers,
> but there's various random other fixes in there too.
>
> Let's give this one (hopefully) final week of testing, but it all
> looks pretty good.
>
Testing looks good as well.
Build results:
total: 149 pass: 149 fail: 0
Qemu test results:
total: 490 pass: 490 fail: 0
No more unexpected warnings in boot logs either.
Guenter
next prev parent reply other threads:[~2022-09-26 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 21:14 Linus Torvalds
2022-09-26 1:17 ` Guenter Roeck [this message]
2022-09-26 8:58 ` Build regressions/improvements in v6.0-rc7 Geert Uytterhoeven
2022-09-26 9:27 ` Geert Uytterhoeven
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=20220926011704.GA617511@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®