Linux 4.3-rc1 - merge window closed

From: Linus Torvalds
Date: Sat Sep 12 2015 - 20:09:11 EST

So it's been fairly quiet today (which is normal: there tends to be a
small rush of stuff on the last Friday of the merge window is closing,
but weekends tend to calm down), and I decided that I'm not interested
in catering to anything that comes in tomorrow, and I might as well
just close the merge window and do the -rc1 release.

I had expected 4.3 to be somewhat smaller after that pretty big 4.2,
but it's not particularly small - pretty average in size, in fact.
Everything looks fairly normal, in fact, with about 70% of the changes
being drivers, 10% architecture updates, and the remaining 20% are
spread out (filesystems, networking, tooling, documentation, mm and
"core" kernel updates etc).

On the driver side, the GPU drivers remain a noticeable chunk, partly
because of the Nouveau updates that missed 4.2, so there's effectively
two releases worth of updates there. But there's driver updates to
pretty much all the other driver subsystems too. So there's
networking drivers (wired and wireless), staging, media, crypto,
pinctrl, you name it.

The architecture updates are about half arm (devicetree updates are
noticeable), with half being spread out (x86, mips, arm64, powerpc,

On the filesystem side, the bulk of the changes (in lines of code) is
the removal of the ext3 filesystem (with ext4 remaining to support
ext3 layouts - but the separate ext3 codebase is gone). But there are
misc updates all over: f2fs, btrfs, nfs, xfs, ufs, gfs2, proc...

As usual, the full log is much too big to post, so I'm appending my
merge-log that gives you a flavor of who I pulled from and what the
big picture changes are..

Go out and test,



Al Viro (1):
vfs updates

Alexandre Belloni (1):
RTC updates

Andrew Morton (4):
second patch-bomb
third patch-bomb
fourth patch-bomb

Bjorn Helgaas (1):
PCI updates

Bob Peterson (1):
GFS2 updates

Borislav Petkov (1):
EDAC fixes

Brian Norris (2):
MTD updates
more MTD updates

Bruce Fields (1):
nfsd updates

Chris Mason (2):
btrfs updates
btrfs cleanups and fixes

Chris Metcalf (1):
tile updates

Chris Zankel (1):
xtensa updates

Corey Minyard (1):
IPMI updates

Dan Williams (1):
libnvdimm updates

Darren Hart (1):
x86 platform driver updates

Dave Airlie (2):
drm updates
drm fixes

Dave Chinner (1):
xfs updates

David Miller (2):
networking updates
networking fixes

David Teigland (1):
dlm updates

David Vrabel (2):
xen updates
xen terminology fixes

Dmitry Torokhov (2):
input subsystem updates
more input updates

Doug Ledford (1):
inifiniband/rdma updates

Eric Biederman (1):
user namespace updates

Eric Van Hensbergen (1):
9p updates

Geert Uytterhoeven (1):
m68k updates

Greg KH (6):
char/misc driver patches
driver core updates
staging driver updates
tty/serial driver updates
USB updates
tty driver reverts

Greg Ungerer (1):
m68k/colfire fixes

Guenter Roeck (1):
hwmon updates

Helge Deller (1):
parisc updates

Herbert Xu (2):
crypto updates
crypto fix

Ingo Molnar (19):
RCU updates
inlining tuning
liblockdep fixes
x86/kasan changes
perf updates
RAS updates
scheduler updates
scheduler fix
NOHZ updates
x86 asm changes
x86 boot updates
x86 build fixlet
x86 init code fixlet
x86 cpu updates
x86 irq fixlet
x86 mm updates
x86 core platform updates
locking and atomic updates
perf fixes

Jacek Anaszewski (1):
LED updates

Jaegeuk Kim (1):
f2fs updates

James Bottomley (2):
first round of SCSI updates
second round of SCSI updates

James Hogan (1):
metag updates

James Morris (1):
security subsystem updates

Jan Kara (1):
ext3 removal, quota & udf fixes

Jassi Brar (1):
mailbox updates

Jens Axboe (4):
core block updates
block driver updates
SG updates
blk-cg updates

Jesper Nilsson (1):
CRIS updates

Jiri Kosina (3):
HID updates
livepatching fix
trivial tree updates

Joerg Roedel (1):
iommu updates for

Jon Mason (1):
NTB fixes

Jonathan Corbet (1):
documentation updates

Kevin Hilman (1):
late ARM SoC updates

Lee Jones (2):
MFD updates
backlight updates

Ley Foon Tan (1):
nios2 updates

Linus Walleij (2):
GPIO updates
pin control updates

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

Martin Schwidefsky (1):
s390 updates

Matt Turner (1):
alpha update

Mauro Carvalho Chehab (3):
media updates
edac updates
media updates

Michael Ellerman (1):
powerpc updates

Michael Tsirkin (1):
virtio updates

Michael Turquette (1):
clk updates

Michal Marek (3):
core kbuild updates
kconfig updates
misc kbuild updates

Michal Simek (1):
microblaze update

Mike Snitzer (1):
device mapper update

Mikulas Patocka (1):
hpfs upddate

Neil Brown (1):
md updates

Nicholas Bellinger (1):
SCSI target updates

Olof Johansson (7):
ARM SoC non-urgent fixes
ARM SoC cleanups
ARM SoC platform updates
ARM SoC driver updates
ARM DT updates
ARM SoC defconfig updates
ARM SoC 64-bit changes

Paolo Bonzini (2):
kvm updates
more kvm updates

Paul Moore (1):
audit update

Rafael Wysocki (2):
power management and ACPI updates
more power management and ACPI updates

Ralf Baechle (1):
MIPS updates

Richard Kuo (1):
hexagon updates

Rob Herring (1):
devicetree updates

Russell King (3):
ARM development updates
ARM pcmcia updates
NMI backtrace update

Sage Weil (1):
Ceph update

Sebastian Reichel (1):
power supply and reset changes

Shuah Khan (1):
kselftest update

Steve French (1):
cifs updates

Steven Rostedt (1):
tracing update

Takashi Iwai (2):
sound updates
sound fixes

Ted Ts'o (1):
ext4 updates

Tejun Heo (4):
libata updates
workqueue updates
percpu updates
cgroup updates

Thierry Reding (1):
pwm updates

Thomas Gleixner (5):
timer updates
irq updates
x86 apic updates
x86 clockevent update
more irq updates

Tomi Valkeinen (1):
fbdev updates

Trond Myklebust (1):
NFS client updates

Tyler Hicks (1):
ecryptfs fixes

Ulf Hansson (1):
MMC updates

Vineet Gupta (1):
ARC architecture updates

Vinod Koul (1):
dmaengine updates

Will Deacon (1):
arm64 updates

Wim Van Sebroeck (1):
watchdog updates

Wolfram Sang (1):
i2c updates

Zhang Rui (1):
thermal updates
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at