Linux Next

• Thread Index

• Re: linux-next: build failure after merge of the final tree (staging tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (staging tree related)
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: linux-next: Tree for Mar 6 (hid)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (staging tree related)
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: linux-next: failure to fetch the watchdog tree
  • From: Wim Van Sebroeck <wim@xxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (gpio tree relatred)
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• linux-next: Tree for Mar 6
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the final tree (gpio tree relatred)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (staging tree related)
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: build failure after merge of the final tree (staging tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: failure to fetch the watchdog tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] leds-ot200: Fix misbehavior caused by wrong bit masks
  • From: Bryan Wu <cooloney@xxxxxxxxx>
• Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1
  • From: Imre Deak <imre.deak@xxxxxxxxx>
• Re: linux-next: Tree for Mar 5 (iio)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: Tree for Mar 5
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm-intel tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: error fetching the osd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Mar 4 (dm-cache-target)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Mar 4 (dm-cache-target)
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v3 resend] procfs: Improve Scaling in proc
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Mar 4 (iio)
  • From: Lars-Peter Clausen <lars@xxxxxxxxxx>
• Re: linux-next: Tree for Mar 4 (dm-cache-target)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Mar 4 (iio)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: consider tidying up the xen-two tree
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: manual merge of the signal tree with Linus' tree
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (akpm tree related)
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH] leds-ot200: Fix misbehavior caused by wrong bit masks
  • From: Christian Gmeiner <christian.gmeiner@xxxxxxxxx>
• linux-next: Tree for Mar 4
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the final tree (akpm tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the final tree (akpm tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the gpio tree
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the gpio tree
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• linux-next: manual merge of the akpm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the signal tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the signal tree with Linus' 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 device-mapper tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: consider tidying up the xen-two tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [git.k.o] Old linux-next WebGit points to $NewWebGitURL/tree
  • From: Konstantin Ryabitsev <mricon@xxxxxxxxxx>
• Re: [git.k.o] Old linux-next WebGit points to $NewWebGitURL/tree
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [git.k.o] Old linux-next WebGit points to $NewWebGitURL/tree
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• [git.k.o] Old linux-next WebGit points to $NewWebGitURL/tree
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Pulling linux-next GIT
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: mmotm 2013-03-01-15-50 uploaded (strict user copy)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the ftrace tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the ftrace tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build failure after merge of the ftrace tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2013-03-01-15-50 uploaded (strict user copy)
  • From: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the ftrace tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build failure after merge of the nfsd tree
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: mmotm 2013-03-01-15-50 uploaded (strict user copy)
  • From: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the ftrace tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2013-03-01-15-50 uploaded (early_printk)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2013-03-01-15-50 uploaded (strict user copy)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the ftrace tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• mmotm 2013-03-01-15-50 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: build warning after merge of the char-misc tree
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: build warning after merge of the char-misc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: build warning after merge of the char-misc tree
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Pulling linux-next GIT
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Pulling linux-next GIT
  • From: Konstantin Ryabitsev <mricon@xxxxxxxxxx>
• Re: [PATCH] libata-acpi.c: fix copy and paste mistake in ata_acpi_register_power_resource
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Pulling linux-next GIT
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [Drbd-dev] linux-next: Tree for Feb 23 (drbd)
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: Pulling linux-next GIT
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Pulling linux-next GIT
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Pulling linux-next GIT
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• linux-next: Tree for Mar 1
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the ftrace tree
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• linux-next: manual merge of the kvm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the ftrace tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the bluetooth tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the nfsd tree
  • From: "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx>
• linux-next: build failure after merge of the nfsd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the nfsd tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: no-MMU build failure
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• no-MMU build failure
  • From: Mark Salter <msalter@xxxxxxxxxx>
• Re: [dm-devel] linux-next: Tree for Feb 28 (dm-cache)
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 28 (dm-cache)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1
  • From: Paulo Zanoni <przanoni@xxxxxxxxx>
• Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [git pull] drm merge for 3.9-rc1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1
  • From: Paulo Zanoni <przanoni@xxxxxxxxx>
• Re: [git pull] drm merge for 3.9-rc1
  • From: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: JFFS2 corruption
  • From: Mark Jackson <mpfj-list@xxxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• RE: linux-next: JFFS2 corruption
  • From: "Philip, Avinash" <avinashphilip@xxxxxx>
• linux-next: Tree for Feb 28
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the final tree (device-mapper tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [git pull] drm merge for 3.9-rc1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [git pull] drm merge for 3.9-rc1
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: JFFS2 deadlock
  • From: Mark Jackson <mpfj-list@xxxxxxxxxx>
• Re: linux-next: JFFS2 corruption
  • From: Mark Jackson <mpfj-list@xxxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 23 [ perf: NULL pointer dereference perf_init_event() ]
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 23 [ perf: NULL pointer dereference perf_init_event() ]
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 23 [ perf: NULL pointer dereference perf_init_event() ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
  • From: Wim Van Sebroeck <wim@xxxxxxxxx>
• linux-next: Tree for Feb 27
  • 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: manual merge of the renesas tree with Linus' tree
  • From: Simon Horman <horms@xxxxxxxxxxxx>
• linux-next: manual merge of the renesas tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: JFFS2 deadlock
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: JFFS2 corruption
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: JFFS2 deadlock
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] conversion to bio batch completion
  • From: Asai Thambi S P <asamymuthupa@xxxxxxxxxx>
• linux-next: JFFS2 corruption
  • From: Mark Jackson <mpfj-list@xxxxxxxxxx>
• linux-next: JFFS2 deadlock
  • From: Mark Jackson <mpfj-list@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 23 [ perf: NULL pointer dereference perf_init_event() ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 26 [ vfs | mm/shmem ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: manual merge of the infiniband tree with Linus' tree
  • From: Or Gerlitz <ogerlitz@xxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 24
  • From: Stephen Rothwell <sfr@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>
• linux-next: manual merge of the infiniband tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] block: fix part_pack_uuid() build error
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] block: fix part_pack_uuid() build error
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 01/11] ARM: disable virt_to_bus/virt_to_bus almost everywhere
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird name <SYSV00000000> ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird name <SYSV00000000> ]
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird name <SYSV00000000> ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH 01/11] ARM: disable virt_to_bus/virt_to_bus almost everywhere
  • From: Vineet Gupta <Vineet.Gupta1@xxxxxxxxxxxx>
