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.15-rc4
Date: Mon, 4 Oct 2021 19:28:49 -0700 [thread overview]
Message-ID: <20211005022849.GA1391135@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wifo=ocAVFtoutuLQvqYyNz1r014uJD8TRPJKpVaPLrRQ@mail.gmail.com>
On Sun, Oct 03, 2021 at 02:26:40PM -0700, Linus Torvalds wrote:
> This release continues to look pretty normal after the initial
> hiccups. At least going purely by number of commits, we're right smack
> dab in the middle of the normal range for this time in the release
> cycle, and the diffstat looks fairly normal too. A bit less
> driver-heavy than usual, perhaps, but nothing big, and nothing that
> makes me go "that's strange".
>
> One thing standing out in the diffs might be the m68k 'set_fs()'
> removal - not really a regression fix, but it has been pending for a
> while, and it turned out that the problems attributed to it were due
> to an entirely unrelated m68k signal handling issue. So with that
> fixed, we could get rid of set_fs from another architecture. There's a
> few more architectures I'd like to see it removed from, but all the
> actively maintained ones have already removed it, so on the whole
> set_fs really is a thing of the past, only used by legacy
> architectures.
>
> Anyway, about a third of the diff is drivers (net, sound, rdma, gpu),
> with the rest being a mix of arch updates (the m68k set_fs stuff and
> some kvm patches), tooling (mostly selftest updates), filesystem code
> and core networking.
>
> The appended shortlog gives you more details, but if you really want
> to dig into it, go for the git tree.
>
> Go test,
Looking pretty good here.
Build results:
total: 153 pass: 153 fail: 0
Qemu test results:
total: 480 pass: 480 fail: 0
Guenter
prev parent reply other threads:[~2021-10-05 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 21:26 Linux 5.15-rc4 Linus Torvalds
2021-10-05 2:28 ` 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=20211005022849.GA1391135@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).