Linux Next

• Thread Index

• [PATCH] tracing, tty: fix warnings caused by branch tracing and tty_kref_get()
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: rr tree build failure
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the perfmon3 tree
  • From: Alexander van Heukelum <heukelum@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the security-testing tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the cputime tree
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• linux-next: Tree for November 25
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the cputime tree
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• linux-next: ocsf2 tree build warnings
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the cputime tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: linux-next: ftrace tree build warnings
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the perfmon3 tree
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: manual merge of the cputime tree
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• Re: linux-next: manual merge of the cputime tree
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• linux-next: manual merge of the perfmon3 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the perfmon3 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the cputime tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: linux-next: kbuild tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: kbuild tree build failure
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: linux-next: ftrace tree build warnings
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the security-testing tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: ftrace tree build warnings
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] use limited register constraint for setnz
  • From: Ingo Molnar <mingo@xxxxxxx>
• linux-next: manual merge of the firmware tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the kvm tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: rr tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Steven Rostedt <srostedt@xxxxxxxxxx>
• [PATCH] use limited register constraint for setnz
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• linux-next: ocfs2 tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Steven Rostedt <srostedt@xxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: kbuild tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: v4l-dvb tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Steven Rostedt <srostedt@xxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Steven Rostedt <srostedt@xxxxxxxxxx>
• Re: linux-next: ftrace tree build failure
  • From: Steven Rostedt <srostedt@xxxxxxxxxx>
• linux-next: ftrace tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: ftrace tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: ftrace tree build warnings
  • From: Steven Rostedt <srostedt@xxxxxxxxxx>
• linux-next: ftrace tree build warnings
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: malahal@xxxxxxxxxx
• Re: userns tree ready
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: linux-next: manual merge of the 4xx tree
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx>
• Re: userns tree ready
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the 4xx tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• userns tree ready
  • From: "Serge E. Hallyn" <serue@xxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: malahal@xxxxxxxxxx
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: malahal@xxxxxxxxxx
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Hemminger <shemminger@xxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: Mike Anderson <andmike@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: linux-next: rr tree build failure
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [alsa-devel] [PATCH] Remove unused variable from tlv320aic23 codec
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: ttydev tree build failure
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: linux-next: build warning
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: build warning
  • From: "NeilBrown" <neilb@xxxxxxx>
• linux-next: proc tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for November 24
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: build warning
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
  • From: Brad Boyer <flar@xxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: cpu_alloc tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: ttydev tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• 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: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the ftrace tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the ftrace tree
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
  • From: Michael Schmitz <schmitz@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• linux-next: manual merge of the ftrace tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
  • From: Brad Boyer <flar@xxxxxxxxxxxxx>
• Re: vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
  • From: Michael Schmitz <schmitz@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
  • From: Brad Boyer <flar@xxxxxxxxxxxxx>
• Re: vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
  • From: Michael Schmitz <schmitz@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• vme_scc.c breakage (was: Re: linux-next: Tree for November 21)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH linux-next] snd-hda: fix build errors
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: [PATCH linux-next] snd-hda: fix build errors
  • From: Wu Fengguang <wfg@xxxxxxxxxxxxxxx>
• Re: next-20081121:WARNING: at drivers/dma/dmaengine.c:665 dma_async_device_unregister()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH linux-next] snd-hda: fix build errors
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: [PATCH linux-next] snd-hda: fix build errors
  • From: Takashi Iwai <tiwai@xxxxxxx>
• [PATCH linux-next] snd-hda: fix build errors
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next-20081120 - staging - asus_oled device build fails with !CONFIG_USB_SUPPORT
  • From: Greg KH <gregkh@xxxxxxx>
• Re: linux-next-20081120 - staging - meilhaus driver build fails
  • From: Greg KH <gregkh@xxxxxxx>
• Re: linux-next: rr tree build failure
  • From: Greg KH <gregkh@xxxxxxx>