• Re: [PATCH] kbuild: Fix reading of .config in link-vmlinux.sh
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weird name <SYSV00000000> ]
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] kbuild: Fix reading of .config in link-vmlinux.sh
  • From: Michal Marek <mmarek@xxxxxxx>
• [PATCH] kbuild: Fix reading of .config in link-vmlinux.sh
  • From: Michal Marek <mmarek@xxxxxxx>
• Re: linux-next: build failure after merge of the kbuild tree
  • From: Michal Marek <mmarek@xxxxxxx>
• Re: linux-next: build failure after merge of the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the kbuild tree
  • From: Michal Marek <mmarek@xxxxxxx>
• Re: linux-next: manual merge of the metag tree with Linus' tree
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• linux-next: Tree for Feb 23
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the vfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] block: fix part_pack_uuid() build error
  • From: James Morris <jmorris@xxxxxxxxx>
• linux-next: manual merge of the watchdog tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the metag tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: please clean up
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] block: fix part_pack_uuid() build error
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH] block: fix part_pack_uuid() build error
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• [PATCH] block: fix part_pack_uuid() build error
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] ima: fix part_pack_uuid() build error
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 2/2] lib/scatterlist: use page iterator in the mapping iterator
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: [PATCH v3 2/2] lib/scatterlist: use page iterator in the mapping iterator
  • From: Imre Deak <imre.deak@xxxxxxxxx>
• Re: [PATCH] leds-ot200: Fix misbehavior caused by wrong bit masks
  • From: Christian Gmeiner <christian.gmeiner@xxxxxxxxx>
• Re: [PATCH v3 2/2] lib/scatterlist: use page iterator in the mapping iterator
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: [PATCH] ima: fix part_pack_uuid() build error
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH] ima: fix part_pack_uuid() build error
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• [PATCH] ima: fix part_pack_uuid() build error
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the infiniband tree with Linus' tree
  • From: Or Gerlitz <or.gerlitz@xxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (drm tree related)
  • From: Rob Clark <robdclark@xxxxxxxxx>
• linux-next: Tree for Feb 22
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the final tree (drm tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the writeback tree with the btrfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the infiniband tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 01/11] ARM: disable virt_to_bus/virt_to_bus almost everywhere
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the signal tree with the powerpc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the signal tree with the powerpc tree
  • From: Michael Neuling <mikey@xxxxxxxxxxx>
