Linux Next

• Thread Index

• linux-next: manual merge of the nfsd tree with the nfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: randconfig build error with next-20150209, in arch/x86/kvm/vmx.c
  • From: Radim Krčmář <rkrcmar@xxxxxxxxxx>
• randconfig build error with next-20150209, in arch/x86/kvm/vmx.c
  • From: Jim Davis <jim.epost@xxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: Pat Erley <pat-lkml@xxxxxxxxx>
• Re: linux-next: Tree for Feb 9 (build failures)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: Jiang Liu <jiang.liu@xxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• linux-next: Tree for Feb 9
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the target-updates tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx>
• linux-next: manual merge of the kvm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: Jiang Liu <jiang.liu@xxxxxxxxxxxxxxx>
• Re: [next-20141231] sched: WARNING: CPU: 1 PID: 2539 at kernel/sched/core.c:7303 __might_sleep+0xbd/0xd0()
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• linux-next: build failure after merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree with the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx>
• linux-next: build failure after merge of the sound-asoc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the wireless-drivers-next tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: Jiang Liu <jiang.liu@xxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: Pat Erley <pat-lkml@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Dave Hansen <dave@xxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: Pat Erley <pat-lkml@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: Pat Erley <pat-lkml@xxxxxxxxx>
• Re: BUG: non-zero nr_pmds on freeing mm: 1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• BUG: non-zero nr_pmds on freeing mm: 1
  • From: Pat Erley <pat-lkml@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 1/2 v2] tracing: Add condition check to RCU lockdep checks
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 1/2] tracing: Add condition check to RCU lockdep checks
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 1/2] tracing: Add condition check to RCU lockdep checks
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH v2] drm/nouveau/clk: Change rate from u32 to u64 in gk20a_pllg_calc_rate()
  • From: Alexandre Courbot <acourbot@xxxxxxxxxx>
• [PATCH v2] drm/nouveau/clk: Change rate from u32 to u64 in gk20a_pllg_calc_rate()
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH -next] drm/nouveau/clk: Use plain "/" for 32-bit division
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: Update for drm-intel.git branches
  • From: Daniel Vetter <daniel.vetter@xxxxxxxx>
• Re: [PATCH -next] drm/nouveau/clk: Use plain "/" for 32-bit division
  • From: Alexandre Courbot <acourbot@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Dave Hansen <dave@xxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Dave Hansen <dave@xxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Dave Hansen <dave@xxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• [PATCH -next] drm/nouveau/clk: Use plain "/" for 32-bit division
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: linux-next: build failure after merge of the scsi tree
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] kasan: fix build warnings
  • From: Michal Marek <mmarek@xxxxxxx>
• Re: Update for drm-intel.git branches
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] kasan: fix build warnings
  • From: Andrey Ryabinin <a.ryabinin@xxxxxxxxxxx>
• [PATCH] kasan: fix build warnings
  • From: Andrey Ryabinin <a.ryabinin@xxxxxxxxxxx>
• linux-next: Tree for Feb 4
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] exynos/drm: fix no hdmi output
  • From: Inki Dae <inki.dae@xxxxxxxxxxx>
• Re: linux-next: build warning after merge of the akpm-current tree
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] scsi_logging: return void for dev_printk() functions
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: linux-next: build failure after merge of the scsi tree
  • From: Joe Perches <joe@xxxxxxxxxxx>
• linux-next: build failure after merge of the scsi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH -next] ARC: Fix earlycon build breakage
  • From: Vineet Gupta <Vineet.Gupta1@xxxxxxxxxxxx>
• linux-next: manual merge of the sound-asoc tree with the sound tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH -next] ARC: Fix earlycon build breakage
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH -next] ARC: Fix earlycon build breakage
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH -next] ARC: Fix earlycon build breakage
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH -next] ARC: Fix earlycon build breakage
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• mmotm 2015-02-03-16-38 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: Tree for Feb 3 (arc:defconfig build failure)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] staging: ft1000: fix braces warning
  • From: Bilel DRIRA <bilel.dr@xxxxxxxxx>
• Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH] staging: ft1000: fix braces warning
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH] staging: ft1000: fix braces warning
  • From: bill <bilel.dr@xxxxxxxxx>