• Re: next-20081121:WARNING: at drivers/dma/dmaengine.c:665 dma_async_device_unregister()
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: next-20081117: kernel freezes with netconsole enabled
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: rr tree build failure
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• next-20081121:WARNING: at drivers/dma/dmaengine.c:665 dma_async_device_unregister()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• next-20081121: WARNING: at lib/debugobjects.c: hpet
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• linux-next: Tree for November 21
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Remove unused variables from the cirrusfb driver
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Remove unused variables from the cirrusfb driver
  • From: Richard Holden <aciddeath@xxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: net tree build failure
  • From: Stephen Hemminger <shemminger@xxxxxxxxxx>
• linux-next: rr tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: net tree build failure
  • 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: [PATCH] Remove unused variables from the cirrusfb driver
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 20 (staging* [lots])
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: [PATCH] Remove unused variable from tlv320aic23 codec
  • From: Mark Brown <broonie@xxxxxxxxxxxxx>
• Re: linux-next-20081120 - staging - asus_oled device build fails with !CONFIG_USB_SUPPORT
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• [PATCH] Remove unused variable from tlv320aic23 codec
  • From: "Richard A. Holden III" <aciddeath@xxxxxxxxx>
• [PATCH] Remove unused variables from the cirrusfb driver
  • From: "Richard A. Holden III" <aciddeath@xxxxxxxxx>
• [PATCH] Fix arch/x86/kernel/cpu/mtrr/main.c build warning
  • From: "Richard A. Holden III" <aciddeath@xxxxxxxxx>
• Re: linux-next-20081120 - staging - meilhaus driver build fails
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the wireless tree
  • From: "John W. Linville" <linville@xxxxxxxxxxxxx>
• Re: [PATCH] sfc: Fix dependency for SFC_MTD
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the s390 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] md_print_devices: use le{32,64}_to_cpu to access data correctly
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH] md_print_devices: use le{32,64}_to_cpu to access data correctly
  • From: crquan@xxxxxxxxx
• Re: linux-next: manual merge of the s390 tree
  • From: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (v4l2 warnings)
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• linux-next: Tree for November 20
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: proc tree build failure
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: linux-next: manual merge of the wireless tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH] Fix arch/x86/kernel/setup.c build warning when !CONFIG_X86_RESERVE_LOW_64K
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH] Fix arch/x86/kernel/genx2apic_uv_x.c build warning when !CONFIG_HOTPLUG_CPU
  • From: Ingo Molnar <mingo@xxxxxxx>
• 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 security-testing tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: md tree build warnings
  • From: "rae l" <crquan@xxxxxxxxx>
• Re: linux-next: md tree build warnings
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: linux-next: md tree build warnings
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: md tree build warnings
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• 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: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the wireless tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: net tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 19 (v4l2 warnings)
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the s390 tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] Fix arch/x86/kernel/setup.c build warning when !CONFIG_X86_RESERVE_LOW_64K
  • From: "Richard A. Holden III" <aciddeath@xxxxxxxxx>
• [PATCH] Fix arch/x86/kernel/genx2apic_uv_x.c build warning when !CONFIG_HOTPLUG_CPU
  • From: "Richard A. Holden III" <aciddeath@xxxxxxxxx>
• Re: [PATCH] sfc: Fix dependency for SFC_MTD
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (section mismatche fpu_init)
  • From: Richard Holden <aciddeath@xxxxxxxxx>
• Re: next-20081119: general protection fault: get_next_timer_interrupt()
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH] sfc: Fix dependency for SFC_MTD
  • From: Ben Hutchings <bhutchings@xxxxxxxxxxxxxx>
• [PATCH] sfc: Fix dependency for SFC_MTD
  • From: Ben Hutchings <bhutchings@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 19 (mtd build error)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (mtd build error)
  • From: Ben Hutchings <bhutchings@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 19 (mtd build error)
  • From: Ben Hutchings <bhutchings@xxxxxxxxxxxxxx>
• [PATCH -next resend] nfsctl: add headers for credentials
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (mtd build error)
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start')
  • From: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] coda: fix creds reference
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (staging/go7007/)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: Tree for November 19 (mtd build error)
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: linux-next: Tree for November 19 (mtd build error)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (ipw2100/2200 build errors)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (mtd build error)
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: linux-next: Tree for November 19 (dvb build errors)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (mtd build error)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (v4l2 warnings)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 19 (staging/go7007/)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: next-20081117: kernel freezes with netconsole enabled
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: next-20081117: kernel freezes with netconsole enabled
  • From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
