Linux Next

• Thread Index

• Re: linux-next: build failure after merge of the tip tree
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: manual merge of the clk tree with the arm-soc tree
  • From: Nicolas Ferre <nicolas.ferre@xxxxxxxxx>
• Re: [PATCH] [v3] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH] [v3] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• next-20160301 build: 4 failures 11 warnings (next-20160301)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: linux-next: manual merge of the target-merge tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Mar 1
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the target-merge tree with the net-next tree
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• linux-next: manual merge of the clk tree with the sunxi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: 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>
• Re: linux-next: build failure after merge of the mfd tree
  • From: Kuninori Morimoto <kuninori.morimoto.gx@xxxxxxxxxxx>
• linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the mfd tree
  • From: Kuninori Morimoto <kuninori.morimoto.gx@xxxxxxxxxxx>
• Re: [PATCH] rapidio/rio_mport_cdev: fix conflicting DMA configuration options
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Unable to write into a vma if it has been mapped without PROT_READ
  • From: Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] rapidio/rio_mport_cdev: fix conflicting DMA configuration options
  • From: Alexandre Bounine <alexandre.bounine@xxxxxxx>
• Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] [v3] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] [v3] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Dave Hansen <dave@xxxxxxxx>
• Re: [PATCH] [v2] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] rapidio/rio_mport_cdev: fix build failure if CONFIG_DMA_ENGINE is not enabled
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 29 (media: em28xx)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Unable to write into a vma if it has been mapped without PROT_READ
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• [PATCH] [v2] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Dave Hansen <dave@xxxxxxxx>
• linux-next: Unable to write into a vma if it has been mapped without PROT_READ
  • From: Andrey Wagin <avagin@xxxxxxxxx>
• [PATCH] rapidio/rio_mport_cdev: fix build failure if CONFIG_DMA_ENGINE is not enabled
  • From: Alexandre Bounine <alexandre.bounine@xxxxxxx>
• Re: next-20160229 build: 1 failures 40 warnings (next-20160229)
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• next-20160229 build: 1 failures 40 warnings (next-20160229)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 29
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH v2] signals, pkeys: make si_pkey 32 bits
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: linux-next: manual merge of the iommu tree with the samsung-krzk tree
  • From: Joerg Roedel <joro@xxxxxxxxxx>
• linux-next: manual merge of the target-merge tree with the net-next 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 tip tree with the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the iommu tree with the samsung-krzk tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the iommu tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the wireless-drivers tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm64 tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH v2] signals, pkeys: make si_pkey 32 bits
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Dave Hansen <dave@xxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the tip tree
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
• Re: [PATCH] PCI: mvebu: Restrict build to 32-bit ARM
  • From: Bjorn Helgaas <helgaas@xxxxxxxxxx>
• Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• [PATCH] x86, pkeys: fix siginfo ABI breakage from new field
  • From: Dave Hansen <dave@xxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• next-20160226 build: 2 failures 44 warnings (next-20160226)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: "Kirill A. Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: kernel panic on next-20160225
  • From: Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• linux-next: Tree for Feb 26
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• kernel panic on next-20160225
  • From: Junxiao Bi <junxiao.bi@xxxxxxxxxx>
• 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 tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• linux-next: manual merge of the tip tree with the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tip tree with the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: Daniel Borkmann <daniel@xxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the sunxi tree with Linus' and the arm-soc trees
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20160225 build: 2 failures 44 warnings (next-20160225)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 25
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-02-24-16-18 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• linux-next: manual merge of the renesas tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 24
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• next-20160224 build: 1 failures 14 warnings (next-20160224)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the mac80211-next tree
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 24
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• linux-next: Tree for Feb 24
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the mac80211-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pci tree with the pci-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arc tree with the arc-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 17
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• next-20160223 build: 3 failures 8 warnings (next-20160223)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 23
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the staging tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the staging tree with the crypto tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the f2fs tree with Linus' tree
  • From: Jaegeuk Kim <jaegeuk@xxxxxxxxxx>