• Re: [PATCH] staging: ft1000: fix braces warning
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: linux-next: Tree for Feb 3 (arc:defconfig build failure)
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• [PATCH] staging: ft1000: fix braces warning
  • From: Bilel DRIRA <bilel.dr@xxxxxxxxx>
• Re: linux-next: Tree for Feb 3 (arc:defconfig build failure)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the clk tree with the arm-soc tree
  • From: Mike Turquette <mturquette@xxxxxxxxxx>
• Update for drm-intel.git branches
  • From: Daniel Vetter <daniel.vetter@xxxxxxxx>
• linux-next: Tree for Feb 3
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the clk tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the clk tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the target-updates tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 27 (build failures due to 'don't offset memmap for flatmem')
  • From: Laura Abbott <lauraa@xxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: Nicolas Dichtel <nicolas.dichtel@xxxxxxxxx>
• linux-next: Tree for Feb 2
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree with the vfs tree
  • From: Christoph Hellwig <hch@xxxxxx>
• linux-next: manual merge of the akpm-current tree with the fsl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the target-updates tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Linux 3.19-rc7
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 30 (clk related WARNING on arm)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 30 (clk related WARNING on arm)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree with the vfs tree
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: libahci_platform has undefined symbol on sparc
  • From: Gregory CLEMENT <gregory.clement@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: libahci_platform has undefined symbol on sparc
  • From: Hans de Goede <hdegoede@xxxxxxxxxx>
• linux-next: libahci_platform has undefined symbol on sparc
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• Re: [PATCH] mm: remove remaining references to NUMA hinting bits and helpers -fix
  • From: Steve Capper <steve.capper@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 30 (clk related WARNING on arm)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 30 (build failures)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 30 (build failures)
  • From: Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 30 (build failures)
  • From: Oleksij Rempel <linux@xxxxxxxxxxxxxxxx>
• Re: [PATCH] exynos/drm: fix no hdmi output
  • From: Gustavo Padovan <gustavo@xxxxxxxxxxx>
• Re: linux-next: Tree for Jan 30 (build failures)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• [PATCH] mm: remove remaining references to NUMA hinting bits and helpers -fix
  • From: Mel Gorman <mgorman@xxxxxxx>
• Re: [PATCH] exynos/drm: fix no hdmi output
  • From: Joonyoung Shim <jy0922.shim@xxxxxxxxxxx>
• linux-next: Tree for Jan 30
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the spi tree
  • From: Ricardo Ribalda Delgado <ricardo.ribalda@xxxxxxxxx>
• Re: [PATCH] arm: reduce conflicts in Kcinfig.debug
  • From: Baruch Siach <baruch@xxxxxxxxxx>
• linux-next: build failure after merge of the spi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] arm: reduce conflicts in Kcinfig.debug
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2015-01-29-16-39 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: [PATCH] exynos/drm: fix no hdmi output
  • From: Joonyoung Shim <jy0922.shim@xxxxxxxxxxx>
• Re: linux-next: manual merge of the arm-soc tree with the arm tree
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the arm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the arm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] exynos/drm: fix no hdmi output
  • From: Alban Browaeys <alban.browaeys@xxxxxxxxx>
• Re: Hangs in libhugetlbfs tests in -next
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: Hangs in libhugetlbfs tests in -next
  • From: Steve Capper <steve.capper@xxxxxxxxxx>
• Re: [PATCH v5 6/8] arm64/efi: move SetVirtualAddressMap() to UEFI stub
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH v5 6/8] arm64/efi: move SetVirtualAddressMap() to UEFI stub
  • From: Steve Capper <steve.capper@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] drm/bridge: sti_dvo: adapt to updated bridge API
  • From: Ajay Kumar <ajaykumar.rs@xxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Oded Gabbay <oded.gabbay@xxxxxxx>
• Re: linux-next: manual merge of the drm tree with Linus' tree
  • From: Oded Gabbay <oded.gabbay@xxxxxxx>
