OSDN Git Service
Stephen Rothwell [Mon, 24 Aug 2015 11:49:12 +0000 (21:49 +1000)]
Add linux-next specific files for
20150824
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Stephen Rothwell [Mon, 24 Aug 2015 11:08:05 +0000 (21:08 +1000)]
Merge branch 'akpm/master'
Levente Kurusa [Mon, 17 Aug 2015 23:54:23 +0000 (09:54 +1000)]
drivers/w1/w1_int.c: call put_device if device_register fails
Currently, memsetting and kfreeing the device is bad behaviour. The
device will have a reference count of 1 and hence can cause trouble
because it has kfree'd. Proper way to handle a failed device_register is
to call put_device right after it fails.
Signed-off-by: Levente Kurusa <levex@linux.com>
Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Mathieu Desnoyers [Mon, 17 Aug 2015 23:54:23 +0000 (09:54 +1000)]
selftests: enhance membarrier syscall test
Update the membarrier syscall self-test to match the membarrier interface.
Extend coverage of the interface. Consider ENOSYS as a "SKIP" test,
since it is a valid configuration, but does not allow testing the system
call.
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Pranith Kumar <bobby.prani@gmail.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Pranith Kumar [Mon, 17 Aug 2015 23:54:23 +0000 (09:54 +1000)]
selftests: add membarrier syscall test
Add a self test for the membarrier system call.
Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Mathieu Desnoyers [Mon, 17 Aug 2015 23:54:22 +0000 (09:54 +1000)]
sys_membarrier(): system-wide memory barrier (generic, x86)
Here is an implementation of a new system call, sys_membarrier(), which
executes a memory barrier on all threads running on the system. It is
implemented by calling synchronize_sched(). It can be used to distribute
the cost of user-space memory barriers asymmetrically by transforming
pairs of memory barriers into pairs consisting of sys_membarrier() and a
compiler barrier. For synchronization primitives that distinguish between
read-side and write-side (e.g. userspace RCU [1], rwlocks), the read-side
can be accelerated significantly by moving the bulk of the memory barrier
overhead to the write-side.
The existing applications of which I am aware that would be improved by this
system call are as follows:
* Through Userspace RCU library (http://urcu.so)
- DNS server (Knot DNS) https://www.knot-dns.cz/
- Network sniffer (http://netsniff-ng.org/)
- Distributed object storage (https://sheepdog.github.io/sheepdog/)
- User-space tracing (http://lttng.org)
- Network storage system (https://www.gluster.org/)
- Virtual routers (https://events.linuxfoundation.org/sites/events/files/slides/DPDK_RCU_0MQ.pdf)
- Financial software (https://lkml.org/lkml/2015/3/23/189)
Those projects use RCU in userspace to increase read-side speed and
scalability compared to locking. Especially in the case of RCU used by
libraries, sys_membarrier can speed up the read-side by moving the bulk of
the memory barrier cost to synchronize_rcu().
* Direct users of sys_membarrier
- core dotnet garbage collector (https://github.com/dotnet/coreclr/issues/198)
Microsoft core dotnet GC developers are planning to use the mprotect()
side-effect of issuing memory barriers through IPIs as a way to implement
Windows FlushProcessWriteBuffers() on Linux. They are referring to
sys_membarrier in their github thread, specifically stating that
sys_membarrier() is what they are looking for.
To explain the benefit of this scheme, let's introduce two example threads:
Thread A (non-frequent, e.g. executing liburcu synchronize_rcu())
Thread B (frequent, e.g. executing liburcu
rcu_read_lock()/rcu_read_unlock())
In a scheme where all smp_mb() in thread A are ordering memory accesses
with respect to smp_mb() present in Thread B, we can change each
smp_mb() within Thread A into calls to sys_membarrier() and each
smp_mb() within Thread B into compiler barriers "barrier()".
Before the change, we had, for each smp_mb() pairs:
Thread A Thread B
previous mem accesses previous mem accesses
smp_mb() smp_mb()
following mem accesses following mem accesses
After the change, these pairs become:
Thread A Thread B
prev mem accesses prev mem accesses
sys_membarrier() barrier()
follow mem accesses follow mem accesses
As we can see, there are two possible scenarios: either Thread B memory
accesses do not happen concurrently with Thread A accesses (1), or they
do (2).
1) Non-concurrent Thread A vs Thread B accesses:
Thread A Thread B
prev mem accesses
sys_membarrier()
follow mem accesses
prev mem accesses
barrier()
follow mem accesses
In this case, thread B accesses will be weakly ordered. This is OK,
because at that point, thread A is not particularly interested in
ordering them with respect to its own accesses.
2) Concurrent Thread A vs Thread B accesses
Thread A Thread B
prev mem accesses prev mem accesses
sys_membarrier() barrier()
follow mem accesses follow mem accesses
In this case, thread B accesses, which are ensured to be in program
order thanks to the compiler barrier, will be "upgraded" to full
smp_mb() by synchronize_sched().
* Benchmarks
On Intel Xeon E5405 (8 cores)
(one thread is calling sys_membarrier, the other 7 threads are busy
looping)
1000 non-expedited sys_membarrier calls in 33s =3D 33 milliseconds/call.
* User-space user of this system call: Userspace RCU library
Both the signal-based and the sys_membarrier userspace RCU schemes
permit us to remove the memory barrier from the userspace RCU
rcu_read_lock() and rcu_read_unlock() primitives, thus significantly
accelerating them. These memory barriers are replaced by compiler
barriers on the read-side, and all matching memory barriers on the
write-side are turned into an invocation of a memory barrier on all
active threads in the process. By letting the kernel perform this
synchronization rather than dumbly sending a signal to every process
threads (as we currently do), we diminish the number of unnecessary wake
ups and only issue the memory barriers on active threads. Non-running
threads do not need to execute such barrier anyway, because these are
implied by the scheduler context switches.
Results in liburcu:
Operations in 10s, 6 readers, 2 writers:
memory barriers in reader:
1701557485 reads,
2202847 writes
signal-based scheme:
9830061167 reads, 6700 writes
sys_membarrier:
9952759104 reads, 425 writes
sys_membarrier (dyn. check):
7970328887 reads, 425 writes
The dynamic sys_membarrier availability check adds some overhead to
the read-side compared to the signal-based scheme, but besides that,
sys_membarrier slightly outperforms the signal-based scheme. However,
this non-expedited sys_membarrier implementation has a much slower grace
period than signal and memory barrier schemes.
Besides diminishing the number of wake-ups, one major advantage of the
membarrier system call over the signal-based scheme is that it does not
need to reserve a signal. This plays much more nicely with libraries,
and with processes injected into for tracing purposes, for which we
cannot expect that signals will be unused by the application.
An expedited version of this system call can be added later on to speed
up the grace period. Its implementation will likely depend on reading
the cpu_curr()->mm without holding each CPU's rq lock.
This patch adds the system call to x86 and to asm-generic.
[1] http://urcu.so
membarrier(2) man page:
MEMBARRIER(2) Linux Programmer's Manual MEMBARRIER(2)
NAME
membarrier - issue memory barriers on a set of threads
SYNOPSIS
#include <linux/membarrier.h>
int membarrier(int cmd, int flags);
DESCRIPTION
The cmd argument is one of the following:
MEMBARRIER_CMD_QUERY
Query the set of supported commands. It returns a bitmask of
supported commands.
MEMBARRIER_CMD_SHARED
Execute a memory barrier on all threads running on the system.
Upon return from system call, the caller thread is ensured that
all running threads have passed through a state where all memory
accesses to user-space addresses match program order between
entry to and return from the system call (non-running threads
are de facto in such a state). This covers threads from all pro=E2=80=90
cesses running on the system. This command returns 0.
The flags argument needs to be 0. For future extensions.
All memory accesses performed in program order from each targeted
thread is guaranteed to be ordered with respect to sys_membarrier(). If
we use the semantic "barrier()" to represent a compiler barrier forcing
memory accesses to be performed in program order across the barrier,
and smp_mb() to represent explicit memory barriers forcing full memory
ordering across the barrier, we have the following ordering table for
each pair of barrier(), sys_membarrier() and smp_mb():
The pair ordering is detailed as (O: ordered, X: not ordered):
barrier() smp_mb() sys_membarrier()
barrier() X X O
smp_mb() X O O
sys_membarrier() O O O
RETURN VALUE
On success, these system calls return zero. On error, -1 is returned,
and errno is set appropriately. For a given command, with flags
argument set to 0, this system call is guaranteed to always return the
same value until reboot.
ERRORS
ENOSYS System call is not implemented.
EINVAL Invalid arguments.
Linux 2015-04-15 MEMBARRIER(2)
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Nicholas Miell <nmiell@comcast.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Pranith Kumar <bobby.prani@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Kirill A. Shutemov [Mon, 17 Aug 2015 23:54:22 +0000 (09:54 +1000)]
mm, madvise: use vma_is_anonymous() to check for anon VMA
!vma->vm_file is not reliable to detect anon VMA, because not all
drivers bother set it. Let's use vma_is_anonymous() instead.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: Minchan Kim <minchan@kernel.org>
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Kirill A. Shutemov [Mon, 17 Aug 2015 23:54:22 +0000 (09:54 +1000)]
mm: use vma_is_anonymous() in create_huge_pmd() and wp_huge_pmd()
Let's use helper rather than direct check of vma->vm_ops to distinguish
anonymous VMA.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Kirill A. Shutemov [Mon, 17 Aug 2015 23:54:22 +0000 (09:54 +1000)]
mm: make sure all file VMAs have ->vm_ops set
We rely on vma->vm_ops == NULL to detect anonymous VMA: see
vma_is_anonymous(), but some drivers doesn't set ->vm_ops.
As a result we can end up with anonymous page in private file mapping.
That should not lead to serious misbehaviour, but nevertheless is wrong.
Let's fix by setting up dummy ->vm_ops for file mmapping if f_op->mmap()
didn't set its own.
The patch also adds sanity check into __vma_link_rb(). It will help
catch broken VMAs which inserted directly into mm_struct via
insert_vm_struct().
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Andrew Morton [Mon, 17 Aug 2015 23:54:21 +0000 (09:54 +1000)]
mm-mpx-add-vm_flags_t-vm_flags-arg-to-do_mmap_pgoff-fix-checkpatch-fixes
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#5:
>> mm/nommu.c:1248:30: error: 'vm_flags' redeclared as different kind of symbol
WARNING: please, no spaces at the start of a line
#28: FILE: mm/nommu.c:1248:
+ unsigned long capabilities, result;$
WARNING: please, no spaces at the start of a line
#37: FILE: mm/nommu.c:1266:
+ vm_flags |= determine_vm_flags(file, prot, flags, capabilities);$
total: 0 errors, 3 warnings, 16 lines checked
./patches/mm-mpx-add-vm_flags_t-vm_flags-arg-to-do_mmap_pgoff-fix.patch has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
Please run checkpatch prior to sending patches
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Kirill A. Shutemov [Mon, 17 Aug 2015 23:54:21 +0000 (09:54 +1000)]
mm-mpx-add-vm_flags_t-vm_flags-arg-to-do_mmap_pgoff-fix
mm/nommu.c: In function 'do_mmap':
>> mm/nommu.c:1248:30: error: 'vm_flags' redeclared as different kind of symbol
unsigned long capabilities, vm_flags, result;
^
mm/nommu.c:1241:15: note: previous definition of 'vm_flags' was here
vm_flags_t vm_flags,
Reported-by: Wu Fengguang <fengguang.wu@intel.com>
Reported-by: Oleg Nesterov <oleg@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Tested-by: Mark Salter <msalter@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Oleg Nesterov [Mon, 17 Aug 2015 23:54:21 +0000 (09:54 +1000)]
mm, mpx: add "vm_flags_t vm_flags" arg to do_mmap_pgoff()
Add the additional "vm_flags_t vm_flags" argument to do_mmap_pgoff(),
rename it to do_mmap(), and re-introduce do_mmap_pgoff() as a simple
wrapper on top of do_mmap(). Perhaps we should update the callers of
do_mmap_pgoff() and kill it later.
This way mpx_mmap() can simply call do_mmap(vm_flags => VM_MPX) and do not
play with vm internals.
After this change mmap_region() has a single user outside of mmap.c,
arch/tile/mm/elf.c:arch_setup_additional_pages(). It would be nice to
change arch/tile/ and unexport mmap_region().
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Dave Hansen <dave.hansen@linux.intel.com>
Tested-by: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Kirill A. Shutemov [Mon, 17 Aug 2015 23:54:21 +0000 (09:54 +1000)]
mm: mark most vm_operations_struct const
With two exceptions (drm/qxl and drm/radeon) all vm_operations_struct
structs should be constant.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Andrew Morton [Mon, 17 Aug 2015 23:54:20 +0000 (09:54 +1000)]
fs-seq_file-convert-int-seq_vprint-seq_printf-etc-returns-to-void-fix-fix
fix drivers/iommu/omap-iommu-debug.c for fs-seq_file-convert-int-seq_vprint-seq_printf-etc-returns-to-void.patch
Cc: Mark Brown <broonie@kernel.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Joe Perches <joe@perches.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Joerg Roedel <jroedel@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Andrew Morton [Mon, 17 Aug 2015 23:54:20 +0000 (09:54 +1000)]
fs-seq_file-convert-int-seq_vprint-seq_printf-etc-returns-to-void-fix
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Joe Perches <joe@perches.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Joe Perches [Mon, 17 Aug 2015 23:54:20 +0000 (09:54 +1000)]
fs/seq_file: convert int seq_vprint/seq_printf/etc... returns to void
The seq_<foo> function return values were frequently misused.
See: commit
1f33c41c03da ("seq_file: Rename seq_overflow() to
seq_has_overflowed() and make public")
All uses of these return values have been removed, so convert the
return types to void.
Miscellanea:
o Move seq_put_decimal_<type> and seq_escape prototypes closer the
other seq_vprintf prototypes
o Reorder seq_putc and seq_puts to return early on overflow
o Add argument names to seq_vprintf and seq_printf
o Update the seq_escape kernel-doc
o Convert a couple of leading spaces to tabs in seq_escape
Signed-off-by: Joe Perches <joe@perches.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Masanari Iida [Mon, 17 Aug 2015 23:54:20 +0000 (09:54 +1000)]
namei: fix warning while make xmldocs caused by namei.c
Fix the following warnings:
Warning(.//fs/namei.c:2422): No description found for parameter 'nd'
Warning(.//fs/namei.c:2422): Excess function parameter 'nameidata'
description in 'path_mountpoint'
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Stephen Rothwell [Mon, 24 Aug 2015 10:51:53 +0000 (20:51 +1000)]
Merge branch 'akpm-current/current'
Stephen Rothwell [Mon, 24 Aug 2015 09:24:55 +0000 (19:24 +1000)]
Merge remote-tracking branch 'nvdimm/libnvdimm-for-next'
Stephen Rothwell [Mon, 24 Aug 2015 09:23:44 +0000 (19:23 +1000)]
Merge remote-tracking branch 'rtc/rtc-next'
Stephen Rothwell [Mon, 24 Aug 2015 09:23:41 +0000 (19:23 +1000)]
Merge remote-tracking branch 'coresight/next'
Stephen Rothwell [Mon, 24 Aug 2015 09:22:35 +0000 (19:22 +1000)]
Merge remote-tracking branch 'livepatching/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 09:22:33 +0000 (19:22 +1000)]
Merge remote-tracking branch 'access_once/linux-next'
Stephen Rothwell [Mon, 24 Aug 2015 09:21:23 +0000 (19:21 +1000)]
Merge remote-tracking branch 'y2038/y2038'
Stephen Rothwell [Mon, 24 Aug 2015 09:21:08 +0000 (19:21 +1000)]
Merge remote-tracking branch 'llvmlinux/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 09:19:50 +0000 (19:19 +1000)]
Merge remote-tracking branch 'clk/clk-next'
Stephen Rothwell [Mon, 24 Aug 2015 09:06:51 +0000 (19:06 +1000)]
Merge remote-tracking branch 'userns/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 09:05:45 +0000 (19:05 +1000)]
Merge remote-tracking branch 'pwm/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 09:04:01 +0000 (19:04 +1000)]
Merge remote-tracking branch 'gpio/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:59:02 +0000 (18:59 +1000)]
Merge remote-tracking branch 'vhost/linux-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:57:54 +0000 (18:57 +1000)]
Merge remote-tracking branch 'pinctrl/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:55:58 +0000 (18:55 +1000)]
Merge remote-tracking branch 'target-updates/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:54:59 +0000 (18:54 +1000)]
Merge remote-tracking branch 'scsi/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:39:00 +0000 (18:39 +1000)]
Merge remote-tracking branch 'cgroup/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:24:42 +0000 (18:24 +1000)]
Merge remote-tracking branch 'kdbus/kdbus'
Stephen Rothwell [Mon, 24 Aug 2015 08:21:23 +0000 (18:21 +1000)]
Merge remote-tracking branch 'char-misc/char-misc-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:14:36 +0000 (18:14 +1000)]
Merge remote-tracking branch 'staging/staging-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:12:09 +0000 (18:12 +1000)]
Merge remote-tracking branch 'usb/usb-next'
Stephen Rothwell [Mon, 24 Aug 2015 08:10:18 +0000 (18:10 +1000)]
Merge remote-tracking branch 'tty/tty-next'
Stephen Rothwell [Mon, 24 Aug 2015 07:56:50 +0000 (17:56 +1000)]
Merge remote-tracking branch 'driver-core/driver-core-next'
Stephen Rothwell [Mon, 24 Aug 2015 07:55:42 +0000 (17:55 +1000)]
Merge remote-tracking branch 'ipmi/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 07:54:55 +0000 (17:54 +1000)]
Merge remote-tracking branch 'leds/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 07:51:40 +0000 (17:51 +1000)]
Merge remote-tracking branch 'regmap/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 07:50:53 +0000 (17:50 +1000)]
Merge remote-tracking branch 'chrome-platform/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 07:50:05 +0000 (17:50 +1000)]
Merge remote-tracking branch 'drivers-x86/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 06:30:34 +0000 (16:30 +1000)]
Merge remote-tracking branch 'workqueues/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 06:14:19 +0000 (16:14 +1000)]
Merge remote-tracking branch 'percpu/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 06:01:17 +0000 (16:01 +1000)]
Merge remote-tracking branch 'xen-tip/linux-next'
Stephen Rothwell [Mon, 24 Aug 2015 05:59:01 +0000 (15:59 +1000)]
Merge remote-tracking branch 'kvm-ppc/kvm-ppc-next'
Stephen Rothwell [Mon, 24 Aug 2015 05:52:28 +0000 (15:52 +1000)]
Merge remote-tracking branch 'kvm-arm/next'
Stephen Rothwell [Mon, 24 Aug 2015 05:51:21 +0000 (15:51 +1000)]
Merge remote-tracking branch 'kvm/linux-next'
Stephen Rothwell [Mon, 24 Aug 2015 05:34:40 +0000 (15:34 +1000)]
Merge remote-tracking branch 'rcu/rcu/next'
Stephen Rothwell [Mon, 24 Aug 2015 05:34:36 +0000 (15:34 +1000)]
Merge remote-tracking branch 'irqchip/irqchip/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 05:33:49 +0000 (15:33 +1000)]
Merge remote-tracking branch 'edac-amd/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 05:17:15 +0000 (15:17 +1000)]
Merge remote-tracking branch 'tip/auto-latest'
Stephen Rothwell [Mon, 24 Aug 2015 05:15:18 +0000 (15:15 +1000)]
Merge remote-tracking branch 'spi/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 05:14:17 +0000 (15:14 +1000)]
Merge remote-tracking branch 'mailbox/mailbox-for-next'
Stephen Rothwell [Mon, 24 Aug 2015 05:13:32 +0000 (15:13 +1000)]
Merge remote-tracking branch 'dt-rh/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 05:12:01 +0000 (15:12 +1000)]
Merge remote-tracking branch 'audit/next'
Stephen Rothwell [Mon, 24 Aug 2015 04:57:49 +0000 (14:57 +1000)]
Merge remote-tracking branch 'trivial/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 04:57:03 +0000 (14:57 +1000)]
Merge remote-tracking branch 'jc_docs/docs-next'
Stephen Rothwell [Mon, 24 Aug 2015 04:55:53 +0000 (14:55 +1000)]
Merge remote-tracking branch 'dwmw2-iommu/master'
Stephen Rothwell [Mon, 24 Aug 2015 04:54:43 +0000 (14:54 +1000)]
Merge remote-tracking branch 'iommu/next'
Stephen Rothwell [Mon, 24 Aug 2015 04:40:44 +0000 (14:40 +1000)]
Merge remote-tracking branch 'security/next'
Stephen Rothwell [Mon, 24 Aug 2015 04:38:48 +0000 (14:38 +1000)]
Merge remote-tracking branch 'regulator/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 04:36:57 +0000 (14:36 +1000)]
Merge remote-tracking branch 'omap_dss2/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 04:36:11 +0000 (14:36 +1000)]
Merge remote-tracking branch 'battery/master'
Stephen Rothwell [Mon, 24 Aug 2015 04:35:05 +0000 (14:35 +1000)]
Merge remote-tracking branch 'mfd/for-mfd-next'
Stephen Rothwell [Mon, 24 Aug 2015 04:34:18 +0000 (14:34 +1000)]
Merge remote-tracking branch 'md/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 04:33:13 +0000 (14:33 +1000)]
Merge remote-tracking branch 'kgdb/kgdb-next'
Stephen Rothwell [Mon, 24 Aug 2015 04:32:04 +0000 (14:32 +1000)]
Merge remote-tracking branch 'mmc-uh/next'
Stephen Rothwell [Mon, 24 Aug 2015 04:31:11 +0000 (14:31 +1000)]
Merge remote-tracking branch 'device-mapper/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 04:15:02 +0000 (14:15 +1000)]
Merge remote-tracking branch 'block/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 03:45:49 +0000 (13:45 +1000)]
Merge remote-tracking branch 'input/next'
Stephen Rothwell [Mon, 24 Aug 2015 03:45:06 +0000 (13:45 +1000)]
Merge remote-tracking branch 'modules/modules-next'
Stephen Rothwell [Mon, 24 Aug 2015 03:43:23 +0000 (13:43 +1000)]
Merge remote-tracking branch 'sound-asoc/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 03:42:33 +0000 (13:42 +1000)]
Merge remote-tracking branch 'sound/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 03:41:47 +0000 (13:41 +1000)]
Merge remote-tracking branch 'drm-misc/topic/drm-misc'
Stephen Rothwell [Mon, 24 Aug 2015 03:41:02 +0000 (13:41 +1000)]
Merge remote-tracking branch 'drm-intel/for-linux-next'
Stephen Rothwell [Mon, 24 Aug 2015 03:39:26 +0000 (13:39 +1000)]
Merge remote-tracking branch 'drm/drm-next'
Stephen Rothwell [Mon, 24 Aug 2015 03:37:14 +0000 (13:37 +1000)]
Merge remote-tracking branch 'crypto/master'
Stephen Rothwell [Mon, 24 Aug 2015 03:36:29 +0000 (13:36 +1000)]
Merge remote-tracking branch 'l2-mtd/master'
Stephen Rothwell [Mon, 24 Aug 2015 03:30:56 +0000 (13:30 +1000)]
Merge remote-tracking branch 'rdma/for-next'
Initial roundup of 4.3 merge window candidates
# gpg: Signature made Sun 02 Aug 2015 07:21:56 AEST using RSA key ID
0E572FDD
# gpg: Oops: keyid_from_fingerprint: no pubkey
# gpg: Good signature from "Doug Ledford <dledford@redhat.com>"
# gpg: aka "Doug Ledford (Personal email) <dledford@xsintricity.com>"
# gpg: aka "[jpeg image of size 3057]"
# gpg: WARNING: This key is not certified with a trusted signature!
# gpg: There is no indication that the signature belongs to the owner.
# Primary key fingerprint: AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Stephen Rothwell [Mon, 24 Aug 2015 03:30:12 +0000 (13:30 +1000)]
Merge remote-tracking branch 'bluetooth/master'
Stephen Rothwell [Mon, 24 Aug 2015 03:20:19 +0000 (13:20 +1000)]
Stephen Rothwell [Mon, 24 Aug 2015 02:51:44 +0000 (12:51 +1000)]
Merge remote-tracking branch 'slave-dma/next'
Stephen Rothwell [Mon, 24 Aug 2015 02:50:59 +0000 (12:50 +1000)]
Merge remote-tracking branch 'dlm/next'
Stephen Rothwell [Mon, 24 Aug 2015 02:49:54 +0000 (12:49 +1000)]
Merge remote-tracking branch 'thermal/next'
Stephen Rothwell [Mon, 24 Aug 2015 02:38:00 +0000 (12:38 +1000)]
Merge remote-tracking branch 'idle/next'
Stephen Rothwell [Mon, 24 Aug 2015 02:25:25 +0000 (12:25 +1000)]
Merge remote-tracking branch 'pm/linux-next'
Stephen Rothwell [Mon, 24 Aug 2015 02:24:40 +0000 (12:24 +1000)]
Merge remote-tracking branch 'libata/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 02:23:35 +0000 (12:23 +1000)]
Merge remote-tracking branch 'kbuild/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 02:11:52 +0000 (12:11 +1000)]
Merge remote-tracking branch 'v4l-dvb/master'
Stephen Rothwell [Mon, 24 Aug 2015 02:11:10 +0000 (12:11 +1000)]
Merge remote-tracking branch 'hwmon-staging/hwmon-next'
Stephen Rothwell [Mon, 24 Aug 2015 02:10:26 +0000 (12:10 +1000)]
Merge branch 'jdelvare-hwmon/master'
Stephen Rothwell [Mon, 24 Aug 2015 02:07:21 +0000 (12:07 +1000)]
Merge remote-tracking branch 'i2c/i2c/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 02:06:32 +0000 (12:06 +1000)]
Merge remote-tracking branch 'hid/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 02:01:43 +0000 (12:01 +1000)]
Merge remote-tracking branch 'pci/next'
Stephen Rothwell [Mon, 24 Aug 2015 01:44:35 +0000 (11:44 +1000)]
Merge remote-tracking branch 'vfs/for-next'
Stephen Rothwell [Mon, 24 Aug 2015 01:43:44 +0000 (11:43 +1000)]
Merge remote-tracking branch 'xfs/for-next'