• Re: [PATCH 01/11] ARM: disable virt_to_bus/virt_to_bus almost everywhere
  • From: Vineet Gupta <Vineet.Gupta1@xxxxxxxxxxxx>
• RE: linux-next: build failure after merge of the xen-two tree
  • From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
• Re: linux-next: manual merge of the signal tree with the powerpc tree
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• linux-next: Tree for Feb 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the signal tree with the powerpc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the mips tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] block/partitions/efi.c: ensure that the GPT header is at least the size of the structure.
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH -next] security/integrity/ima: make part_pack_uuid() always visible
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• [PATCH -next] security/integrity/ima: make part_pack_uuid() always visible
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: dw_mmc build broken in next-20130220 (was Re: [PATCH v3 2/2] lib/scatterlist: use page iterator in the mapping iterator)
  • From: Imre Deak <imre.deak@xxxxxxxxx>
• Re: linux-next: Tree for Feb 19 (security/integrity/ima)
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [PATCHv2] idr: always do slow path when hint is uninitialized
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH] events: always do slow path when trying to find a pmu
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• [PATCHv2] idr: always do slow path when hint is uninitialized
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH] events: always do slow path when trying to find a pmu
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [PATCH] events: always do slow path when trying to find a pmu
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• dw_mmc build broken in next-20130220 (was Re: [PATCH v3 2/2] lib/scatterlist: use page iterator in the mapping iterator)
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• since-3.8 branch opened for mm git tree (was: mmotm 2013-02-19-17-20 uploaded)
  • From: Michal Hocko <mhocko@xxxxxxx>
• Re: [PATCH 01/11] ARM: disable virt_to_bus/virt_to_bus almost everywhere
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: [PATCH 01/11] ARM: disable virt_to_bus/virt_to_bus almost everywhere
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 01/11] ARM: disable virt_to_bus/virt_to_bus almost everywhere
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• [PATCH] block/partitions/efi.c: ensure that the GPT header is at least the size of the structure.
  • From: Peter Jones <pjones@xxxxxxxxxx>
• linux-next: build warning after merge of the akpm tree
  • From: Peter Jones <pjones@xxxxxxxxxx>
• Re: linux-next: manual merge of the pm tree with the pci tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• linux-next: Tree for Feb 20
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm tree with the net-next tree
  • From: Cong Wang <xiyou.wangcong@xxxxxxxxx>
• linux-next: build warning after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the modem_shm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the vhost tree with the virtio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the driver-core tree with the virtio tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: manual merge of the driver-core tree with the virtio tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pm tree with the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2013-02-19-17-20 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: build failure after merge of the mips tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 19 (security/integrity/ima)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: Broken build due to 6aed8ec "drm: review locking for drm_fb_helper_restore_fbdev_mode"
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: Broken build due to 6aed8ec "drm: review locking for drm_fb_helper_restore_fbdev_mode"
  • From: Daniel Vetter <daniel.vetter@xxxxxxxx>
• Broken build due to 6aed8ec "drm: review locking for drm_fb_helper_restore_fbdev_mode"
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: Linux 3.8
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm-intel tree
  • From: Daniel Vetter <daniel.vetter@xxxxxxxx>
• linux-next: Tree for Feb 19
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the wireless-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Linux 3.8
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm-intel tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: interesting commits in the cifs tree
  • From: Steve French <smfrench@xxxxxxxxx>
• 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>
• Re: linux-next: interesting commits in the cifs tree
  • From: Steve French <smfrench@xxxxxxxxx>
• linux-next: interesting commits in the cifs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH linux-next]cputime: fix compiler warning caused by timeval_to_cputime()
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: linux-next: manual merge of the pm tree with the pci tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: manual merge of the pm tree with the pci tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: manual merge of the tip tree with the kbuild tree
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• linux-next: Tree for Feb 18
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the userns tree with the nfsd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the input tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the usb tree with the driver-core tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: manual merge of the usb tree with the driver-core tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tip tree with the kbuild tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pm tree with the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pm tree with the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the mips tree
  • From: Hauke Mehrtens <hauke@xxxxxxxxxx>
• linux-next: build failure after merge of the mips tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• [PATCH 2/2] xen/acpi: xen cpu hotplug minor updates
  • From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
• [PATCH 1/2] xen/acpi: xen memory hotplug minor updates
  • From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