• linux-next: Tree for Jan 29
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the xen-tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: randconfig build error with next-20150127, in drivers/i2c/busses/i2c-designware-baytrail.c
  • From: Wolfram Sang <wsa@xxxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: linux-next: manual merge of the block tree with the vfs tree
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• build fails: drm/bridge: make bridge registration independent of drm flow
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the sound-asoc tree
  • From: Mark Brown <broonie@xxxxxxxxxx>
• linux-next: manual merge of the block tree with the l2-mtd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2015-01-27-16-19 uploaded (smack)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the sound-asoc tree
  • From: Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree with the vfs tree
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: Daniel Borkmann <dborkman@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the sound-asoc tree
  • From: Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• randconfig build error with next-20150128, in drivers/gpu/drm/panel
  • From: Jim Davis <jim.epost@xxxxxxxxx>
• linux-next: Tree for Jan 28
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• linux-next: build failure after merge of the sound-asoc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2015-01-27-16-19 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• linux-next: manual merge of the pci tree with the mips tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Fwd: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• randconfig build error with next-20150127, in drivers/iio/magnetometer/ak8975.c
  • From: Jim Davis <jim.epost@xxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 27 (build failures due to 'don't offset memmap for flatmem')
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Michal Hocko <mhocko@xxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: make allyesconfig i386 build failure with next-20150122 (caused by fb_agm1264k-fl driver)
  • From: Tilman Schmidt <tilman@xxxxxxx>
• linux-next: Tree for Jan 27
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the akpm-current tree
  • From: Vladimir Davydov <vdavydov@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the wireless-drivers-next tree
  • From: Kalle Valo <kvalo@xxxxxxxxxxxxxx>
• linux-next: build warnings after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the wireless-drivers-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the clockevents tree with the arm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree with the vfs tree
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree with the vfs tree
  • From: Jens Axboe <axboe@xxxxxxxxx>
• linux-next: manual merge of the block tree with the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: make allyesconfig i386 build failure with next-20150122 (caused by fb_agm1264k-fl driver)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• linux-next: manual merge of the drm-panel tree with the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm64 tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: make allyesconfig i386 build failure with next-20150122 (caused by fb_agm1264k-fl driver)
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Tyler Baker <tyler.baker@xxxxxxxxxx>
• Re: make allyesconfig i386 build failure with next-20150122 (caused by fb_agm1264k-fl driver)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: contact change for the integrity tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: contact change for the integrity tree
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• linux-next: contact change for the integrity tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Valdis.Kletnieks@xxxxxx
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• mmotm 2015-01-23-16-19: build failures due to 'mm/page_alloc.c: don't offset memmap for flatmem'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Nishanth Menon <nm@xxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• mmotm 2015-01-23-16-19 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: [next-20150119]regression (mm)?
  • From: Tyler Baker <tyler.baker@xxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Nishanth Menon <nm@xxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Nishanth Menon <nm@xxxxxx>
• Re: linux-next: Tree for Jan 23
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Tyler Baker <tyler.baker@xxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Nishanth Menon <nm@xxxxxx>
• Re: randconfig build error with next-20150123, in security/smack/smack_netfilter.c
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Johannes Weiner <hannes@xxxxxxxxxxx>
• Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Christoffer Dall <cdall@xxxxxxxxxxxxxxx>
• Re: mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• linux-next: Tree for Jan 23
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2015-01-22-15-04: qemu failure due to 'mm: memcontrol: remove unnecessary soft limit tree node test'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• mmotm 2015-01-22-15-04: qemu failures due to 'mm: account pmd page tables to the process'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Wei Huang <wei@xxxxxxxxxx>
• linux-next: manual merge of the vfs tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2015-01-22-15-04 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: kvms390 tree for Linux next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: kvms390 tree for Linux next
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: kvms390 tree for Linux next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: remove obsolete documentation tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: remove obsolete documentation tree
  • From: Jiri Kosina <jkosina@xxxxxxx>
• Re: linux-next: Tree for Jan 20 -- sparc32: fix broken set_pte()
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• make allyesconfig i386 build failure with next-20150122
  • From: Jim Davis <jim.epost@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- sparc32: fix broken set_pte()
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- sparc32: fix broken set_pte()
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• kvms390 tree for Linux next
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Marc Zyngier <marc.zyngier@xxxxxxx>
• linux-next: Tree for Jan 22
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: strange commit in the mfd tree
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm-arm tree with the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm-arm tree with the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the drm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the drm tree with Linus' tree
  • From: Dave Airlie <airlied@xxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• linux-next: manual merge of the drm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] tpm/tpm_tis: Add missing ifdef CONFIG_ACPI for pnp_acpi_device
  • From: James Morris <jmorris@xxxxxxxxx>
