Linux Next

• Thread Index

• Re: [PATCH] qla2xxx: Fix for build warning
  • From: Anirban Chakraborty <anirban.chakraborty@xxxxxxxxxx>
• Re: [PATCH] qla2xxx: Fix for build warning
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] qla2xxx: Fix for build warning
  • From: Anirban Chakraborty <anirban.chakraborty@xxxxxxxxxx>
• Re: linux-next: warning from build
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: warning from build
  • From: Anirban Chakraborty <anirban.chakraborty@xxxxxxxxxx>
• Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
  • From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
• Re: linux-next: Tree for November 10
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: block tree build failure
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: manual merge of the cputime tree
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• Re: [PATCH v42] proc: add /proc/*/stack (was Re: linux-next: proc tree build failure)
  • From: Ingo Molnar <mingo@xxxxxxx>
• [PATCH v42] proc: add /proc/*/stack (was Re: linux-next: proc tree build failure)
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: Tree for November 7
  • From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
• Re: linux-next: proc tree build failure
  • From: Ingo Molnar <mingo@xxxxxxx>
• linux-next: Tree for November 10
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 7
  • From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
• linux-next: manual merge of the cputime tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: proc tree build failure
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• linux-next: proc tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: block tree build failure
  • From: malahal@xxxxxxxxxx
• linux-next: warning from build
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: block tree build failure
  • From: malahal@xxxxxxxxxx
• Re: linux-next: manual merge of the usb tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the usb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: merging of 2.6.29 material
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: voltage regulator tree branch change
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• voltage regulator tree branch change
  • From: Liam Girdwood <lrg@xxxxxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
  • From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
• Re: linux-next: arm build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: arm build failure
  • From: Russell King <rmk@xxxxxxxxxxxxxxxx>
• Re: next-20081107: ia64 vs kvm
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: linux-next: Tree for November 7
  • From: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
• Re: linux-next: Tree for November 7
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: Tree for November 7
  • From: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
• RE: next-20081107: ia64 vs kvm
  • From: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 7
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: perfmon3 tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20081107: ia64 vs kvm
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: build failure
  • From: Hollis Blanchard <hollisb@xxxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Harvey Harrison <harvey.harrison@xxxxxxxxx>
• Re: linux-next: build failure
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: Hollis Blanchard <hollisb@xxxxxxxxxx>
• Re: linux-next: build failure
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: Hollis Blanchard <hollisb@xxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: perfmon3 tree build failure
  • From: "stephane eranian" <eranian@xxxxxxxxxxxxxx>
• Re: [linux-next] possible circular locking dependency for cryptsetup
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for November 7
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [linux-next] possible circular locking dependency for cryptsetup
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: perfmon3 tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [linux-next] possible circular locking dependency for cryptsetup
  • From: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx>
• linux-next: manual merge of the perfmon3 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [linux-next] possible circular locking dependency for cryptsetup
  • From: Markus Dahms <mad@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: wireless/arm build failure
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: unable to fetch the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: xfs tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: unable to fetch the xfs tree
  • From: Lachlan McIlroy <lachlan@xxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: unable to fetch the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: unable to fetch the xfs tree
  • From: Lachlan McIlroy <lachlan@xxxxxxx>
• Re: linux-next: unable to fetch the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: v4l-dvb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: arm build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: wireless/arm build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: unable to fetch the xfs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: new warnings
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] ftrace: split out hardirq ftrace code into own header
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: [PATCH 0/0] ftrace: fix hardirq.h for m68k
  • From: Ingo Molnar <mingo@xxxxxxx>
• [PATCH 1/1] ftrace: split out hardirq ftrace code into own header
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 0/1] ftrace: fix hardirq.h for m68k
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 0/0] ftrace: fix hardirq.h for m68k
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: next-20081106: perfmon on ia64
  • From: "stephane eranian" <eranian@xxxxxxxxxxxxxx>
• Re: next-20081106: today's ftrace episode
  • From: Steven Rostedt <srostedt@xxxxxxxxxx>