• RE: linux-next: manual merge of the acpi tree with the pm tree
  • From: "Zheng, Lv" <lv.zheng@xxxxxxxxx>
• RE: linux-next: build failure after merge of the xen-two tree
  • From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
• [PATCH linux-next] Remove unused variable in mwait_play_dead()
  • From: Li Zhong <zhong@xxxxxxxxxxxxxxxxxx>
• [PATCH linux-next]cputime: fix compiler warning caused by timeval_to_cputime()
  • From: Li Zhong <zhong@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH] leds-ot200: Fix misbehavior caused by wrong bit masks
  • From: Bryan Wu <cooloney@xxxxxxxxx>
• Re: linux-next: build warning after merge of the char-misc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH -next] i2c: fix i2c-ismt.c printk format warning
  • From: Wolfram Sang <wsa@xxxxxxxxxxxxx>
• [PATCH -next] i2c: fix i2c-ismt.c printk format warning
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: build warning after merge of the char-misc tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• RE: linux-next: build failure after merge of the xen-two tree
  • From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
• Re: linux-next: build warning after merge of the char-misc tree
  • From: Greg KH <greg@xxxxxxxxx>
• RE: linux-next: build failure after merge of the xen-two tree
  • From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
• RE: linux-next: build failure after merge of the xen-two tree
  • From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
• [PATCH] xen/acpi: updates the argument of .remove operation of xen cpu/mem hotplug
  • From: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>
• Re: linux-next: manual merge of the driver-core tree with the tree
  • From: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the drm-intel tree
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: linux-next: manual merge of the pm tree with the pci tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: Tree for Feb 15
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: build failure after merge of the drm-intel tree
  • From: Daniel Vetter <daniel.vetter@xxxxxxxx>
• Re: linux-next: Tree for Feb 15
  • From: "Arend van Spriel" <arend@xxxxxxxxxxxx>
• linux-next: Tree for Feb 15
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the workqueues tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the idle tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the char-misc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the driver-core tree with the tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: manual merge of the driver-core tree with the tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the xen-two tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the drm-intel tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pm tree with the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Joe Millenbach <jmillenbach@xxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• linux-next: Tree for Feb 14
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm tree with the tip tree
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• linux-next: manual merge of the akpm tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH -next 1/1] net: skbuff: fix compile error in skb_panic()
  • From: Jean Sacren <sakiwit@xxxxxxxxx>
• Re: linux-next: Tree for Feb 13 (virtio_console)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH -next 1/1] net: skbuff: fix compile error in skb_panic()
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH] leds-ot200: Fix misbehavior caused by wrong bit masks
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] leds-ot200: Fix misbehavior caused by wrong bit masks
  • From: Christian Gmeiner <christian.gmeiner@xxxxxxxxx>
• Re: [PATCH v2] gpio: devm_gpio_* support should not depend on GPIOLIB
  • From: Shawn Guo <shawn.guo@xxxxxxxxxx>
• Re: linux-next: manual merge of the ia64 tree with Linus' tree
  • From: Matt Fleming <matt.fleming@xxxxxxxxx>
• Re: [PATCH -next 1/1] net: skbuff: fix compile error in skb_panic()
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• [PATCH -next 1/1] net: skbuff: fix compile error in skb_panic()
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• linux-next: Tree for Feb 13
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the ipsec-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the samsung tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the metag 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 ia64 tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the acpi tree with the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 12 (drm_pci.c)
  • From: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 12 [ WARNING: at drivers/tty/tty_buffer.c:427 flush_to_ldisc | tty is NULL ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related))
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: Should SPARC use cpuidle?
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: Should SPARC use cpuidle?
  • From: Len Brown <lenb@xxxxxxxxxx>
• Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related))
  • From: Len Brown <lenb@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (acpi tree related)
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 12 (drm_pci.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the arm-soc tree with the mfd tree
  • From: Samuel Ortiz <sameo@xxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the arm-soc tree with the mfd tree
  • From: Roger Quadros <rogerq@xxxxxx>
• Re: linux-next: manual merge of the arm-soc tree with the metag tree
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH v2] gpio: devm_gpio_* support should not depend on GPIOLIB
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• linux-next: Tree for Feb 12
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the usb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the metag tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Yinghai Lu <yinghai@xxxxxxxxxx>
• linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Yinghai Lu <yinghai@xxxxxxxxxx>
• Re: linux-next: manual merge of the acpi tree with the pm tree
  • From: Len Brown <lenb@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (acpi tree related)
  • From: Len Brown <lenb@xxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