• linux-next: manual merge of the drm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] tpm/tpm_tis: Add missing ifdef CONFIG_ACPI for pnp_acpi_device
  • From: Peter Huewe <peterhuewe@xxxxxx>
• Re: linux-next: Tree for Jan 20
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [PATCH] tpm/tpm_tis: Add missing ifdef CONFIG_ACPI for pnp_acpi_device
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: strange commit in the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] tpm/tpm_tis: Add missing ifdef CONFIG_ACPI for pnp_acpi_device
  • From: Peter Hüwe <PeterHuewe@xxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Walmsley <paul@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [PATCH] tpm/tpm_tis: Add missing ifdef CONFIG_ACPI for pnp_acpi_device
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] tpm/tpm_tis: Add missing ifdef CONFIG_ACPI for pnp_acpi_device
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: tidy up of trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• [PATCH] tpm/tpm_tis: Add missing ifdef CONFIG_ACPI for pnp_acpi_device
  • From: Peter Huewe <peterhuewe@xxxxxx>
• Re: [PATCH] staging/lustre/llite: get rid of backing_dev_info
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [PATCH] staging/lustre/llite: get rid of backing_dev_info
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Aw: randconfig build error with next-20150121, in drivers/char/tpm/tpm_tis.c
  • From: "Peter Huewe" <PeterHuewe@xxxxxx>
• Re: next-20150120 broken on Tegra by "ata: libahci: Allow using multiple regulators"
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: next-20150120 broken on Tegra by "ata: libahci: Allow using multiple regulators"
  • From: Thierry Reding <treding@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: linux-next: manual merge of the mmc-uh tree with the sunxi tree
  • From: Ulf Hansson <ulf.hansson@xxxxxxxxxx>
• Re: linux-next: tidy up of trees
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: next-20150120 broken on Tegra by "ata: libahci: Allow using multiple regulators"
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: linux-next: manual merge of the mmc-uh tree with the sunxi tree
  • From: Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the mmc-uh tree with the sunxi tree
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 21
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the mmc-uh tree with the sunxi tree
  • From: Ulf Hansson <ulf.hansson@xxxxxxxxxx>
• Re: next-20150120 broken on Tegra by "ata: libahci: Allow using multiple regulators"
  • From: Gregory CLEMENT <gregory.clement@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 21
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: next-20150120 broken on Tegra by "ata: libahci: Allow using multiple regulators"
  • From: Thierry Reding <treding@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Peter Ujfalusi <peter.ujfalusi@xxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Konstantin Khlebnikov <koct9i@xxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Konstantin Khlebnikov <koct9i@xxxxxxxxx>
• [PATCH] staging/lustre/llite: get rid of backing_dev_info
  • From: green@xxxxxxxxxxxxxx
• linux-next: Tree for Jan 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Fwd: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: Fwd: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: Fwd: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: Fwd: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: Fwd: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Fwd: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• linux-next: tidy up of trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• linux-next: build failure after merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree with the l2-mtd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Fwd: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• next-20150120 broken on Tegra by "ata: libahci: Allow using multiple regulators"
  • From: Paul Walmsley <paul@xxxxxxxxx>
• next-20150120 broken on Tegra by "ata: libahci: Allow using multiple regulators"
  • From: Paul Walmsley <paul@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Nishanth Menon <nm@xxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: linux-next: manual merge of the omap tree with the arm-soc tree
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the omap tree with the arm-soc tree
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the omap tree with the arm-soc tree
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Paul Moore <pmoore@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs
  • From: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the audit tree with Linus' tree
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Felipe Balbi <balbi@xxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Fabio Estevam <festevam@xxxxxxxxx>
• Re: linux-next: Tree for Jan 20
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Jan 20
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the audit tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the audit tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the audit tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the mmc-uh tree with the sunxi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• linux-next: manual merge of the omap tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Felipe Balbi <balbi@xxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Tyler Baker <tyler.baker@xxxxxxxxxx>
• Re: [next-20150119]regression (mm)?
  • From: Nishanth Menon <nm@xxxxxx>
