linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 6.0-rc1
Date: Sun, 14 Aug 2022 16:41:33 -0700	[thread overview]
Message-ID: <CAHk-=wgRFjPHV-Y_eKP9wQMLFDgG+dEUHiv5wC17OQHsG5z7BA@mail.gmail.com> (raw)

So here we are, two weeks later, and the merge window has closed.

People are chasing down one active bug, and I'm sure there are others
hiding that just need more people to do testing, but that's kind of
the point of rc1: all the big changes have been merged, and now we
need to calm it down and chase down any problems.

Despite the major number change, there's nothing fundamentally
different about this release - I've long eschewed the notion that
major numbers are meaningful, and the only reason for a "hierarchical"
numbering system is to make the numbers easier to remember and
distinguish. Which is why when the minor number gets to around 20 I
prefer to just increment the major number instead and reset to
something smaller.

"Nothing fundamentally different about this release" obviously doesn't
mean there aren't lots of changes, though. There's about 13.5k
non-merge commits in here (and 800+ merges), so 6.0 looks to be
another fairly sizable release.

I actually was hoping that we'd get some of the first rust
infrastructure, and the multi-gen LRU VM, but neither of them happened
this time around. There's always more releases. But there's a lot of
continued development pretty much all over the place, with the
"shortlog" being much too long to post and thus - as always for rc1
notices - below only contains my "merge log". You can definitely get a
kind of high-level overview by just scanning that, but obviously it's
worth once again pointing out that the people mentioned in the merge
log are just the maintainers I pull from, and there's more than 1700
developers involved when you start looking at the full details in the
git tree.

And, once again, this is one of those releases where you should not
look at the diffstat too closely, because more than half of it is yet
another AMD GPU register dump. And the Habanalabs Gaudi2 people want
to play in that space too, but they don't reach quite the same lofty
results that the AMD GPU people  have become so famous for. I'm sure
it's just a matter of time.

The CPU people also show up in the JSON files that describe the perf
events, but they look absolutely tiny compared to the 'asic_reg'
auto-generated GPU and AI hardware definitions.

So just avert your eyes from those parts if you decide that you
actually want to look at the diffs themselves. Once you do that, the
stats look pretty normal, with roughly 60% driver updates (all over,
but gpu, networking and sound are the big updates - again, that's
pretty much par for the course). The rest is a mix of arch updates,
filesystems, tooling, and just random changes all over.

In all its glory (so all those AMD GPU hardware definitions etc included), it's

 13099 files changed, 1280295 insertions(+), 341210 deletions(-)

just because I was curious and looked.

Oh, and after I had already decided to call this kernel 6.0, a few
Chinese developers piped up and pointed out that "5.20" is a more
wholesome version of the Western "4.20" internet-famous number. So if
you want to call this "Linux 5.20", go right ahead. Because the kernel
version  numbers really are entirely made up and have no intrinsic
meaning.

But whatever you call it, please help test this, so that we can get it
all in shape for the final release (hopefully early October).

                 Linus

---

Al Viro (9):
    vfs namei updates
    vfs lseek updates
    vfs dcache updates
    vfs iov_iter updates
    copy_to_iter_mc fix
    9p iov_iter fix
    more iov_iter updates
    /proc/mounts fix
    vfs lseek fix

Alex Williamson (2):
    VFIO updates
    another VFIO update

Alexander Gordeev (1):
    s390 updates

Alexandre Belloni (1):
    RTC updates

Andreas Gruenbacher (1):
    gfs2 updates

Andrew Morton (3):
    MM updates
    misc updates
    remaining MM updates

Ard Biesheuvel (2):
    EFI updates
    efivars sysfs interface removal

Arnaldo Carvalho de Melo (2):
    perf tools updates
    more perf tool updates

Arnd Bergmann (8):
    ARM SoC updates
    ARM SoC drivers
    ARM DT updates
    ARM SoC defconfig updates
    ARM new SoC support
    ARM boardfile deprecation
    more ARM SoC updates
    asm-generic updates

Bartosz Golaszewski (1):
    gpio updates

Bjorn Andersson (4):
    hwspinlock updates
    rpmsg updates
    remoteproc updates
    rpmsg fixes

Bjorn Helgaas (1):
    pci updates

Borislav Petkov (11):
    RAS update
    x86 vmware cleanup
    x86 cleanup
    x86 mm updates
    x86 fpu update
    x86 cpu updates
    misc x86 updates
    x86 core updates
    x86 build updates
    x86 kdump updates
    x86 eIBRS fixes

Casey Schaufler (1):
    msack updates

Christian Brauner (3):
    fs idmapping updates
    acl updates
    setgid updates

Christoph Hellwig (1):
    dma-mapping updates

Chuck Lever (1):
    nfsd updates

Damien Le Moal (2):
    zonefs update
    ATA updates

Dan Williams (1):
    cxl updates

Darrick Wong (4):
    iomap updates
    xfs updates
    more iomap updates
    more xfs updates

Dave Airlie (2):
    drm updates
    drm fixes

Dave Hansen (1):
    x86 SGX updates

David Howells (2):
    AFS fixes
    fscache updates

David Sterba (2):
    btrfs updates
    affs fix

David Teigland (1):
    dlm updates

Dmitry Torokhov (1):
    input updates

Dominique Martinet (1):
    9p updates

Eric Biggers (1):
    fsverity update

Gao Xiang (1):
    erofs updates

Geert Uytterhoeven (1):
    m68k updates

Greg KH (6):
    char / misc driver updates
    driver core / kernfs updates
    USB / Thunderbolt updates
    staging driver updates
    SPDX updates
    tty / serial driver updates

Greg Ungerer (1):
    m68knommu fixes