• Re: next-20081117: kernel freezes with netconsole enabled
  • From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
• pci_read_config_* functions and uninitialized warnings?
  • From: Richard Holden <aciddeath@xxxxxxxxx>
• next-20081117: kernel freezes with netconsole enabled
  • From: Alexander Beregalov <a.beregalov@xxxxxxxxx>
• Re: 2.6.28-rc4 suspend issues on Lenovo X200
  • From: Pavel Machek <pavel@xxxxxxx>
• next-20081119: general protection fault: get_next_timer_interrupt()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the sched tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-m68k.git
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: manual merge of the block tree
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: manual merge of the sched tree
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: linux-m68k.git
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-m68k.git
  • From: Ralf Baechle <ralf@xxxxxxxxxxxxxx>
• Re: linux-m68k.git
  • From: Michael Schmitz <schmitz@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: linux-next: driver-core tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• linux-next: Tree for November 19
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: driver-core tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: driver-core tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: driver-core tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: driver-core tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the block tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the cifs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: driver-core tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: driver-core tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the sched tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: driver-core tree build failure
  • From: "Kay Sievers" <kay.sievers@xxxxxxxx>
• linux-next: driver-core tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: spinlock lockup with next-20081118 on powerpc
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-m68k.git
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-m68k.git
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• linux-m68k.git
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: procedures
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: lblnet tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• struct uart_port has no member named 'sysrq' (was: linux-next: parisc build failure)
  • From: Helge Deller <deller@xxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
• Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: procedures
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: linux-next: lblnet tree build failure
  • From: Paul Moore <paul.moore@xxxxxx>
• Re: linux-next: manual merge of the security-testing tree
  • From: James Morris <jmorris@xxxxxxxxx>
• linux-next: Tree for November 18
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start')
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: lblnet tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sh tree build warning
  • From: Paul Mundt <lethal@xxxxxxxxxxxx>
• linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: [PATCH 1/1] ring-buffer: buffer record on/off switch
  • From: Andy Whitcroft <apw@xxxxxxxxxxxx>
• linux-next: Tree for November 17
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Automated Build Infrastructure
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: Automated Build Infrastructure
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• linux-next: manual merge of the security-testing tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Automated Build Infrastructure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Automated Build Infrastructure
  • From: Richard Holden <aciddeath@xxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• linux-next: manual merge of the cifs tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: sh tree build warning
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: next-20081114 build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: osd tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: parisc build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: next-20081114 build failure
  • From: David Howells <dhowells@xxxxxxxxxx>
• linux-next: next-20081114 build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: next-20081114 build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: osd tree build failure
  • From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
• [PATCH] MTD: NAND: make gpio_nand use io{read,write}{8,16}_rep (was: Re: linux-next: mtd tree build failure)
  • From: Mike Rapoport <mike@xxxxxxxxxxxxxx>
• Re: 2.6.28-rc4 suspend issues on Lenovo X200
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: linux-next: security-testing tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging)
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging#2)
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging#2)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: security-testing tree build failure
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging#2)
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging/agnx/)
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging/agnx/)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging/meilhaus/ more)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging/meilhaus/)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging#2)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 14 (staging)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• 2.6.28-rc4 suspend issues on Lenovo X200
  • From: Nico -telmich- Schottelius <nico-linux-next@xxxxxxxxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: security-testing tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Takashi Iwai <tiwai@xxxxxxx>