• [next-20150119]regression (mm)?
  • From: Nishanth Menon <nm@xxxxxx>
• Re: linux-next: build warning after merge of the akpm-current tree
  • From: Chris Mason <clm@xxxxxx>
• Re: compaction tracepoint broken with CONFIG_COMPACTION enabled
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• compaction tracepoint broken with CONFIG_COMPACTION enabled (was: mmotm 2015-01-16-15-50 uploaded)
  • From: Michal Hocko <mhocko@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Borislav Petkov <bp@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• linux-next: Tree for Jan 19
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2015-01-16-15-50 uploaded
  • From: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx>
• linux-next: manual merge of the luto-misc tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2 ] staging: ft1000: fix else style error
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: mmotm 2015-01-16-15-50 uploaded
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: mmotm 2015-01-16-15-50 uploaded (netfilter xt_TPROXY.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• mmotm 2015-01-16-15-50 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: [PATCH 1/2 v3] ftrace: don't allow IPMODIFY without proper compiler support
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2 v3] ftrace: don't allow IPMODIFY without proper compiler support
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2 v3] ftrace: don't allow IPMODIFY without proper compiler support
  • From: Jiri Kosina <jkosina@xxxxxxx>
• RE: linux-next: manual merge of the usb-gadget tree with the usb.current tree
  • From: "Kaukab, Yousaf" <yousaf.kaukab@xxxxxxxxx>
• linux-next: Tree for Jan 16
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the i2c tree
  • From: Pantelis Antoniou <pantelis.antoniou@xxxxxxxxxxxx>
• linux-next: manual merge of the usb-gadget tree with the usb.current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the wireless-drivers-next tree with the wireless-drivers tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the i2c tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 12 (build failures: m68k, ppc)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 12 (build failures: m68k, ppc)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• [PATCH 2/2 v3] kprobes: compile out IPMODIFY support if ftrace doesn't support it
  • From: Jiri Kosina <jkosina@xxxxxxx>
• [PATCH 1/2 v3] ftrace: don't allow IPMODIFY without proper compiler support
  • From: Jiri Kosina <jkosina@xxxxxxx>
• Re: [PATCH 1/2 v2] ftrace: don't allow IPMODIFY without proper compiler support
  • From: Jiri Kosina <jkosina@xxxxxxx>
• Re: linux-next: manual merge of the renesas tree with the arm-soc tree
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• linux-next: Tree for Jan 15
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 1/2 v2] ftrace: don't allow IPMODIFY without proper compiler support
  • From: Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx>
• Re: [PATCH 2/2] kprobes: compile out IPMODIFY support if ftrace doesn't support it
  • From: Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the renesas tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] next: drm/atomic: Use copy_from_user to copy 64 bit data from user space
  • From: Daniel Vetter <daniel@xxxxxxxx>
• [PATCH 2/2] kprobes: compile out IPMODIFY support if ftrace doesn't support it
  • From: Jiri Kosina <jkosina@xxxxxxx>
• [PATCH 1/2 v2] ftrace: don't allow IPMODIFY without proper compiler support
  • From: Jiri Kosina <jkosina@xxxxxxx>
• Re: [PATCH] ftrace: don't allow IPMODIFY without proper compiler support (was Re: Re: livepatching tree for linux-next)
  • From: Jiri Kosina <jkosina@xxxxxxx>
• linux-next: Tree for Jan 14
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] ftrace: don't allow IPMODIFY without proper compiler support (was Re: Re: livepatching tree for linux-next)
  • From: Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx>
• Re: [PATCH] ftrace: don't allow IPMODIFY without proper compiler support (was Re: Re: livepatching tree for linux-next)
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH] ftrace: don't allow IPMODIFY without proper compiler support (was Re: Re: livepatching tree for linux-next)
  • From: Jiri Kosina <jkosina@xxxxxxx>