• Re: next-20081106: today's ftrace episode
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: next-20081106: today's ftrace episode
  • From: Steven Rostedt <srostedt@xxxxxxxxxx>
• next-20081106: today's ftrace episode
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• next-20081106: perfmon on ia64
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• next-20081106: undefined reference to `__per_cpu_start'
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: xfs tree build failure
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: new warnings
  • From: "John W. Linville" <linville@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: new build warning
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• Re: linux-next: Tree for November 3
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: linux-next: testing of new cpumask API introduction patch
  • From: Ingo Molnar <mingo@xxxxxxx>
• linux-next: Tree for November 6
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: testing of new cpumask API introduction patch
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: new warnings
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: new build warning
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: new warnings
  • From: David Miller <davem@xxxxxxxxxxxxx>
• linux-next: new warnings
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: testing of new cpumask API introduction patch
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: linux-next: xfs tree build failure
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Mac802.11/iwlagn call trace in linux-next: Tree for November 5
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: 2.6.28-rc3(-next20081103) suspend issues on Lenovo X200
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: linux-next: usb tree build failure
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tests tree
  • From: Ananth N Mavinakayanahalli <ananth@xxxxxxxxxx>
• Re: Git next: Second stage of cpu_alloc patches
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
  • From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the userns tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: next-20081103 - possible circular locking dependency detected while bring up eth1
  • From: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx>
• Re: next-20081103: oxu210hp-hcd.c:3849: error: implicit declaration of function 'set_irq_type'
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: Git next: Second stage of cpu_alloc patches
  • From: "Vegard Nossum" <vegard.nossum@xxxxxxxxx>
• Re: next-20081103 - possible circular locking dependency detected while bring up eth1
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• linux-next: Tree for November 5
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Git next: Second stage of cpu_alloc patches
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20081103 - possible circular locking dependency detected while bring up eth1
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tests tree
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: patch excluded from usb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the userns tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: usb tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: patch excluded from usb tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the semaphore-removal tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the tests tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: xfs tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: patch excluded from usb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: git tree with cputime changes
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20081103: oxu210hp-hcd.c:3849: error: implicit declaration of function 'set_irq_type'
  • From: Rodolfo Giometti <giometti@xxxxxxxxxxxx>
• Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: next-20081103: oxu210hp-hcd.c:3849: error: implicit declaration of function 'set_irq_type'
  • From: Greg KH <gregkh@xxxxxxx>
• Re: next-20081103: oxu210hp-hcd.c:3849: error: implicit declaration of function 'set_irq_type'
  • From: Rodolfo Giometti <giometti@xxxxxxxxxxxx>
• Re: git tree with cputime changes
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• Re: git tree with cputime changes
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 3 (kvm)(resend/lost)
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: [PATCH 1/1] [ALSA] SOC: Fix setting codec register with debugfs filesystem merge error
  • From: Takashi Iwai <tiwai@xxxxxxx>
• [PATCH] Fix fs/coda/sysctl.c build warnings when !CONFIG_SYSCTL
  • From: "Richard A. Holden III" <aciddeath@xxxxxxxxx>
• linux-next: no release today - 20081104
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: 2.6.28-rc3(-next20081103) suspend issues on Lenovo X200
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: 2.6.28-rc3(-next20081103) suspend issues on Lenovo X200
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: Tree for October 31
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: print_ssid undefined (linux-next 20081103)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: [PATCH] net/9p: limit RDMA to INET
  • From: Roland Dreier <rdreier@xxxxxxxxx>
• Re: print_ssid undefined (linux-next 20081103)
  • From: "Luis R. Rodriguez" <lrodriguez@xxxxxxxxxxx>
• Re: print_ssid undefined (linux-next 20081103)
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] [ALSA] SOC: Fix setting codec register with debugfs filesystem merge error
  • From: Mark Brown <broonie@xxxxxxxxxxxxx>
• [PATCH 1/1] [ALSA] SOC: Fix setting codec register with debugfs filesystem merge error
  • From: Troy Kisky <troy.kisky@xxxxxxxxxxxxxxxxxxx>
• print_ssid undefined (linux-next 20081103)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 3 (kvm)(resend/lost)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 3 (kvm)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• [PATCH] net/9p: limit RDMA to INET
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: 2.6.28-rc3(-next20081103) suspend issues on Lenovo X200
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3)
  • From: Alexander Beregalov <a.beregalov@xxxxxxxxx>
• Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3)
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3)
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• next-20081103: oxu210hp-hcd.c:3849: error: implicit declaration of function 'set_irq_type'
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• 2.6.28-rc3(-next20081103) suspend issues on Lenovo X200
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: next-20081103: arch/arm/kernel/elf.c:30: error: 'e_flags' undeclared
  • From: Russell King <rmk+lkml@xxxxxxxxxxxxxxxx>
• git tree with cputime changes
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• Re: linux-next: Tree for October 31
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: next-20081103: arch/arm/kernel/elf.c:30: error: 'e_flags' undeclared
  • From: Mikael Pettersson <mikpe@xxxxxxxx>
• Re: next-20081103: voyager
  • From: Ingo Molnar <mingo@xxxxxxx>
• next-20081103: voyager
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• next-20081103: arch/arm/kernel/elf.c:30: error: 'e_flags' undeclared
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: next-20081103: error: asm/ftrace.h: No such file or directory
  • From: Ingo Molnar <mingo@xxxxxxx>
• next-20081103: error: asm/ftrace.h: No such file or directory
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Deadlock at io_schedule? (Re: linux-next: Tree for November 3)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: manual merge of the slab tree
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the slab tree
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the slab tree
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Re: linux-next: slab tree build failure
  • From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
• Lenovo X200 configuration
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• linux-next: Tree for November 3
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: slab tree build failure
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the slab tree
  • From: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx>
• linux-next: slab tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the slab tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the slab tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the slab tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the trivial tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the semaphore-removal tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: patch excluded from usb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: usb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 31
  • From: "Vegard Nossum" <vegard.nossum@xxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: manual merge of the hdlc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Troy Kisky <troy.kisky@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 31 (repeat build failures)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: manual merge of the hdlc tree
  • From: Krzysztof Halasa <khc@xxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: linux-next: Tree for October 30
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [uml-devel] "warning: passing argument 1 of ‘um_execve’ discards qualifiers from pointer target type"
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• linux-next: Tree for October 31
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: Tree for October 30
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the hdlc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: sound tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: Lachlan McIlroy <lachlan@xxxxxxx>
• Re: linux-next: Tree for October 30
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>
• Re: [uml-devel] "warning: passing argument 1 of ‘um_execve’ discards qualifiers from pointer target type"
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: UDP/bnx2: inconsistent lock state
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: next-20081030: voyager compile busted
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: tree build warning
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the cpu_alloc tree
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• Re: next-20081029: arch/ia64/include/asm/smp.h:60: error: expected ')' before '*' token
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• next-20081030: voyager compile busted
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• next-20081029: arch/ia64/include/asm/smp.h:60: error: expected ')' before '*' token
  • From: "Luck, Tony" <tony.luck@xxxxxxxxx>
• Re: [uml-devel] "warning: passing argument 1 of ‘um_execve’ discards qualifiers from pointer target type"
  • From: "Peter Teoh" <htmldeveloper@xxxxxxxxx>
• Re: UDP/bnx2: inconsistent lock state (Re: linux-next: Tree for October 30)
  • From: Eric Dumazet <dada1@xxxxxxxxxxxxx>
• Re: UDP/bnx2: inconsistent lock state (Re: linux-next: Tree for October 30)
  • From: Eric Dumazet <dada1@xxxxxxxxxxxxx>
• Re: UDP/bnx2: inconsistent lock state (Re: linux-next: Tree for October 30)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• UDP/bnx2: inconsistent lock state (Re: linux-next: Tree for October 30)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: xfs tree build failure
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: next-20081029: arch/ia64/include/asm/smp.h:60: error: expected ')' before '*' token
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: [uml-devel] "warning: passing argument 1 of ‘um_execve’ discards qualifiers from pointer target type"
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• linux-next: Tree for October 30
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: xfs tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• [PATCH trivial] ia64: Fix gru compiler warning
  • From: Russ Anderson <rja@xxxxxxx>
• Re: linux-next: Tree for October 28
  • From: Mark Fasheh <mfasheh@xxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: Tree for October 28
  • From: Greg KH <gregkh@xxxxxxx>
• next-20081029: include/linux/percpu.h:176:1: warning: "SHIFT_PERCPU_PTR" redefined
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• next-20081029: arch/ia64/include/asm/smp.h:60: error: expected ')' before '*' token
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: Tree for October 28
  • From: "John W. Linville" <linville@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: "John W. Linville" <linville@xxxxxxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Andreas Oberritter <obi@xxxxxxxxxxx>
• Re: linux-next: Tree for October 28
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the kvm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the kvm tree
  • From: Avi Kivity <avi@xxxxxxxxxx>
• linux-next: Tree for October 29
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 28
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: Tree for October 28
  • From: Ingo Molnar <mingo@xxxxxxx>
• linux-next: manual merge of the hdlc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 28
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH V2 00/16] Squashfs: compressed read-only filesystem
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• linux-next: v4l-dvb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the s390 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 28
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 28
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: Add a tree to linux-next
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Add a tree to linux-next
  • From: Kumar Gala <galak@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the v4l-dvb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the v4l-dvb tree
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the kmemcheck tree
  • From: Ingo Molnar <mingo@xxxxxxx>
• linux-next: Tree for October 28
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] ftrace: handle archs that do not support irqs_disabled_flags
  • From: Greg Ungerer <gerg@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
• linux-next: tree build warning
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: build failure on sparc64 (Re: linux-next: Tree for October 27)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the cpu_alloc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the cpu_alloc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Ananth N Mavinakayanahalli <ananth@xxxxxxxxxx>
• linux-next: manual merge of the kmemcheck tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: build failure on sparc64 (Re: linux-next: Tree for October 27)
  • From: Ananth N Mavinakayanahalli <ananth@xxxxxxxxxx>
• linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PTCH -next] i2o: fix kernel-doc warnings
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: [PTCH -next] i2o: fix kernel-doc warnings
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 27 (netdev/hp-plus)
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: Tree for October 27 (netdev/hp-plus)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: linux-next: Tree for October 27 (staging/go7007)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: build failure on sparc64 (Re: linux-next: Tree for October 27)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• build failure on sparc64 (Re: linux-next: Tree for October 27)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Lachlan McIlroy <lachlan@xxxxxxx>
• Re: 2.6.29 stuff to linux-next now?
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: 2.6.29 stuff to linux-next now?
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for October 27
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the v4l-dvb tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• 2.6.29 stuff to linux-next now?
  • From: Takashi Iwai <tiwai@xxxxxxx>
• linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [ofa-general] Re: linux-next: Tree for October 23
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 24 (ACPI)
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: [ofa-general] Re: linux-next: Tree for October 23
  • From: Or Gerlitz <ogerlitz@xxxxxxxxxxxx>
• Re: linux-next: Tree for October 24 (usbip)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: Tree for October 24 (ieee80211)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 24 (usbip)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 24 (ACPI)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
  • From: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
• Re: linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
  • From: Sergei Shtylyov <sshtylyov@xxxxxxxxxxxxx>
• Re: IRC channel: Re-Announce
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: linux-next: left over things in linux-next after 2.6.28-c1
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• linux-next: left over things in linux-next after 2.6.28-c1
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
  • From: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
• Re: [PATCH] ftrace: handle archs that do not support irqs_disabled_flags
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: IRC channel: Re-Announce
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
  • From: Sergei Shtylyov <sshtylyov@xxxxxxxxxxxxx>
• Re: linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: Current suspend issues on Lenovo X200
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: build failure at x86/kernel/pci-dma.c with !CONFIG_PCI
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [PATCH] PCI hotplug printk format
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: [PATCH] PCI hotplug printk format
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200
  • From: Andres Freund <andres@xxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH] ftrace: handle archs that do not support irqs_disabled_flags
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• IRC channel: Re-Announce
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• [PATCH] ftrace: handle archs that do not support irqs_disabled_flags
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• xorg not working on 2.6.28-rc1 (was xorg not working on 2.6.27-next-20081017 (intel/lenovo x200)
  • From: Nico Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
  • From: Sergei Shtylyov <sshtylyov@xxxxxxxxxxxxx>
• linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: Fw: [PATCH] coda: credentials error
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Fw: [PATCH] nfsctl: credentials error
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200 (w/ Intel graphics)
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: S3 sleep no longer works on x86_64 in 2.6.27
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• linux-next: Tree for October 24
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: build failure at x86/kernel/pci-dma.c with !CONFIG_PCI
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Fw: [PATCH] nfsctl: credentials error
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Fw: [PATCH] coda: credentials error
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20081023 x86_64 boot hang: int3
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: next-20081023 x86_64 boot hang: int3
  • From: Hiroshi Shimamoto <h-shimamoto@xxxxxxxxxxxxx>
• Re: linux-next: ttydev tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: rr tree build warning
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200
  • From: Nigel Cunningham <ncunningham@xxxxxxxxxxx>
• Re: S3 sleep no longer works on x86_64 in 2.6.27
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• linux-next: rr tree build warning
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: drivers/lguest/page_tables.c:1044: error: invalid initializer
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• [PATCH] coda: credentials error
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• [PATCH] nfsctl: credentials error
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• [PATCH] PCI hotplug printk format
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 23
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 23 (cx88)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: build failure at x86/kernel/pci-dma.c with !CONFIG_PCI
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: build failure at x86/kernel/pci-dma.c with !CONFIG_PCI
  • From: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
• Re: build failure at x86/kernel/pci-dma.c with !CONFIG_PCI
  • From: Fenghua Yu <fenghua.yu@xxxxxxxxx>
• Re: Current suspend issues on Lenovo X200
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: leds tree build failure
  • From: Richard Purdie <rpurdie@xxxxxxxxx>
• Re: xorg not working on 2.6.27-next-20081017 (intel/lenovo x200)
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: Current suspend issues on Lenovo X200
  • From: Nico Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Current suspend issues on Lenovo X200
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: next-20081023 x86_64 boot hang: int3
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• Re: next-20081023 x86_64 boot hang: int3
  • From: Cyrill Gorcunov <gorcunov@xxxxxxxxx>
• next-20081023 x86_64 boot hang: int3
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: [PATCH] tracing: fix a build error on alpha and m68k
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• [PATCH] tracing: fix a build error on alpha and m68k
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• xorg not working on 2.6.27-next-20081017 (intel/lenovo x200)
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: linux-next: kernel/trace/trace.c:658: error:
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: linux-next: kernel/trace/trace.c:658: error:
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: arch/alpha/include/asm/smp.h:48:1: error: "cpu_possible_map" redefined
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: linux-next: kernel/trace/trace.c:658: error:
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: linux-next: include/linux/mmzone.h:288: error: 'CONFIG_NR_CPUS' undeclared here (not in a function)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: kernel/trace/trace.c:658: error:
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• linux-next: x86_64 UML broken
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: kernel/trace/trace.c:658: error:
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: linux-next: rr tree build failure
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: linux-next: undefined reference to 'forbid_dac'
  • From: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
• Re: linux-next: kernel/trace/trace.c:658: error:
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• Re: S3 sleep no longer works on x86_64 in 2.6.27
  • From: Gleb Natapov <gleb@xxxxxxxxxx>
• linux-next: arch/s390/kernel/smp.c:120: error: request for member 'bits' in something not a structure or union
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: rr tree build failure
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• linux-next: undefined reference to `nop_trace'
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: S3 sleep no longer works on x86_64 in 2.6.27
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Mike Travis <travis@xxxxxxx>
• Re: linux-next: kernel/trace/trace.c:658: error:
  • From: "Frédéric Weisbecker" <fweisbec@xxxxxxxxx>
