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.14-rc2
Date: Mon, 19 Jul 2021 07:04:37 -0700	[thread overview]
Message-ID: <20210719140437.GA2178213@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjYghA5O+ZsWKVNApMK3j4V1EibO5P+c4MrHnqp8YhY=g@mail.gmail.com>

On Sun, Jul 18, 2021 at 02:32:31PM -0700, Linus Torvalds wrote:
> Often rc2 ends up being fairly small and calm - either because people
> take a breather after the merge window, or because it takes a while
> for people to start reporting bugs.
> 
> Not so this time.
> 
> At least in pure number of commits, this is the biggest rc2 we've had
> during the 5.x cycle. Whether that is meaningful or not, who knows -
> it might be just random timing effects, or it might indicate that this
> release is not going to be one of those nice and calm ones. We'll just
> have to wait and see.
> 
> But it's not like anything looks super-scary, and it really is too
> early to start worrying about it, so let's just say that rc2's are
> usually smaller than this, and just leave it at that.
> 
> The changes are a bit all over the map, with gpu and networking driver
> fixes accounting for about half of the patch. But some of that is -
> again - AMD GPU header file noise, so that may not be all that
> important. The rest tends to be a mix of things: filesystem fixes,
> networking, perf tool and selftest fixes, and various random noise.
> 
> While being larger than usual, it's by no means _huge_, and anybody
> who cares about the details can easily scan the appended shortlog.
> 

Build results:
	total: 154 pass: 152 fail: 2
Failed builds:
	riscv32:allmodconfig
	riscv:allmodconfig
Qemu test results:
	total: 465 pass: 446 fail: 19
Failed tests:
	arm:z2:pxa_defconfig:nodebug:nocd:nofs:nonvme:noscsi:notests:novirt:nofdt:flash8,384k,2:rootfs
	<all riscv32>

No major change here, except that arcv2 images now build.
For reference, the riscv build problem is:

cc1: error: '4496' is not a valid offset in '-mstack-protector-guard-offset='

The patch fixing the arm boot problem is queued in pending-fixes.

There is still the warning about missing sha512 code.

[    3.581014] WARNING: CPU: 0 PID: 55 at crypto/testmgr.c:5652 alg_test.part.0+0x148/0x460
[    3.581548] alg: self-tests for drbg_nopr_hmac_sha512 (stdrng) failed (rc=-22)

The patch fixing this problem is queued in linux-next.

Guenter

      reply	other threads:[~2021-07-19 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 21:32 Linus Torvalds
2021-07-19 14:04 ` 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=20210719140437.GA2178213@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: Linux 5.14-rc2' \
    /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

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).