• [PATCH v2 ] staging: ft1000: fix else style error
  • From: Bilel DRIRA <bilel.dr@xxxxxxxxx>
• Re: linux-next: Tree for Jan 13 (arm build failure)
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: linux-next: Tree for Jan 13 (arm build failure)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the imx-mxs tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: randconfig build error with next-20150113, in sound/pci/hda/patch_realtek.c
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: randconfig build error with next-20150113, in drivers/pcmcia/rsrc_pci.c
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the imx-mxs tree with the arm-soc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• linux-next: Tree for Jan 13
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the char-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] next: drm/atomic: Use copy_from_user to copy 64 bit data from user space
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• linux-next: manual merge of the usb-gadget tree with the usb.current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the usb-gadget tree with the usb.current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the mvebu tree with the arm-soc tree
  • From: Andrew Lunn <andrew@xxxxxxx>
• linux-next: manual merge of the mvebu tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the imx-mxs tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 12 (build failures: m68k, ppc)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: randconfig build error with next-20150112, in drivers/hwmon/gpio-fan.c
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 12 (build failures: m68k, ppc)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 12 (build failures: m68k, ppc)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the usb-gadget-fixes tree with the usb.current tree
  • From: Thierry Reding <treding@xxxxxxxxxx>
• [PATCH] drm/i915: fix build for CONFIG_BUG=n
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: Re: livepatching tree for linux-next
  • From: Masami Hiramatsu <masami.hiramatsu.pt@xxxxxxxxxxx>
• Re: bf609: CONFIG_SND_BF6XX_PCM?
  • From: Paul Bolle <pebolle@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the pinctrl tree
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• linux-next: Tree for Jan 12
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the pinctrl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the usb-gadget-fixes tree with the usb.current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: livepatching tree for linux-next
  • From: Jiri Kosina <jkosina@xxxxxxx>
• linux-next: Tree for Jan 9
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 8 (media, v4l2, vb2)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7 (microblaze qemu problems)
  • From: Michal Simek <monstr@xxxxxxxxx>
• Re: linux-next: Tree for Jan 7 (microblaze qemu problems)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• linux-next: Tree for Jan 8
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: livepatching tree for linux-next
  • From: Jingoo Han <jg1.han@xxxxxxxxxxx>
• mmotm 2015-01-07-17-07 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: livepatching tree for linux-next
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: livepatching tree for linux-next
  • From: Jiri Kosina <jkosina@xxxxxxx>
• Re: livepatching tree for linux-next
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: livepatching tree for linux-next
  • From: Jiri Kosina <jkosina@xxxxxxx>
• Re: livepatching tree for linux-next
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: livepatching tree for linux-next
  • From: Jiri Kosina <jkosina@xxxxxxx>
• Re: livepatching tree for linux-next
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7 (microblaze qemu problems)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 7
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH next v2] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
  • From: Kalle Valo <kvalo@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 7
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• linux-next: Tree for Jan 7
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: error fetching the microblaze tree
  • From: Michal Simek <monstr@xxxxxxxxx>
• Re: linux-next: error fetching the microblaze tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: error fetching the microblaze tree
  • From: Michal Simek <monstr@xxxxxxxxx>
• linux-next: Tree for Jan 6
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: error fetching the microblaze tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 5
  • From: Ralf Baechle <ralf@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 5
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• linux-next: Tree for Jan 5
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: bad commit in the luto-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: bad commit in the luto-misc tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• linux-next: bad commit in the luto-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [next-20141231] sched: WARNING: CPU: 1 PID: 2539 at kernel/sched/core.c:7303 __might_sleep+0xbd/0xd0()
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [next-20141231] sched: WARNING: CPU: 1 PID: 2539 at kernel/sched/core.c:7303 __might_sleep+0xbd/0xd0()
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [next-20141231] sched: WARNING: CPU: 1 PID: 2539 at kernel/sched/core.c:7303 __might_sleep+0xbd/0xd0()
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH] scsi: bfa: bfad_bsg: Avoid memory overflow in bfad_iocmd_ioc_get_info()
  • From: Chen Gang <gang.chen@xxxxxxxxxxxxx>