• linux-next: include/linux/mmzone.h:288: error: 'CONFIG_NR_CPUS' undeclared here (not in a function)
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• S3 sleep no longer works on x86_64 in 2.6.27
  • From: Gleb Natapov <gleb@xxxxxxxxxx>
• linux-next: undefined reference to 'forbid_dac'
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: arch/alpha/include/asm/smp.h:48:1: error: "cpu_possible_map" redefined
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• linux-next: arch/alpha/include/asm/smp.h:48:1: error: "cpu_possible_map" redefined
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• linux-next: kernel/trace/trace.c:658: error:
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• linux-next: Tree for October 23
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ttydev tree build failure
  • From: Hendrik Brueckner <brueckner@xxxxxxxxxxxxxxxxxx>
• linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ttydev tree build failure
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: ttydev tree build failure
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• linux-next: ttydev tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH -next] ftrace: rename FTRACE to FUNCTION_TRACER more successfully.
  • From: Paul Mundt <lethal@xxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• linux-next: rr tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: rr tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linuxt-next: nfsd strange commit
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: linux-next: failed import of the rr tree
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: linux-next: v9fs patch comment
  • From: "Eric Van Hensbergen" <ericvh@xxxxxxxxx>
• Re: linux-next: stackprotector tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH -next] fs: fix inode.c kernel-doc warnings
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• [PTCH -next] i2o: fix kernel-doc warnings
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• [PATCH -next] kgdb: fix kernel-doc error
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• linux-next: failed import of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: v9fs patch comment
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linuxt-next: nfsd strange commit
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• adding staging tree for empia?
  • From: "Markus Rechberger" <mrechberger@xxxxxxxxx>
