archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Linux Kernel Mailing List <>
Subject: Linux 6.1-rc1
Date: Sun, 16 Oct 2022 16:01:33 -0700	[thread overview]
Message-ID: <> (raw)

You all know the drill: it's Sunday afternoon, the two weeks of merge
window are over, and now we're supposed to start calming things down.

This isn't actually shaping up to be a particularly large release: we
"only" have 11.5k non-merge commits during this merge window, compared
to 13.5k last time around. So not exactly tiny, but smaller than the
last few releases. At least in number of commits.

That said, we've got a few core things that have been brewing for a
long time, most notably the multi-gen LRU VM series, and the initial
Rust scaffolding (no actual real Rust code in the kernel yet, but the
infrastructure is there).

And hey, this merge window was full of surprises for other reasons too
- my main machine was basically out of action for a couple of days
because it suddenly started showing memory problems, and it took me a
couple of days to get that sorted out (to a large degree because it
was unexpected and I started out blaming a kernel bug for the memory
corruption). All sorted out now, but it caused some frustration.

Talking about frustration, let me just say that after I got my machine
sorted out and caught up with the merge window, I wass somewhat
frustrated with various late pull requests. I've mentioned this
before, but it's _really_ quite annoying to get quite a few pull
requests in the last few days of the merge window.

Yes, the merge window is two weeks, but that's very much to allow me
time to look things over, not "two weeks to hurriedly put together a
branch that you send Linus on Friday of the second week". The whole
"do an all-nighter to get the paper in the day before the dealine" is
something that should have gone out the window after highschool. Not
for kernel development.

The rule is that things that get sent to me should be ready *before*
the merge window opens, not be made ready during the merge window.
With some slack for "life happens", of course, but I really get the
feeling that a few people treat the end of the merge window as a
deadline, missing the whole "it was supposed to be ready before the
merge window".

You know who you are.

Anyway, it's not the first time I've said this, I doubt it will be the
last. But maybe more people could take it to heart, ok?

Enough kvetching, let's get this party calmed down. The merge window
may not be the biggest ever, but it's certainly big enough that the
shortlog is much too big to post, and below is just my usual merge
log. For all the gory details, please refer to the git tree.

Please get the testing started,



Al Viro (7):
    coredump fix
    vfs inode update
    vfs d_path updates
    vfs file updates
    misc tomoyo changes
    vfs constification updates
    vfs tmpfile updates

Al Vrio (1):
    file_inode() updates

Alex Williamson (1):
    VFIO updates

Alexandre Belloni (2):
    i3c updates
    RTC updates

Andreas Gruenbacher (2):
    gfs2 updates
    gfs2 debugfs updates

Andrew Morton (4):
    MM updates
    non-MM updates
    misc hotfixes
    more MM updates

Anna Schumaker (1):
    NFS client updates

Ard Biesheuvel (1):
    EFI updates

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

Arnd Bergmann (7):
    ARM defconfig updates
    ARM driver updates
    ARM devicetree updates
    ARM SoC updates
    asm-generic updates
    ARM SoC fixes
    asm-generic fix

Bartosz Golaszewski (1):
    gpio updates

Benjamin Tissoires (1):
    HID updates

Bjorn Andersson (2):
    rpmsg updates
    remoteproc updates

Bjorn Helgaas (2):
    pci updates
    pci fix

Borislav Petkov (14):
    EDAC updates
    x86 platform update
    x86 RTC cleanups
    x86 SGX update
    x86 cpu updates
    x86 RAS updates
    x86 APIC update
    x86 core fixes
    x86 asm update
    misc x86 fixes
    x86 paravirt fix
    x75 microcode loader updates
    x86 cache resource control updates
    x86 cleanups

Casey Schaufler (1):
    smack updates

Catalin Marinas (2):
    arm64 updates
    arm64 fixes

Christian Brauner (2):
    vfs acl updates
    fatfs vfsuid conversion

Christoph Hellwig (1):
    dma-mapping updates

Chuck Lever (2):
    nfsd updates
    more nfsd updates

Corey Minyard (1):
    IPMI updates

Damien Le Moal (1):
    ata updates

Dan Williams (1):
    nvdimm updates

Darrick Wong (1):
    iomap updates

Dave Airlie (3):
    drm updates
    drm fix
    more drm updates

Dave Chinner (1):
    xfs updates

Dave Hansen (1):
    x86 mm updates

David Sterba (2):
    btrfs updates
    affs update

David Teigland (1):
    dlm updates

Dmitry Torokhov (1):
    input updates

Dominik Brodowski (1):
    PCMCIA updates

Dominique Martinet (1):
    9p updates

Eric Biederman (4):
    kthread update
    mqueue fix
    ptrace update
    ucounts update

Eric Biggers (3):
    fscrypt updates
    fsverity updates
    STATX_DIOALIGN support