• linux-next: Tree for Jan 3
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Dec 31 (usb/dwc2)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: question about the luto-misc tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• linux-next: Tree for Dec 31
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH v6] Thermal: introduce INT3406 thermal driver
  • From: Aaron Lu <aaron.lu@xxxxxxxxx>
• Re: linux-next: Tree for Dec 26 (f2fs)
  • From: Changman Lee <cm224.lee@xxxxxxxxxxx>
• Re: linux-next: question about the luto-misc tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: linux-next: error while fetching the watchdog tree
  • From: Wim Van Sebroeck <wim@xxxxxxxxx>
• Re: linux-next: missing merge fix for the access_once tree
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Pranith Kumar <bobby.prani@xxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Pranith Kumar <bobby.prani@xxxxxxxxx>
• Re: linux-next: question about the luto-misc tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] fix handling of wait_for_completion_timeout result
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Dec 26 (f2fs)
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• Re: linux-next: Tree for Dec 26 (f2fs)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Dec 26 (sst-haswell-pcm)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: Tree for Dec 26
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: livepatching tree for linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: error while fetching the watchdog tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: question about the luto-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH next] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• Re: [PATCH next] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
  • From: Kalle Valo <kvalo@xxxxxxxxxxxxxx>
• Re: [PATCH next] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• Re: [PATCH next] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
  • From: Kalle Valo <kvalo@xxxxxxxxxxxxxx>
• [PATCH next v2] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• Re: [PATCH next] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• [PATCH next] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
  • From: Nishanth Menon <nm@xxxxxx>
• Re: livepatching tree for linux-next
  • From: Josh Poimboeuf <jpoimboe@xxxxxxxxxx>
• Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
  • From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
• Re: livepatching tree for linux-next
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: missing merge fix for the access_once tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: missing merge fix patch for the merge of the xen-tip tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: missing merge fix for the access_once tree
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: missing merge fix patch for the merge of the xen-tip tree with the arm-soc tree
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• linux-next: missing merge fix patch for the merge of the xen-tip tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: missing merge fix for the access_once tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH v6] Thermal: introduce INT3406 thermal driver
  • From: Aaron Lu <aaron.lu@xxxxxxxxx>
• livepatching tree for linux-next
  • From: Jiri Kosina <jkosina@xxxxxxx>
• Re: linux-next: question about the luto-misc tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
  • From: Nishanth Menon <nm@xxxxxx>
• Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: regression: OMAP4 (next-20141204) (bisect to: ARM: 8208/1: l2c: Refactor the driver to use commit-like)
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: [PATCH v6] Thermal: introduce INT3406 thermal driver
  • From: Lee Jones <lee.jones@xxxxxxxxxx>
• Re: [PATCH v6] Thermal: introduce INT3406 thermal driver
  • From: Zhang Rui <rui.zhang@xxxxxxxxx>
• Re: randconfig build error with next-20141219, in drivers/input/misc/regulator-haptic.c
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• linux-next: Tree for Dec 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the idle tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• randconfig build error with next-20141219, in drivers/input/misc/regulator-haptic.c
  • From: Jim Davis <jim.epost@xxxxxxxxx>
• Re: [PATCH] pwm: atmel-hlcdc: Prevent div by zero
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: randconfig build error with next-20141204, in drivers/pwm
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• linux-next: Tree for Dec 19
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] pwm: atmel-hlcdc: Prevent div by zero
  • From: Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx>
• Re: randconfig build error with next-20141204, in drivers/pwm
  • From: Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx>
• Re: randconfig build error with next-20141204, in drivers/pwm
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: randconfig build error with next-20141204, in drivers/pwm
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: [PATCH] arm/rpc: avoid static keyword removal via define
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• linux-next: Tree for Dec 18
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the modules tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: status of the logfs tree?
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] arm/rpc: avoid static keyword removal via define
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [PATCH] arm/rpc: avoid static keyword removal via define
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [PATCH] arm/rpc: avoid static keyword removal via define
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: [PATCH] arm/rpc: avoid static keyword removal via define
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [BUG, linux-next] spawn PID 1 without CLONE_FS, wireless inop
  • From: Jeremiah Mahler <jmmahler@xxxxxxxxx>