From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.0-rc5
Date: Mon, 12 Sep 2022 12:59:05 +0100 [thread overview]
Message-ID: <CADVatmPAkS9ope2oOQHB8nKc_sx2MM9P6aSqxwdA5sgyqvCvvQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wjG0js0MpsoH3-yvp05u_gXHu+uhkvqdAZDVb=9xUmX=g@mail.gmail.com>
On Sun, Sep 11, 2022 at 11:05 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> It's Sunday afternoon, time for another -rc release.
>
> Things look fairly normal for the rc5 timeframe, at least in number of
> commits, and in the diffstat.
>
> A bit over half the diff is drivers: GPU, rdma, iommu, networking,
> sound, scsi... A little bit of everything.
>
> The rest is the usual random fixes, with i2c doc updates standing out,
> but also various DT updates, a few filesystem fixes (btrfs and erofs),
> some core networking, and some tooling (perf and selftests).
>
> Nothing looks particularly scary, so jump right in.
clang build failure as reported in [1] is still there. Nathan has
posted a patch series at [2] to fix it, but it has not landed yet.
[1]. https://lore.kernel.org/lkml/YuwRyQYPCb1FD+mr@debian/#t
[2]. https://lore.kernel.org/all/20220830203409.3491379-1-nathan@kernel.org/
--
Regards
Sudip
next prev parent reply other threads:[~2022-09-12 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 21:03 Linux 6.0-rc5 Linus Torvalds
2022-09-12 9:13 ` Build regressions/improvements in v6.0-rc5 Geert Uytterhoeven
2022-09-12 9:22 ` Geert Uytterhoeven
2022-09-20 20:23 ` Helge Deller
2022-09-20 20:29 ` Randy Dunlap
2022-09-20 21:07 ` Helge Deller
2022-09-21 18:29 ` Helge Deller
2022-09-23 11:52 ` Michael Ellerman
2022-09-12 11:59 ` Sudip Mukherjee [this message]
2022-09-12 14:01 ` Linux 6.0-rc5 Linus Torvalds
2022-09-12 16:44 ` Guenter Roeck
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=CADVatmPAkS9ope2oOQHB8nKc_sx2MM9P6aSqxwdA5sgyqvCvvQ@mail.gmail.com \
--to=sudipm.mukherjee@gmail.com \
--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).