Gao Xiang (1):
    erofs updates

Geert Uytterhoeven (1):
    m68k updates

Greg KH (5):
    tty/serial driver updates
    USB / Thunderbolt updates
    driver core updates
    char/misc and other driver updates
    staging driver updates

Greg Ungerer (1):
    m68knommu updates

Guenter Roeck (1):
    hwmon updates

Hans de Goede (1):
    x86 platform driver updates

Helge Deller (2):
    fbdev updates
    parisc updates

Herbert Xu (1):
    crypto updates

Huacai Chen (1):
    LoongArch updates

Ilya Dryomov (1):
    ceph updates

Ingo Molnar (5):
    scheduler updates
    perf events updates
    locking updates
    objtool updates
    PSI updates

Jaegeuk Kim (1):
    f2fs updates

Jakub Kicinski (2):
    networking updates
    networking fixes

James Bottomley (1):
    SCSI updates

Jan Kara (2):
    fsnotify updates
    ext2, udf, reiserfs, and quota updates

Jarkko Sakkinen (1):
    tpm updates

Jason Donenfeld (2):
    random number generator updates
    more random number generator updates

Jason Gunthorpe (1):
    rdma updates

Jassi Brar (1):
    mailbox updates

Jean Delvare (1):
    dmi updates

Jens Axboe (5):
    io_uring updates
    block updates
    passthrough updates
    more io_uring updates
    more block updates

Joerg Roedel (1):
    iommu updates

Jonathan Corbet (2):
    documentation updates
    documentation fixes

Juergen Gross (1):
    xen updates

Kees Cook (4):
    Rust introductory support
    execve updates
    kcfi updates
    kernel hardening updates

Lee Jones (2):
    backlight update
    MFD 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 (2):
    Kbuild updates
    Kbuild fixes

Mauro Carvalho Chehab (1):
    media updates

Max Filippov (1):
    xtensa updates

Michael Ellerman (2):
    powerpc updates
    powerpc fixes

Michael Tsirkin (2):
    virtio updates
    virtio fixes

Michal Simek (1):
    microblaze updates

Mickaël Salaün (1):
    landlock updates

Mike Marshall (1):
    orangefs update

Mike Rapoport (1):
    memblock updates

Mimi Zohar (1):
    integrity updates

Miquel Raynal (1):
    MTD updates

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

Paolo Bonzini (2):
    kvm updates
    more kvm updates

Paul McKenney (3):
    nolibc updates
    LKMM (Linux Kernel Memory Model) updates
    RCU updates

Paul Moore (3):
    SELinux updates
    LSM updates
    audit updates

Pavel Machek (1):
    LED updates

Petr Mladek (2):
    printk updates
    livepatching updates

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

Richard Weinberger (2):
    UML updates
    UBI and UBIFS updates

Rob Herring (2):
    devicetree updates
    devicetree fixes

Russell King (2):
    ARM fixes
    ARM updates

Sebastian Reichel (2):
    HSI updates
    power supply and reset updates

Shuah Khan (4):
    Kselftest updates
    KUnit updates
    more Kselftest updates
    more KUnit updates

Stafford Horne (1):
    OpenRISC updates

Stephen Boyd (2):
    clk updates
    more clk updates

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

Steven Rostedt (2):
    tracing updates
    tracing fixes

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 (3):
    preempt RT updates
    timer updates
    interrupt updates

Tzung-Bi Shih (1):
    chrome platform updates

Ulf Hansson (2):
    MMC updates
    MMC fixes

Vasily Gorbik (2):
    s390 updates
    more s390 updates

Vinod Koul (3):
    dmaengine updates
    phy updates
    soundwire updates

Vlastimil Babka (2):
    slab fixes
    slab hotfix

Wei Liu (1):
    hyperv updates

Wim Van Sebroeck (1):
    watchdog updates

Wolfram Sang (2):
    i2c updates
    more i2c updates

Yury Norov (1):
    bitmap updates

             reply	other threads:[~2022-10-16 23:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 23:01 Linus Torvalds [this message]
2022-10-17  1:53 ` linux-next: stats for 6.1-rc1 (was: Linux 6.1-rc1) Stephen Rothwell
2022-10-17  2:58 ` 6.1rc1: NFS memcpy warning on mount Dave Jones
2022-10-17  3:58   ` Bagas Sanjaya
2022-10-17  4:17     ` Kees Cook
2022-10-17  4:20       ` Bagas Sanjaya
2022-10-17  4:57   ` Kees Cook
2022-10-17 12:34 ` Linux 6.1-rc1 Guenter Roeck
2022-10-17 17:39   ` Linus Torvalds
2022-10-17 18:28     ` Guenter Roeck
2022-10-17 18:54       ` Conor Dooley
2022-10-18  0:03     ` Jason A. Donenfeld
2022-12-25 19:05 Zeno Davatz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

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