• Re: linux-next: Tree for October 22
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: linux-next: stackprotector tree build failure
  • From: Johannes Schindelin <Johannes.Schindelin@xxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS?
  • From: Johannes Weiner <hannes@xxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] mfd/wm8350: don't export static functions
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for October 22
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] mfd/wm8350: don't export static functions
  • From: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mfd/wm8350: don't export static functions
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: stackprotector tree build failure
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: stackprotector tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: linux-next: stackprotector tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: linux-next: stackprotector tree build failure
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: stackprotector tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 21 (printk format warnings)
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: Tree for October 21 (printk format warnings)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 21 (printk format warnings)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 21 (printk format warnings)
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: Tree for October 21 (staging/prism2-usb)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 21 (staging/prism2-usb)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for October 21 (printk format warnings)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: Tree for October 21 (staging/prism2-usb)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: Tree for October 21 (printk format warnings)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: stackprotector tree build failure
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: Tree for October 21 (jffs2)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: pci tree build failure
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• linux-next: pci tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: stackprotector tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] byteorder: remove direct includes of linux/byteorder/swab[b].h
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 01/31] proc: switch /proc/loadavg to seq_file
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 21
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linuxt-next: nfsd strange commit
  • From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx>
• Re: linux-next: Tree for October 21
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the timers tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the timers tree
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: Tree for October 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 21
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: ttydev tree build failure
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• linux-next: Tree for October 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: proc tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the proc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the proc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the kmemcheck tree
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: leds tree build failure
  • From: Pavel Machek <pavel@xxxxxxx>