• Re: [PATCH] of: fix recursive locking in of_get_next_available_child()
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• Re: [PATCH next v2] OF: convert devtree lock from rw_lock to raw spinlock
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• Re: [PATCH next v2] OF: convert devtree lock from rw_lock to raw spinlock
  • From: Rob Herring <robherring2@xxxxxxxxx>
• Re: [PATCH next v2] OF: convert devtree lock from rw_lock to raw spinlock
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• [PATCH] of: fix recursive locking in of_get_next_available_child()
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Yinghai Lu <yinghai@xxxxxxxxxx>
• Re: [PATCH v2] gpio: devm_gpio_* support should not depend on GPIOLIB
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Yinghai Lu <yinghai@xxxxxxxxxx>
• Re: [PATCH next v2] OF: convert devtree lock from rw_lock to raw spinlock
  • From: Rob Herring <robherring2@xxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Yinghai Lu <yinghai@xxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH next v2] OF: convert devtree lock from rw_lock to raw spinlock
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Yinghai Lu <yinghai@xxxxxxxxxx>
• Re: linux-next: manual merge of the arm-soc tree with the mfd tree
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: linux-next: manual merge of the arm-soc tree with the mfd tree
  • From: Tony Lindgren <tony@xxxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (acpi tree related)
  • From: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 11 (intel_pstate.c)
  • From: Dirk Brandewie <dirk.brandewie@xxxxxxxxx>
• Re: [PATCH v2] gpio: devm_gpio_* support should not depend on GPIOLIB
  • From: Max Filippov <jcmvbkbc@xxxxxxxxx>
• Re: linux-next: Tree for Feb 11 (intel_pstate.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the tty tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH v2] gpio: devm_gpio_* support should not depend on GPIOLIB
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the akpm tree
  • From: Amir Vadai <amirv@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the driver-core tree with the pm tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Jiri Slaby <jslaby@xxxxxxx>
• Re: [PATCH v2] wlcore: remove newly introduced alloc/OOM messages
  • From: Felipe Balbi <balbi@xxxxxx>
• [PATCH v2] wlcore: remove newly introduced alloc/OOM messages
  • From: Luciano Coelho <coelho@xxxxxx>
• Re: [PATCH] wlcore: remove newly introduced alloc/OOM messages
  • From: Felipe Balbi <balbi@xxxxxx>
• Re: [PATCH] wlcore: remove newly introduced alloc/OOM messages
  • From: Luciano Coelho <coelho@xxxxxx>
• Re: [PATCH] wlcore: remove newly introduced alloc/OOM messages
  • From: Luciano Coelho <coelho@xxxxxx>
• Re: [PATCH] wlcore: remove newly introduced alloc/OOM messages
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH] wlcore: remove newly introduced alloc/OOM messages
  • From: Luciano Coelho <coelho@xxxxxx>
• Re: linux-next: manual merge of the wireless-next tree with the net-next tree
  • From: Luciano Coelho <coelho@xxxxxx>
