mirror of https://lore.kernel.org/lkml/
 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-rc5
Date: Mon, 2 May 2022 09:29:34 -0700	[thread overview]
Message-ID: <20220502162934.GA981862@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjUhfhaes6_hMYDQFTbGjkmA-j2ZSeXZ32H66ufRfYrmQ@mail.gmail.com>

On Sun, May 01, 2022 at 02:13:49PM -0700, Linus Torvalds wrote:
> So if rc4 last week was tiny and smaller than usual, it seems to have
> been partly timing, and rc5 is now a bit larger than usual.
> 
> But only a very tiny bit larger - certainly not outrageously so, and
> not something that worries me (admittedly partly because of that small
> rc4: it doesn't feel like we're having any more issues than usual,
> it's just that the work ended up shifting a bit to this past week).
> 
> The diffstat looks normal too, although with an odd bump for the n_gsm
> tty ldisc code. I could have sworn that thing was legacy and nobody
> used it, but apparently I would have been very wrong about that.
> 
> That small oddity aside, nothing surprising in here, with about half
> the patch being drivers (mainly networking, gpu, pincontrol, clk, usb,
> and that tty gsm thing), with the rest being the usual suspects:
> architecture fixes (kvm, some arm dts files), core networking, tools
> (both objtool and perf) and some documentation fixes. Add in a few
> random things, and you have rc5.
> 
> The shortlog is appended for people who want to see the details, but
> it honestly doesn't look very interesting.
> 
> But "interesting" isn't what we're going for - we're past the halfway
> mark in the release, and "boring" is very much what we want.
> 
> Please do test, and hopefully we don't have some silly brown-paper bug
> like the no-mmu breakage in rc4.
> 

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

We still have

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

for parisc nosmp boot tests, but that is fixed in -next and not really
critical.

Guenter

      parent reply	other threads:[~2022-05-02 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 21:13 Linus Torvalds
2022-05-02  6:53 ` Build regressions/improvements in v5.18-rc5 Geert Uytterhoeven
2022-05-02  7:14   ` Geert Uytterhoeven
2022-05-02 16:29 ` 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=20220502162934.GA981862@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®