• Re: linux-next: manual merge of the kmemcheck tree
  • From: "Vegard Nossum" <vegard.nossum@xxxxxxxxx>
• Re: linux-next: manual merge of the kmemcheck tree
  • From: Ingo Molnar <mingo@xxxxxxx>
• linux-next: manual merge of the kmemcheck tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kmemcheck tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the slab tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: leds tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linuxt-next: nfsd strange commit
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the acpi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the timers tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• RE: linux-next: ttydev tree build failure
  • From: "Lee Howard" <lee.howard@xxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: usb tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the pci tree
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: pci_ioremap_bar() breaks s390 build
  • From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
• Re: pci_ioremap_bar() breaks s390 build
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: pci_ioremap_bar() breaks s390 build
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: pci_ioremap_bar() breaks s390 build
  • From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
• Re: pci_ioremap_bar() breaks s390 build
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
• pci_ioremap_bar() breaks s390 build
  • From: Heiko Carstens <heiko.carstens@xxxxxxxxxx>
• Re: linux-next: Tree for October 20
  • From: Jason Baron <jbaron@xxxxxxxxxx>
• Re: linux-next: build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: build failure
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• linux-next: Tree for October 20
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: mtd tree build failure
  • From: Mike Rapoport <mike@xxxxxxxxxxxxxx>