• linux-next: Tree for Feb 11
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the wireless-next tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the final tree (acpi tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the wireless-next tree with the net-next tree
  • From: Luciano Coelho <coelho@xxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Yinghai Lu <yinghai@xxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the usb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the usb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the tty tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the driver-core tree with the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the iommu tree with the sound-asoc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the wireless-next tree with the net-next tree
  • From: Joe Perches <joe@xxxxxxxxxxx>
• linux-next: manual merge of the wireless-next tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the acpi tree with the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the acpi tree with the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Yinghai Lu <yinghai@xxxxxxxxxx>
• Re: [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] gpio: devm_gpio_* support should not depend on GPIOLIB
  • From: Max Filippov <jcmvbkbc@xxxxxxxxx>
• [Bisected] [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the samsung tree with the arm-soc tree
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the nfsd tree
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [linux-pm] linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Hillf Danton <dhillf@xxxxxxxxx>
• Re: linux-next: manual merge of the watchdog tree with the mfd tree
  • From: Wim Van Sebroeck <wim@xxxxxxxxx>
• Re: linux-next build conflict between modules and metag trees (LOCKDEP_NOW_UNRELIABLE)
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 8 [ smp|cpufreq: WARNING: at kernel/smp.c:245 smp_call_function_single ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 8 [ idr fixes from akpm-tree ]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next build conflict between modules and metag trees (LOCKDEP_NOW_UNRELIABLE)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the nfsd tree
  • From: Stanislav Kinsbursky <skinsbursky@xxxxxxxxxxxxx>
• Re: linux-next build conflict between modules and metag trees (LOCKDEP_NOW_UNRELIABLE)
  • From: Vineet Gupta <Vineet.Gupta1@xxxxxxxxxxxx>
• linux-next: Tree for Feb 8
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next build conflict between modules and metag trees (LOCKDEP_NOW_UNRELIABLE)
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• linux-next: manual merge of the watchdog tree with the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the sound-asoc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] staging/goldfish: Add MTD dependency to KCONFIG
  • From: Peter Huewe <peterhuewe@xxxxxx>
• Re: linux-next: Tree for Feb 6 [WARNING: at kernel/sched/clock.c:219 sched_clock_cpu+0xf9/0x110()]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH v2] ipc: convert to idr_alloc()
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 7 (staging/goldfish)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 7 (drivers/misc/mei)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [PATCH v2] ipc: convert to idr_alloc()
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• linux-next build conflict between modules and metag trees (LOCKDEP_NOW_UNRELIABLE)
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Heads up on a device tree change
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: mmotm 2013-02-06-17-13 uploaded (alsa)
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: manual merge of the signal tree with the s390 tree
  • From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the kvm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for Feb 7
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the akpm-current tree with the kvm tree
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the kvm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: mmotm 2013-02-06-17-13 uploaded (alsa)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: mmotm 2013-02-06-17-13 uploaded (iio)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: manual merge of the signal tree with the s390 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the iommu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the iommu 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 tip tree with the s390 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2013-02-06-17-13 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: linux-next: build failure after merge of the final tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Heads up on a device tree change
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• Re: Heads up on a device tree change
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Heads up on a device tree change
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the metag tree with the arc tree
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: EXPORT_SYMBOL(min_low_pfn);
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 6 [WARNING: at kernel/sched/clock.c:219 sched_clock_cpu+0xf9/0x110()]
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: build failure after merge of the block tree
  • From: Jens Axboe <axboe@xxxxxxxxx>
• linux-next: Tree for Feb 6
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the final tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the nfsd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the driver-core tree with the spi tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the driver-core tree with the iommu tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the crypto tree with the net-next tree
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the driver-core tree with the iommu tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the driver-core tree with the spi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm tree with the arm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the spi tree with the sound-asoc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the battery tree with the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the crypto tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2013-02-05-17-21 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• Re: EXPORT_SYMBOL(min_low_pfn);
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the metag tree with the arc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] init: fix name of root device in /proc/mounts
  • From: William Hubbs <w.d.hubbs@xxxxxxxxx>
• Re: [PATCH] init: fix name of root device in /proc/mounts
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] init: fix name of root device in /proc/mounts
  • From: William Hubbs <w.d.hubbs@xxxxxxxxx>
• [PATCH] init: fix name of root device in /proc/mounts
  • From: William Hubbs <w.d.hubbs@xxxxxxxxx>
• [-next-20130204] usb/hcd: irq 18: nobody cared
  • From: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>
• EXPORT_SYMBOL(min_low_pfn);
  • From: Tony Luck <tony.luck@xxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: linux-next: build failure after merge of the xen-two tree
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: Revert "console: implement lockdep support for console_lock"
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Revert "console: implement lockdep support for console_lock"
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: linux-next: Tree for Feb 5
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• linux-next: Tree for Feb 5
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] netfilter: fix missing dependencies for NETFILTER_XT_MATCH_CONNLABEL
  • From: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: Christoph Lameter <cl@xxxxxxxxx>
• linux-next: build failure after merge of the sound-asoc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: CPU hotplug hang due to "swap: make each swap partition have one address_space"
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: [PATCH] leds-ot200: Fix error caused by shifted mask
  • From: Bryan Wu <cooloney@xxxxxxxxx>
• Re: linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the clk tree with the arm-soc tree
  • From: Mike Turquette <mturquette@xxxxxxxxxx>
• Re: CPU hotplug hang due to "swap: make each swap partition have one address_space"
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries"
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: [PATCH] leds-ot200: Fix error caused by shifted mask
  • From: Christian Gmeiner <christian.gmeiner@xxxxxxxxx>
