linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 5.18-rc2
Date: Sun, 10 Apr 2022 21:58:22 -0700	[thread overview]
Message-ID: <20220411045822.GA295401@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wh0+DYC2+Aeu2=vfUtGaDqVuKxKrxyhwQFoG89rcynzww@mail.gmail.com>

On Sun, Apr 10, 2022 at 02:54:27PM -1000, Linus Torvalds wrote:
> It's Sunday afternoon for me, which means "rc release time". Things
> look fairly normal here, although it's early in the release cycle so
> it's a bit hard to say for sure. But at least it's not looking
> particularly odd, and we have fixes all over.
> 
> Drivers is the bulk of it, and there's a little bit of everything
> here, although the AMD GPU driver fixes are perhaps the most
> noticeable. But there's also networking, scsi, rdma, block, you name
> it...
> 
> On the non-driver side, we've got a bump in the diffstat for the
> static call infrastructure, but that's really just code movement. The
> actual changes are more spread out than that bump would imply, and are
> generally pretty small. There's some filesystem fixes, core
> networking, and obviously the usual architecture work.
> 
> And as has been the case lately, there's the usual tooling updates -
> selftests and perf.
> 
> Full shortlog appended, it's not exactly tiny, but it's easy enough to
> scroll through to get a feel for what's been going on.
> 
> Testing appreciated as always,

Build results:
	total: 151 pass: 151 fail: 0
Qemu test results:
	total: 488 pass: 488 fail: 0

The only issue left in my testing is the warning in nosmp parisc code.

WARNING: CPU: 0 PID: 1 at fs/sysfs/group.c:115 internal_create_group+0x360/0x394

This problem is fixed in linux-next with
https://lore.kernel.org/all/20220401203114.348053-1-deller@gmx.de/
which should hopefully find its way into mainline soon.

Guenter

  reply	other threads:[~2022-04-11  4:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  0:54 Linux 5.18-rc2 Linus Torvalds
2022-04-11  4:58 ` Guenter Roeck [this message]
2022-04-11  5:12   ` Linus Torvalds
2022-04-11 10:35 ` Build regressions/improvements in v5.18-rc2 Geert Uytterhoeven
2022-04-11 10:42   ` Geert Uytterhoeven
2022-04-11 18:15     ` Kalle Valo
2022-04-12  7:09       ` Geert Uytterhoeven
2022-04-12  7:58         ` Kalle Valo
2022-04-11 23:35     ` Randy Dunlap

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=20220411045822.GA295401@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).