• linux-next: manual merge of the f2fs tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Marc Zyngier <marc.zyngier@xxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Brian Starkey <brian.starkey@xxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Marc Zyngier <marc.zyngier@xxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Brian Starkey <brian.starkey@xxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Marc Zyngier <marc.zyngier@xxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Jean-Philippe Brucker <Jean-Philippe.Brucker@xxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• next-20160222 build: 5 failures 9 warnings (next-20160222)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 22
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the staging tree with the crypto 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: build failure after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the crypto tree with the f2fs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the crypto tree with the net tree
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: next-20160217 build: 3 failures 14 warnings (next-20160217)
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 19 (rapidio: rio_mport_cdev.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the tip tree
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH next] ARM: virt: fix build of hyp-stub
  • From: Jean-Philippe Brucker <Jean-Philippe.Brucker@xxxxxxx>
• Re: linux-next: build failure after merge of the wireless-drivers-next tree
  • From: Kalle Valo <kvalo@xxxxxxxxxxxxxx>
• next-20160219 build: 4 failures 18 warnings (next-20160219)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 19
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the crypto tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• RE: linux-next: build failure after merge of the net-next tree
  • From: Yuval Mintz <Yuval.Mintz@xxxxxxxxxx>
• [PATCH next] ARM: virt: fix build of hyp-stub
  • From: Vincent Stehlé <vincent.stehle@xxxxxxxxxxx>
• linux-next: build failure after merge of the wireless-drivers-next 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: build failure after merge of the net-next tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH] PCI: mvebu: Restrict build to 32-bit ARM
  • From: Gregory CLEMENT <gregory.clement@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] PCI: mvebu: Restrict build to 32-bit ARM
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH] PCI: mvebu: Restrict build to 32-bit ARM
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] PCI: mvebu: Restrict build to 32-bit ARM
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: [PATCH] PCI: mvebu: Restrict build to 32-bit ARM
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: next-20160217 build: 3 failures 14 warnings (next-20160217)
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: next-20160217 build: 3 failures 14 warnings (next-20160217)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH] PCI: mvebu: Restrict build to 32-bit ARM
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• next-20160218 build: 4 failures 20 warnings (next-20160218)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 18
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block 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: next-20160217 build: 3 failures 14 warnings (next-20160217)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the mvebu tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-02-17-13-16 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: Tree for Feb 17
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 17
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: next-20160217 build: 3 failures 14 warnings (next-20160217)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• next-20160217 build: 3 failures 14 warnings (next-20160217)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH] crypto: fix compile errors of XTS
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: fix compile errors of XTS
  • From: Stephan Mueller <smueller@xxxxxxxxxx>
• linux-next: Tree for Feb 17
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the clockevents tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the crypto 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: build failure after merge of the gpio tree
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• next-20160216 build: 3 failures 14 warnings (next-20160216)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v2] arm64/efi: Make strnlen() available to the EFI namespace
  • From: Will Deacon <will.deacon@xxxxxxx>
• Re: [PATCH v2] arm64/efi: Make strnlen() available to the EFI namespace
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH] arm64/efi: Make strnlen() available to the EFI namespace
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• [PATCH v2] arm64/efi: Make strnlen() available to the EFI namespace
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: linux-next: manual merge of the gpio tree with the pinctrl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the gpio tree with the pinctrl tree
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• linux-next: Tree for Feb 16
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the clk tree with the samsung-krzk tree
  • From: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
• linux-next: manual merge of the clk tree with the samsung-krzk tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the gpio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the gpio tree with the pinctrl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the gpio tree with the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the staging tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the staging tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Peter Maydell <peter.maydell@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH] arm64/efi: Make strnlen() available to the EFI namespace
  • From: Will Deacon <will.deacon@xxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: [PATCH] arm64/efi: Make strnlen() available to the EFI namespace
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• [PATCH] arm64/efi: Make strnlen() available to the EFI namespace
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Marc Zyngier <marc.zyngier@xxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Marc Zyngier <marc.zyngier@xxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Sudeep Holla <sudeep.holla@xxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Sudeep Holla <sudeep.holla@xxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Sudeep Holla <sudeep.holla@xxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: next-20160215 build: 3 failures 14 warnings (next-20160215)
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: next-20160215 build: 3 failures 14 warnings (next-20160215)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: next-20160215 build: 3 failures 14 warnings (next-20160215)
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Robin Murphy <robin.murphy@xxxxxxx>
• Re: next-20160215 build: 3 failures 14 warnings (next-20160215)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• next-20160215 build: 3 failures 14 warnings (next-20160215)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the net-next tree
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: linux-next: arm64 no longer boots with initramfs in qemu tests
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• linux-next: Tree for Feb 15
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the mips tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next: sparc64 crashes due to 'blk-mq: dynamic h/w context count'
  • From: Jens Axboe <axboe@xxxxxxxxx>