• Re: linux-next: Tree for Feb 4
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: [PATCH] regmap: include linux/sched.h to fix build
  • From: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• linux-next: Tree for Feb 4
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm tree with the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the signal tree with the mips tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pinctrl tree with the battery tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the mfd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the driver-core tree with the net-next tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: CPU hotplug hang due to "swap: make each swap partition have one address_space"
  • From: Joseph Lo <josephl@xxxxxxxxxx>
• linux-next: manual merge of the driver-core tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the driver-core tree with the net-next tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the xen-two tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the security tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: CPU hotplug hang due to "swap: make each swap partition have one address_space"
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] netfilter: fix missing dependencies for NETFILTER_XT_MATCH_CONNLABEL
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the nfsd tree
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• [PATCH] netfilter: fix missing dependencies for NETFILTER_XT_MATCH_CONNLABEL
  • From: Florian Westphal <fw@xxxxxxxxx>
• [PATCH] regmap: include linux/sched.h to fix build
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Feb 2 (netfilter)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• linux-next: Tree for Feb 2
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the cortex tree with the arm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with the watchdog tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the nfsd tree
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• linux-next: manual merge of the akpm-current tree with Linus' 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: manual merge of the cortex tree with the arm tree
  • From: Russell King <rmk@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tegra tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tegra tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the cortex tree with the arm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warnings after merge of the l2-mtd tree
  • From: Stefan Roese <sr@xxxxxxx>
• Re: linux-next: manual merge of the net-next tree with the net tree
  • From: Jiri Pirko <jiri@xxxxxxxxxxx>
• linux-next: build warning after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• CPU hotplug hang due to "swap: make each swap partition have one address_space"
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• linux-next: build warnings after merge of the l2-mtd 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>
• linux-next: build failure after merge of the nfsd tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] leds-ot200: Fix error caused by shifted mask
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] leds-ot200: Fix error caused by shifted mask
  • From: Christian Gmeiner <christian.gmeiner@xxxxxxxxx>
• Re: Linux-Next releases this week?
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Revert "console: implement lockdep support for console_lock"
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: Revert "console: implement lockdep support for console_lock"
  • From: Daniel Vetter <daniel.vetter@xxxxxxxx>
• Re: Revert "console: implement lockdep support for console_lock"
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Linux-Next releases this week?
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: next-20130128 lockdep whinge in sys_swapon()
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: BUG: circular locking dependency detected
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: BUG: circular locking dependency detected
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH] watchdog: da9055_wdt needs to select WATCHDOG_CORE
  • From: Wim Van Sebroeck <wim@xxxxxxxxx>
• Re: [PATCH -next] staging: comedi: ISA DMA drivers should depend on ISA_DMA_API
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• RE: [PATCH -next] staging: comedi: ISA DMA drivers should depend on ISA_DMA_API
  • From: H Hartley Sweeten <hartleys@xxxxxxxxxxxxxxxxxxx>
• linux-next: no tree for Jan 30
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the samsung tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the samsung tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the arm-soc tree with the pinctrl tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the pm tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: manual merge of the pm tree with the pci tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• [PATCH -next] staging: comedi: ISA DMA drivers should depend on ISA_DMA_API
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• linux-next: build warning after merge of the tip tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the battery tree with Linus' tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pm tree with the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the usb tree
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• RE: linux-next: build failure after merge of the usb tree
  • From: "Lan, Tianyu" <tianyu.lan@xxxxxxxxx>
• Re: linux-next: build failure after merge of the usb tree
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the usb tree with the driver-core tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Joe Millenbach <jmillenbach@xxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: James Hogan <james.hogan@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Joe Millenbach <jmillenbach@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• [PATCH] watchdog: da9055_wdt needs to select WATCHDOG_CORE
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• RE: linux-next: build failure after merge of the usb tree
  • From: "Lan, Tianyu" <tianyu.lan@xxxxxxxxx>
• Re: linux-next: build failure after merge of the usb tree
  • From: Lan Tianyu <tianyu.lan@xxxxxxxxx>
• Re: linux-next: build failure after merge of the usb tree
  • From: Lan Tianyu <tianyu.lan@xxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with the input tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the usb tree with the tty tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: build failure after merge of the usb tree
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• linux-next: Tree for Jan 28
  • 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: manual merge of the char-misc tree with the sound-asoc tree
  • From: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the char-misc tree with the sound-asoc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the usb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the usb tree with the driver-core tree
  • From: Felipe Balbi <balbi@xxxxxx>