• linux-next: Tree for November 14
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: osd tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: sound tree build failure
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the rr 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: sound tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• next-20081113: ndefined ureference to `freeze_processes'
  • From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: "J.R. Mauro" <jrm8005@xxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Can you add the staging tree to -next?
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: Missing CONFIG_IDE_LEGACY definition (Re: linux-next: Tree for November 13)
  • From: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>
• Re: linux-next: Tree for November 13 (auditsc)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 13 (v4l2 build error)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: "Serge E. Hallyn" <serue@xxxxxxxxxx>
• Re: [PATCH linux-next] : Tree for November 12 (libcrc32c)
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: Deadlock at io_schedule? (Re: linux-next: Tree for November 3)
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next infrastructure open?
  • From: Frank Seidel <fseidel@xxxxxxx>
• Missing CONFIG_IDE_LEGACY definition (Re: linux-next: Tree for November 13)
  • From: Takashi Iwai <tiwai@xxxxxxx>
• linux-next: security-testing tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: Tree for November 13
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• 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: security-testing tree build warning
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: manual merge of the hdlc tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sparc/firmware build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sh tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: sh tree build failure
  • From: Paul Mundt <lethal@xxxxxxxxxxxx>
• linux-next: sh tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] ftrace: disable tracing on resize
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Can you add the staging tree to -next?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] sparc64: add function save_stack_trace_tsk()
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH linux-next 3rd time] 9p: restrict RDMA usage
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• [PATCH linux-next] : Tree for November 12 (libcrc32c)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: 2.6.28-rc3(-next20081103) suspend issues on Lenovo X200
  • From: "Rob Latham" <rlatham@xxxxxxxxx>
• Re: [PATCH 1/2] ftrace: disable tracing on resize
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2] ftrace: disable tracing on resize
  • From: Pekka Paalanen <pq@xxxxxx>
• Re: linux-next: manual merge of the creds tree
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: linux-next: manual merge of the trivial tree
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: [PATCH] mac80211: add explicit padding in struct ieee80211_tx_info
  • From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
• Re: [PATCH] sparc64: add function save_stack_trace_tsk()
  • From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx>
• [PATCH] mac80211: add explicit padding in struct ieee80211_tx_info
  • From: "John W. Linville" <linville@xxxxxxxxxxxxx>
• linux-next infrastructure open?
  • From: Frank Seidel <fseidel@xxxxxxx>
• Re: linux-next: security-testing tree build failure
  • From: Eric Paris <eparis@xxxxxxxxxx>
• [PATCH] sparc64: add function save_stack_trace_tsk()
  • From: Alexander Beregalov <a.beregalov@xxxxxxxxx>
• Re: [PATCH 1/1] ring-buffer: buffer record on/off switch
  • From: Pavel Machek <pavel@xxxxxxx>
• Re: [Lguest] linux-next: Tree for November 12 - lguest build failure
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• Re: linux-next: security-testing tree build failure
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: linux-next: Tree for November 12 - lguest build failure
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• linux-next: Tree for November 12 - lguest build failure
  • From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
• Re: next-20081106: undefined reference to `__per_cpu_start'
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• mac80211.h (was: Re: linux-next: Tree for November 12)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• linux-next: Tree for November 12
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: procedures
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• linux-next: ttydev tree build warning
  • 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: security-testing tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: "John W. Linville" <linville@xxxxxxxxxxxxx>
• linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: v4l-dvb tree build failure
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] ring-buffer: buffer record on/off switch
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: [PATCH 1/1] ring-buffer: buffer record on/off switch
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/1] ring-buffer: buffer record on/off switch
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/1] ring-buffer: buffer record on/off switch
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/1] ring-buffer: disable tracing switch
  • From: Ingo Molnar <mingo@xxxxxxx>
• [PATCH 1/1] ring-buffer: buffer record on/off switch
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 0/1] ring-buffer: disable tracing switch
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: linux-next: build failure
  • From: David Miller <davem@xxxxxxxxxxxxx>
• linux-next: Tree for November 11
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] ftrace updates for 2.6.28
  • From: Ingo Molnar <mingo@xxxxxxx>
• linux-next: build failure
  • From: Sujith <Sujith.Manoharan@xxxxxxxxxxx>
• linux-next: build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: manual merge of the net tree
  • From: David Miller <davem@xxxxxxxxxxxxx>
• linux-next: manual merge of the cputime tree
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: crypto tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: crypto tree build failure
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• linux-next: crypto tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] ftrace updates for 2.6.28
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 1/2] ftrace: disable tracing on resize
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 2/2] ring-buffer: prevent infinite looping on time stamping
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 1/2] ftrace: disable tracing on resize
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 0/2] ftrace updates for 2.6.28
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: linux-next: xfs tree build failure
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: linux-next: xfs tree build failure
  • From: Lachlan McIlroy <lachlan@xxxxxxx>
• 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>