• linux-next: arm64 no longer boots with initramfs in qemu tests
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: next: sparc64 crashes due to 'blk-mq: dynamic h/w context count'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• arm qemu test failures due to 'driver-core: platform: probe of-devices only using list of compatibles'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: next: sparc64 crashes due to 'blk-mq: dynamic h/w context count'
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• next: sparc64 crashes due to 'blk-mq: dynamic h/w context count'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 12
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: linux-next: Tree for Feb 12
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: linux-next: Tree for Feb 12
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 12
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: next-20160208 perf build error "tests/bp_signal.c:106:47: error: declaration of ‘signal’ shadows a global declaration [-Werror=shadow]"
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 12
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• next-20160212 build: 2 failures 13 warnings (next-20160212)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 12
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• linux-next: Tree for Feb 12
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm-arm tree with the arm64 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160208 perf build error "tests/bp_signal.c:106:47: error: declaration of ‘signal’ shadows a global declaration [-Werror=shadow]"
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• next-20160211 build: 1 failures 7 warnings (next-20160211)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 11
  • 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: build failure 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: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] irq_work: unhide irq_work_queue_on declaration on non-SMP
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH] irq_work: unhide irq_work_queue_on declaration on non-SMP
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• [PATCH] irq_work: unhide irq_work_queue_on declaration on non-SMP
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: next-20160210 build: 2 failures 4 warnings (next-20160210)
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: next-20160210 build: 2 failures 4 warnings (next-20160210)
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm-misc tree
  • From: Daniel Vetter <daniel@xxxxxxxx>
• Re: linux-next: build failure after merge of the drm-misc tree
  • From: Lukas Wunner <lukas@xxxxxxxxx>
• Re: next-20160210 build: 2 failures 4 warnings (next-20160210)
  • From: Will Deacon <will.deacon@xxxxxxx>
• Re: next-20160210 build: 2 failures 4 warnings (next-20160210)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: next-20160210 build: 2 failures 4 warnings (next-20160210)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• next-20160210 build: 2 failures 4 warnings (next-20160210)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm-misc tree
  • From: Lukas Wunner <lukas@xxxxxxxxx>
• Re: linux-next: build failure after merge of the drm-misc tree
  • From: Daniel Vetter <daniel@xxxxxxxx>
• linux-next: Tree for Feb 10
  • 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 xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the drm-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-02-09-15-03 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: [PATCH] asm-generic: Fix build when __set_fixmap is absent
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH] asm-generic: Fix build when __set_fixmap is absent
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• Re: [PATCH] asm-generic: Fix build when __set_fixmap is absent
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH] asm-generic: Fix build when __set_fixmap is absent
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH] asm-generic: Fix build when __set_fixmap is absent
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• Re: [PATCH] asm-generic: Fix build when __set_fixmap is absent
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: linux-next: Tree for Feb 9
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: linux-next: Tree for Feb 9
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• Re: linux-next: Tree for Feb 9
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: linux-next: Tree for Feb 9
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: linux-next: Tree for Feb 9
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• Re: linux-next: manual merge of the akpm tree with the tip tree
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: linux-next: manual merge of the akpm tree with the tip tree
  • From: Matt Fleming <matt@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 9
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 9
  • From: Mark Rutland <mark.rutland@xxxxxxx>
• next-20160209 build: 1 failures 5 warnings (next-20160209)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 9
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• linux-next: Tree for Feb 9
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xfs tree
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• linux-next: build failure after merge of the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20160208 perf build error "tests/bp_signal.c:106:47: error: declaration of ‘signal’ shadows a global declaration [-Werror=shadow]"
  • From: Vinson Lee <vlee@xxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the gpio tree
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 8 (kernel/memremap.c, PRINTK, WARN)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 8
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 8
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: linux-next: Tree for Feb 8
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• next-20160208 build: 0 failures 5 warnings (next-20160208)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 8
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the tty.current tree
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the tty.current tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: manual merge of the tty tree with the tty.current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the ext4 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-02-05-16-31 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: build failure after merge of the sunxi tree
  • From: Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx>