• linux-next: manual merge of the usb tree with the driver-core tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the usb tree with the driver-core tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the usb tree with the tty tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tty tree with the input tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Boot crashes due to global async pending list
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• [next-20130124][next-20130125] Fix available for broken PM-suspend
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (kvm)
  • From: Avi Kivity <avi.kivity@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: Tree for Jan 25 (BROKEN suspend)
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c])
  • From: Jonathan Cameron <jic23@xxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (kvm)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tty tree with Linus' tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the usb tree with Linus' tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Crash with 9fdb04c "async: replace list of active domains with global list of pending items"
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH] extcon: max77693: Fix bug of build error related to INPUT subsystem
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 25 (kvm)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH next-20130124] Sound: pci: Fix unused variable warning in patch_sigmatel.c
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: [PATCH next-20130124] Sound: pci: Fix unused variable warning in patch_sigmatel.c
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH next-20130124] Sound: pci: Fix unused variable warning in patch_sigmatel.c
  • From: Takashi Iwai <tiwai@xxxxxxx>
• linux-next: Tree for Jan 25
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Crash with 9fdb04c "async: replace list of active domains with global list of pending items"
  • From: Stephen Warren <swarren@xxxxxxxxxxxxx>
• [PATCH] extcon: max77693: Fix bug of build error related to INPUT subsystem
  • From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
• Re: linux-next: Tree for Jan 24 (extcon-max77693)
  • From: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
• Re: [PATCH] serial: pch_uart: fix sysrq handling for pch_uart
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 24 (extcon-max77693)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (akpm tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH next-20130124] Sound: pci: Fix unused variable warning in patch_sigmatel.c
  • From: Stratos Karafotis <stratosk@xxxxxxxxxxxx>
• Re: linux-next: build failure after merge of the final tree (akpm tree related)
  • From: Shaohua Li <shli@xxxxxxxxxx>
• linux-next: Tree for Jan 24
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure after merge of the final tree (akpm tree related)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] serial: pch_uart: fix sysrq handling for pch_uart
  • From: Liang Li <liang.li@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (pch_uart.c)
  • From: Liang Li <liang.li@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (pch_uart.c)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (pch_uart.c)
  • From: Liang Li <liang.li@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (pch_uart.c)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• mmotm 2013-01-23-17-04 uploaded
  • From: akpm@xxxxxxxxxxxxxxxxxxxx
• linux-next: manual merge of the net-next tree with the mips tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (hvc and virtio_console)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c])
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (pch_uart.c)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c])
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c])
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: linux-next: Tree for Jan 23
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• RE: linux-next: manual merge of the wireless-next tree with Linus' tree
  • From: "Grumbach, Emmanuel" <emmanuel.grumbach@xxxxxxxxx>
• Re: jbd2: don't wake kjournald unnecessarily
  • From: Jan Kara <jack@xxxxxxx>
• Re: jbd2: don't wake kjournald unnecessarily
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: linux-next: manual merge of the tegra tree with the pm tree
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: jbd2: don't wake kjournald unnecessarily
  • From: Jan Kara <jack@xxxxxxx>
• Re: linux-next: manual merge of the pinctrl tree with the driver-core tree
  • From: Linus Walleij <linus.walleij@xxxxxxxxxx>
• AW: [PATCH] leds-ot200: Fix error caused by shifted mask
  • From: "GMEINER.Christian" <C.GMEINER@xxxxxxxxxxxxx>
• [PATCH] leds-ot200: Fix error caused by shifted mask
  • From: Christian Gmeiner <christian.gmeiner@xxxxxxxxx>
• [PATCH 3/3] leds-ot200: Fix error caused by shifted mask
  • From: Christian Gmeiner <christian.gmeiner@xxxxxxxxx>
• Re: linux-next: build warning after merge of the akpm tree
  • From: Tang Chen <tangchen@xxxxxxxxxxxxxx>
• linux-next: Tree for Jan 23
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning after merge of the akpm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• RE: linux-next: build failure after merge of the leds tree
  • From: "Kim, Milo" <Milo.Kim@xxxxxx>
• linux-next: manual merge of the tegra tree with the pm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tegra tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the tegra tree with the arm-soc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>