[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwdd30eBsnMLB=ncExY0-P=eAsxkn_O6ir10JUyVSYdhA@mail.gmail.com>
Date: Sun, 5 Mar 2017 13:41:04 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Linux 4.11-rc1
So two weeks have passed, the merge window is over, and 4.11-rc1 has
been tagged and pushed out.
This looks like a fairly regular release. It's on the smallish side,
but mainly just compared to 4.9 and 4.10 - so it's not really
_unusually_ small (in recent kernels, 4.1, 4.3, 4.5, 4.7 and now 4.11
all had about the same number of commits in the merge window).
It _does_ feel like there was more stuff that I was asked to pull than
was in linux-next. That always happens, but seems to have happened
more now than usually. Comparing to the linux-next tree at the time of
the 4.10 release, almost 18% of the non-merge commits were not in
Linux-next. That seems higher than usual, although I guess Stephen
Rothwell has actual numbers from past merges.
Now, about a quarter of the patches that weren't in linux-next do end
up having the same patch ID as something that was, so some of it was
due to just rebasing. But still - we have about 13% of the merge
window that wasn't in linux-next when 4.10 was released.
Looking at the sources of that, there's a few different classes:
- fixes.
This is obviously ok and inevitable. I don't expect everything to
have been in linux-next, after all.
- the statx() systen call thing.
Yeah, I'll allow this one too, because quite frankly, the first
version of that patch was posted over six years ago.
- there's the quite noticeable <linux/sched.h> split-up series
This one was posted and discussed before the merge window, and
needed to be merged late (and even then caused some conflicts). So it
had real reasons for late inclusion.
- a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out.
That last case is what I found rather annoying this merge window.
In particular, if you cannot follow the simple merge window rules
(this whole two-week merge window and linux-next process has been in
place over a decade), at least make the end result look good. Make it
all look easy and problem-free. Make it look like you know what you're
doing, and make damn sure the code was tested exhaustively some other
way.
Because if you bypass the linux-next sanity checks, you had better
have your own sanity checks that you replaced them with. Or you just
need to be _so_ good that nobody minds you bypassing them, and nobody
ever notices your shortcuts.
Saying "screw all the rules and processes we have in place to verify
things", and then sending me crap that doesn't even build for me is
_not_ acceptable.
You people know who you are. Next merge window I will not accept
anything even remotely like that. Things that haven't been in
linux-next will be rejected, and since you're already on my shit-list
you'll get shouted at again.
Linus
---
Al Viro (4):
vfs sendmsg updates
vfs pile two
vfs 'statx()' update
misc final vfs updates
Alex Williamson (1):
VFIO updates
Alexandre Belloni (1):
RTC updates
Andrew Morton (3):
updates
more updates
yet more updates
Anna Schumaker (1):
NFS client updates
Arnd Bergmann (8):
ARM SoC non-urgent fixes
ARM SoC platform updates
ARM SoC 64-bit updates
ARM SoC defconfig updates
ARM DT updates
ARM 64-bit DT updates
ARM SoC driver updates
ARM SoC late DT updates
Bartlomiej Zolnierkiewicz (1):
fbdev updates
Bjorn Andersson (2):
remoteproc updates
rpmsg updates
Bjorn Helgaas (2):
PCI updates
PCI fixes
Bob Peterson (1):
GFS2 fix
Borislav Petkov (1):
EDAC updates
Brian Norris (1):
MTD updates
Bruce Fields (1):
nfsd updates
Chris Mason (2):
btrfs updates
more btrfs updates
Corey Minyard (1):
IPMI updates
Dan Williams (1):
libnvdimm fixes
Darren Hart (1):
x86 platform driver updates
Darrick Wong (1):
xfs updates
Dave Airlie (3):
drm updates
drm fixes
drm AST2500 support
David Miller (6):
networking updates
networking fixes
sparc updates
networking fixes
IDE updates
networking fixes
Dmitry Torokhov (1):
input updates
Doug Ledford (3):
rdma updates
Mellanox rdma updates
rdma DMA mapping updates
Eric Biederman (1):
namespace updates
Geert Uytterhoeven (1):
m68k updates
Greg KH (6):
USB/PHY updates
char/misc driver updates
driver core updates
staging/iio driver updates
tty/serial driver updates
staging/IIO driver fixes
Greg Ungerer (1):
m68nommu update
Guenter Roeck (3):
hwmon updates
watchdog updates
more watchdog updates
Helge Deller (1):
parisc fixes and cleanups
Herbert Xu (2):
crypto update
crypto fixes
Ilya Dryomov (1):
ceph updates
Ingo Molnar (23):
debugobjects updates
RCU updates
EFI updates
perf updates
RAS updates
scheduler updates
locking updates
x86 apic changes
x86 asm update
x86 boot updates
x86 cleanups
x86 cpufeature updates
x86 fpu updates
x86 microcode updates
x86 mm updates
x86 platform updates
objtool fixes
locking fixes
perf fixes
scheduler fixes
x86 fixes
objtool relocation fixes
sched.h split-up
Jacek Anaszewski (1):
LED updates
Jaegeuk Kim (1):
f2fs updates
James Bottomley (2):
SCSI updates
more SCSI updates
James Hogan (1):
MIPS updates
James Morris (3):
security layer updates
seccomp fix
security subsystem fixes
Jan Kara (1):
UDF fixes and cleanups
Jens Axboe (3):
block layer updates
block updates and fixes
block layer fixes
Jessica Yu (1):
modules updates
Jiri Kosina (3):
livepatching updates
HID updates
HID fix
Joerg Roedel (3):
IOMMU UPDATES
IOMMU fix
IOMMU fixes
Jonathan Corbet (2):
documentation updates
documentation fixes
Juergen Gross (1):
xen updates
Kees Cook (5):
pstore updates
usercopy test updates
rodata updates
gcc-plugins updates
usercopy test fix
Lee Jones (2):
MFD updates
backlight updates
Linus Walleij (2):
pin control updates
GPIO updates
Mark Brown (3):
regmap updates
regulator updates
spi updates
Martin Schwidefsky (2):
s390 updates
more s390 updates
Matthew Wilcox (1):
IDR rewrite
Mauro Carvalho Chehab (1):
media updates
Max Filippov (1):
Xtensa updates
Michael Ellerman (2):
powerpc updates
more powerpc updates
Michael Tsirkin (1):
vhost updates
Mike Marshall (1):
orangefs updates
Mike Snitzer (2):
device mapper updates
device mapper fixes
Miklos Szeredi (2):
overlayfs updates
fuse update
Nicholas Bellinger (1):
SCSI target updates
Paolo Bonzini (1):
KVM updates
Paul Gortmaker (1):
exception table module split
Paul Moore (1):
audit updates
Petr Mladek (1):
printk updates
Radim Krčmář (1):
more KVM updates
Rafael Wysocki (5):
device property updates
power management updates
ACPI updates
ACPI fix
turbostat utility updates
Rob Herring (1):
DeviceTree updates
Robert Peterson (1):
GFS2 updates
Russell King (1):
ARM updates
Sebastian Reichel (1):
power supply and reset updates
Shaohua Li (1):
md updates
Shuah Khan (2):
Kselftest update
kselftest fix
Stafford Horne (1):
OpenRISC updates
Stephen Boyd (1):
clk updates
Steve French (2):
CIFS/SMB3 updates
SMB3 fixes
Steven Rostedt (3):
tracing updates
another tracing update
ktest updates
Takashi Iwai (2):
sound updates
sound fixes
Ted Ts'o (2):
fscrypt updates
ext4 updates
Tejun Heo (4):
libata updates
percpu update
cgroup updates
workqueue update
Thierry Reding (1):
pwm updates
Thomas Gleixner (2):
timer updates
irq updates
Ulf Hansson (1):
MMC updates
Vineet Gupta (1):
ARC updates
Vinod Koul (1):
dmaengine updates
Will Deacon (2):
arm64 updates
arm64 fixes
Wolfram Sang (1):
i2c updates
Zhang Rui (1):
thermal management updates
Powered by blists - more mailing lists