• next-20160205 build: 0 failures 6 warnings (next-20160205)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 5
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the sunxi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• Re: mmotm 2016-02-03-16-36 uploaded
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: mmotm 2016-02-03-16-36 uploaded
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: mmotm 2016-02-03-16-36 uploaded
  • From: Joonsoo Kim <js1304@xxxxxxxxx>
• Re: mmotm 2016-02-03-16-36 uploaded
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• next-20160204 build: 0 failures 8 warnings (next-20160204)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Feb 4
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the gpio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-02-03-16-36 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 3 (mm, hugepage)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2016-02-02-17-08 uploaded
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• next-20160203 build: 2 failures 8 warnings (next-20160203)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• 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>
• linux-next: Tree for Feb 3
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• 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>
• mmotm 2016-02-02-17-08 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: manual merge of the tip tree with Linus' tree
  • From: Toshi Kani <toshi.kani@xxxxxxx>
• linux-next: manual merge of the tip tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the btrfs-kdave tree
  • From: David Sterba <dsterba@xxxxxxx>
• next-20160202 build: 0 failures 18 warnings (next-20160202)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: manual merge of the btrfs-kdave tree with Linus' tree
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• linux-next: Tree for Feb 2
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the btrfs-kdave tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the btrfs-kdave tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160201 build: 1 failures 25 warnings (next-20160201)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 1
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• linux-next: Tree for Feb 1
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the staging tree with the tty tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the staging tree with the staging.current tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: manual merge of the staging tree with the tty tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the staging tree with the staging.current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the dt-rh tree with the qcom tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Build failures (s390) in -next due to 'mm, printk: introduce new format string for flags'
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Build failures (s390) in -next due to 'mm, printk: introduce new format string for flags'
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• next-20160129 build: 0 failures 10 warnings (next-20160129)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the mac80211 tree
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Jan 29
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the mac80211 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the gpio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20160128 build: 4 failures 9 warnings (next-20160128)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• next-20160128 build: 4 failures 9 warnings (next-20160128)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 28
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2016-01-27-14-04 uploaded
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-01-27-14-04 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• next-20160127 build: 0 failures 9 warnings (next-20160127)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 27
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Add my git tree for linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Vinod Koul <vinod.koul@xxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Vinod Koul <vinod.koul@xxxxxxxxx>
• Re: Add my git tree for linux-next
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Add my git tree for linux-next
  • From: David Sterba <dsterba@xxxxxxx>
• Re: Add my git tree for linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Add my git tree for linux-next
  • From: Chris Mason <clm@xxxxxx>
• Re: Add my git tree for linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Add my git tree for linux-next
  • From: David Sterba <dsterba@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Vinod Koul <vinod.koul@xxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: Tree for Jan 25
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the mips tree with Linus' tree
  • From: Ralf Baechle <ralf@xxxxxxxxxxxxxx>
• next-20160125 build: 0 failures 7 warnings (next-20160125)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 25
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Jan 25
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the mips tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-01-22-16-43 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• next-20160122 build: 0 failures 6 warnings (next-20160122)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 22
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree with Linus' tree
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: linux-next: manual merge of the block tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20160121 build: 0 failures 5 warnings (next-20160121)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: linux-next: build failure 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: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• linux-next: build failure after merge of the akpm-current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Jan 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the tty tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: build warning after merge of the tty tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-01-20-16-10 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• linux-next: manual merge of the pci tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• next-20160120 build: 0 failures 5 warnings (next-20160120)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 20
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20160119 build: 0 failures 6 warnings (next-20160119)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 19
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the audit tree with Linus' tree
  • From: Paul Moore <paul@xxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm 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>