• Re: linux-next: mtd tree build failure
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: ttydev tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: vfs tree build failure
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: mtd tree build failure
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: linux-next: vfs tree build failure
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• linux-next: vfs tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: mtd tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the acpi tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the pci tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual import of the driver-core,current tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the driver-core.current tree
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: manual merge of the driver-core.current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual import of the driver-core,current tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next current contents
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: pci tree build failure
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: linux-next: pci tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: pci tree build failure
  • From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
• Re: Hung processes (root fs on USB pen-drive)
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: Hung processes (root fs on USB pen-drive)
  • From: "Vegard Nossum" <vegard.nossum@xxxxxxxxx>
• Re: Hung processes (root fs on USB pen-drive)
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Hung processes (root fs on USB pen-drive)
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxx>
• Re: linux-next: Tree for October 17 (build errors/warnings)
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: Tree for October 17 (build errors/warnings)
  • From: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
• Re: linux-next: Tree for October 17 (build errors/warnings)
  • From: "Randy.Dunlap" <rdunlap@xxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: linux-next: Tree for October 17
  • From: "Randy.Dunlap" <rdunlap@xxxxxxxxxxxx>
• Re: linux-next: creds tree build failure
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the hdlc tree
  • From: Krzysztof Halasa <khc@xxxxxxxxx>