Guenter Roeck (2):
    hwmon updates
    hwmon fixes

Guo Ren (1):
    csky updates

Gustavo Silva (1):
    uapi flexible array update

Hans de Goede (1):
    x86 platform driver updates

Hans-Christian Noren Egtvedt (1):
    AVR32 updates

Helge Deller (2):
    parisc updates
    fbdev updates

Herbert Xu (1):
    crypto updates

Huacai Chen (1):
    LoongArch updates

Ilya Dryomov (1):
    ceph updates

Ingo Molnar (8):
    scheduler updates
    locking updates
    perf events updates
    perf fixes
    scheduler fixes
    x86 fixes
    x86 fix
    timer fixes

Jaegeuk Kim (1):
    f2fs updates

Jakub Kicinski (1):
    networking fixes

James Bottomley (2):
    SCSI updates
    more SCSI updates

Jan Kara (2):
    ext2 and reiserfs updates
    fsnotify updates

Jarkko Sakkinen (1):
    tpm updates

Jason Donenfeld (1):
    random number generator updates

Jason Gunthorpe (1):
    rdma updates

Jassi Brar (1):
    mailbox updates

Jeff Layton (1):
    file locking updates

Jens Axboe (7):
    io_uring updates
    io_uring buffered writes support
    io_uring zerocopy support
    block updates
    block driver updates
    io_uring fixes
    block fixes

Jiri Kosina (1):
    HID updates

Joerg Roedel (1):
    iommu updates

John Johansen (1):
    AppArmor updates

Jon Mason (1):
    NTB updates

Jonathan Corbet (1):
    documentation updates

Juergen Gross (2):
    xen updates
    more xen updates

Julia Lawall (1):
    coccinelle semantic patch updates

Kees Cook (4):
    pstore updates
    seccomp update
    execve updates
    hardening updates

Lee Jones (2):
    MFD updates
    backlight updates

Len Brown (1):
    turbostat updates

Linus Walleij (1):
    pin control updates

Luis Chamberlain (2):
    module updates
    sysctl updates

Mark Brown (3):
    regmap updates
    regulator updates
    spi updates

Masahiro Yamada (1):
    Kbuild updates

Matthew Wilcox (2):
    XArray/IDR updates
    folio updates

Mauro Carvalho Chehab (1):
    media updates

Max Filippov (1):
    xtensa updates

Micah Morton (1):
    SafeSetID updates

Michael Ellerman (2):
    powerpc updates
    powerpc fixes

Michael Tsirkin (1):
    virtio updates

Michal Simek (1):
    microblaze updates

Mike Rapoport (1):
    memblock updates

Mike Snitzer (3):
    device mapper updates
    more device mapper updates
    device mapper fixes

Miklos Szeredi (2):
    overlayfs update
    fuse updates

Mimi Zohar (1):
    integrity updates

Namjae Jeon (1):
    exfat updates

Palmer Dabbelt (2):
    RISC-V updates
    more RISC-V updates

Paolo Abeni (1):
    networking changes

Paolo Bonzini (2):
    kvm updates
    more kvm updates

Paul McKenney (2):
    RCU updates
    nolibc updates

Paul Moore (3):
    selinux updates
    audit updates
    LSM update

Pavel Machek (1):
    LED updates

Petr Mladek (2):
    printk updates
    livepatching update

Rafael Wysocki (6):
    ACPI updates
    power management updates
    thermal control updates
    more thermal control updates
    more power management updates
    more ACPI updates

Richard Weinberger (2):
    UML updates
    MTD updates

Rob Herring (2):
    devicetree updates
    devicetree fixes

Russell King (1):
    ARM updates

Sebastian Reichel (1):
    power supply and reset updates

Shuah Khan (2):
    KUnit updates
    Kselftest updates

Stafford Horne (1):
    OpenRISC updates

Stephen Boyd (1):
    clk updates

Steve French (3):
    cifs updates
    ksmbd updates
    more cifs updates

Steven Rostedt (2):
    real time analysis tool (rtla) updates
    tracing updates

Takashi Iwai (2):
    sound updates
    sound fixes

Ted Ts'o (1):
    ext4 updates

Tejun Heo (1):
    cgroup updates

Thierry Reding (1):
    pwm updates

Thomas Bogendoerfer (1):
    MIPS updates

Thomas Gleixner (2):
    timer updates
    irq updates

Trond Myklebust (1):
    NFS client updates

Tzung-Bi Shih (1):
    chrome platform updates

Ulf Hansson (1):
    MMC updates

Vinod Koul (1):
    dmaengine updates

Vlastimil Babka (1):
    slab updates

Wei Liu (1):
    hyperv updates

Will Deacon (1):
    arm64 updates

Wim Van Sebroeck (1):
    watchdog updates

Wolfram Sang (2):
    i2c updates
    more i2c updates

Yury Norov (1):
    bitmap updates

             reply	other threads:[~2022-08-14 23:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14 23:41 Linus Torvalds [this message]
2022-08-15  1:23 ` Linux 6.0-rc1 Kirill A. Shutemov
2022-08-15  2:27   ` Steven Rostedt
2022-08-15  2:50 ` linux-next: stats (Was: Linux 6.0-rc1) Stephen Rothwell
2022-08-17 14:41   ` Geert Uytterhoeven
2022-08-15 18:04 ` Build regressions/improvements in v6.0-rc1 Geert Uytterhoeven
2022-08-15 18:10   ` Geert Uytterhoeven
2022-08-15 23:48 ` Linux 6.0-rc1 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='CAHk-=wgRFjPHV-Y_eKP9wQMLFDgG+dEUHiv5wC17OQHsG5z7BA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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).