• next-20160118 build: 0 failures 7 warnings (next-20160118)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 18
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the luto-misc tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the luto-misc tree with Linus' tree
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20160115 build: 0 failures 6 warnings (next-20160115)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• linux-next: Tree for Jan 15
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the luto-misc tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drivers-x86 tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20160114 build: 0 failures 6 warnings (next-20160114)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 14
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20160113 build: 0 failures 6 warnings (next-20160113)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: mmotm git tree since-4.4 branch created (was: mmotm 2016-01-12-16-44 uploaded)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• mmotm git tree since-4.4 branch created (was: mmotm 2016-01-12-16-44 uploaded)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the powerpc tree
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• linux-next: Tree for Jan 13
  • 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: linux-next: build failure after merge of the powerpc tree
  • From: "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the rdma tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2016-01-12-16-44 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: strange commit in the parisc-hd tree
  • From: Helge Deller <deller@xxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the aio tree
  • From: Benjamin LaHaise <bcrl@xxxxxxxxx>
• next-20160112 build: 1 failures 6 warnings (next-20160112)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the powerpc tree
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the nettree
  • From: Ido Schimmel <idosch@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: Ido Schimmel <idosch@xxxxxxxxxxxx>
• RE: linux-next: build failure after merge of the drm tree
  • From: "Zhu, Rex" <Rex.Zhu@xxxxxxx>
• linux-next: Tree for Jan 12
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the aio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• RE: next-20160111 build: 2 failures 11 warnings (next-20160111)
  • From: "Bayyavarapu, Maruthi" <Maruthi.Bayyavarapu@xxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the nettree
  • 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: build failure after merge of the drm tree
  • From: Dave Airlie <airlied@xxxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: strange commit in the parisc-hd tree
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: linux-next: strange commit in the parisc-hd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: strange commit in the parisc-hd tree
  • From: Helge Deller <deller@xxxxxx>
• Re: next-20160111 build: 2 failures 11 warnings (next-20160111)
  • From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the cgroup tree with the tip tree
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the vfs tree
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• [PATCH] PCI: designware: Remove unused variable
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• next-20160111 build: 2 failures 11 warnings (next-20160111)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm-current tree
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: [PATCH] [net] phy: micrel: Fix build failure in ksz9031_config_init()
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• linux-next: Tree for Jan 11
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pci tree
  • From: Bjorn Helgaas <helgaas@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the net-next tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the vfs tree with the nsfd tree
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• linux-next: build failure after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the vfs tree with the nsfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the vfs tree with the nfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: strange commit in the parisc-hd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Boqun Feng <boqun.feng@xxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• next-20160108 build: 0 failures 9 warnings (next-20160108)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the vhost tree
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• linux-next: Tree for Jan 8
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the vhost tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the vhost tree
  • From: Minchan Kim <minchan@xxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the vhost tree
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the vhost tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the vhost tree
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the vhost tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the nvdimm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Boqun Feng <boqun.feng@xxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the target-updates tree with the rdma tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: next boot: 564 boots: 59 failed, 448 passed with 57 offline (next-20160107)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Boqun Feng <boqun.feng@xxxxxxxxx>
• Re: linux-next: build failure after merge of the nfs tree
  • From: Trond Myklebust <trond.myklebust@xxxxxxxxxx>
• linux-next: build failure after merge of the nfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the powerpc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next boot: 564 boots: 59 failed, 448 passed with 57 offline (next-20160107)
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 7 (regulator/max8973)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the rcu tree
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the powerpc tree
  • From: "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx>
• Re: next boot: 564 boots: 59 failed, 448 passed with 57 offline (next-20160107)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: next boot: 564 boots: 59 failed, 448 passed with 57 offline (next-20160107)
  • From: Thierry Reding <thierry.reding@xxxxxxxxx>
• Re: next boot: 564 boots: 59 failed, 448 passed with 57 offline (next-20160107)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• next-20160107 build: 0 failures 9 warnings (next-20160107)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 6 (clocksource/fsl_ftm_timer.c)
  • From: Daniel Lezcano <daniel.lezcano@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the powerpc tree
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• linux-next: Tree for Jan 7
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the target-updates tree with the rdma tree
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the powerpc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the rcu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the powerpc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: error while fetching the microblaze tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: error while fetching the microblaze tree
  • From: Michal Simek <monstr@xxxxxxxxx>