• Re: [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: manual merge of the bdev tree
  • From: "Bartlomiej Zolnierkiewicz" <bzolnier@xxxxxxxxx>
• Re: [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: creds tree build failure
  • From: Ian Kent <raven@xxxxxxxxxx>
• Re: linux-next: creds tree build failure
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: creds tree build failure
  • From: Ian Kent <raven@xxxxxxxxxx>
• Re: linux-next: manual merge of the bdev tree
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: creds tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: creds tree build failure
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 17
  • From: "Vegard Nossum" <vegard.nossum@xxxxxxxxx>
• Re: linux-next: manual merge of the bdev tree
  • From: "Bartlomiej Zolnierkiewicz" <bzolnier@xxxxxxxxx>
• linux-next: Tree for October 17
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: creds tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the bdev tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the bdev tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the bdev tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: creds tree build failure
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• linux-next: creds tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the drm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the hdlc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the v9fs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: usb tree build failure
  • From: Dmitry <dbaryshkov@xxxxxxxxx>
• Re: linux-next: usb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the sh tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the scsi-post-merge tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the hid tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: bad import of rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 16
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: usb tree build failure
  • From: Dmitry Baryshkov <dbaryshkov@xxxxxxxxx>
• [BUG] linux-next: Tree for October 16 - softlockup detected at blk_invoke_request_fn
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] linux-next: Tree for October 16 - build failure at MAL support on powerpc
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] linux-next: Tree for October 16 - build failure at MAL support on powerpc
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx>
• [PATCH] linux-next: Tree for October 16 - build failure at MAL support on powerpc
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 16
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: linux-next: usb tree build failure
  • From: Dmitry Baryshkov <dbaryshkov@xxxxxxxxx>
• Re: linux-next: build failure
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: build failure
  • From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
• Re: linux-next: usb tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: build warning
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: build failure
  • From: "Eric Van Hensbergen" <ericvh@xxxxxxxxx>
• Re: linux-next: manual merge of the scsi-post-merge tree
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for October 16
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>