• linux-next: manual merge of the target-updates tree with the rdma tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the vfs tree
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: error while fetching the microblaze tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 6 (clocksource/fsl_ftm_timer.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Or Gerlitz <ogerlitz@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Anna Schumaker <Anna.Schumaker@xxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Chuck Lever <chuck.lever@xxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Steve Capper <steve.capper@xxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Or Gerlitz <ogerlitz@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Chuck Lever <chuck.lever@xxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Or Gerlitz <ogerlitz@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Chuck Lever <chuck.lever@xxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Or Gerlitz <ogerlitz@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Chuck Lever <chuck.lever@xxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Or Gerlitz <ogerlitz@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Chuck Lever <chuck.lever@xxxxxxxxxx>
• next-20160106 build: 0 failures 13 warnings (next-20160106)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Sudeep Holla <sudeep.holla@xxxxxxx>
• Re: linux-next: manual merge of the pm tree with the i2c tree
  • From: Wolfram Sang <wsa@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the kbuild tree
  • From: Michal Marek <mmarek@xxxxxxx>
• linux-next: Tree for Jan 6
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tip tree with the h8300 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the spi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the pm tree with the i2c tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• linux-next: manual merge of the pm tree with the i2c tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• mmotm 2016-01-05-15-24 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: manual merge of the rdma tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Steve Capper <steve.capper@xxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the net-next tree
  • From: Or Gerlitz <ogerlitz@xxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the mmc-uh tree
  • From: Thierry Reding <treding@xxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Sudeep Holla <sudeep.holla@xxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Mark Brown <broonie@xxxxxxxxxx>
• next-20160105 build: 4 failures 16 warnings (next-20160105)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 5
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the ext4 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the l2-mtd tree with the mtd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rdma tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the i2c tree
  • From: Wolfram Sang <wsa@xxxxxxxxxxxxx>
• Re: next-20160104 build: 3 failures 15 warnings (next-20160104)
  • From: "Rafael J. Wysocki" <rafael.j.wysocki@xxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the i2c tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: next-20160104 build: 3 failures 15 warnings (next-20160104)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: next-20160104 build: 3 failures 15 warnings (next-20160104)
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: next-20160104 build: 3 failures 15 warnings (next-20160104)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: next-20160104 build: 3 failures 15 warnings (next-20160104)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the ext4 tree
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: linux-next: manual merge of the integrity tree with the vfs tree
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• next-20160104 build: 3 failures 15 warnings (next-20160104)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• linux-next: Tree for Jan 4
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the integrity tree with the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the integrity tree with the vfs tree
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the integrity tree with the vfs tree
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the integrity tree with the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• linux-next: manual merge of the integrity tree with the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the security tree with the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rdma tree with the nfsd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the security tree with the vfs tree
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the ext4 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: unmet direct dependencies in -next
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH] ima_write_policy() optimizations;
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: linux-next: manual merge of the security tree with the vfs tree
  • From: Petko Manolov <petkan@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the security tree with the vfs tree
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the libata tree
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 6/8] cgroup: mount cgroupns-root when inside non-init cgroupns
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 6/8] cgroup: mount cgroupns-root when inside non-init cgroupns
  • From: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx>
• Re: [PATCH 6/8] cgroup: mount cgroupns-root when inside non-init cgroupns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH v2 1/3] device property: add spaces to PROPERTY_ENTRY_STRING macro
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Dec 31 (net/xfrm/xfrm_input.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• RE: linux-next: manual merge of the akpm-current tree with the jc_docs tree
  • From: "Elliott, Robert (Persistent Memory)" <elliott@xxxxxxx>
• Re: linux-next: build failure after merge of the thermal-soc tree
  • From: Srinivas Pandruvada <srinivas.pandruvada@xxxxxxxxxxxxxxx>
• next-20151231 build: 2 failures 16 warnings (next-20151231)
  • From: Build bot for Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH 6/8] cgroup: mount cgroupns-root when inside non-init cgroupns
  • From: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx>
• linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the security tree with the vfs tree
  • From: Petko Manolov <petkan@xxxxxxxxxxxx>
• 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 jc_docs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the nvdimm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the jc_docs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>