lists-archives.org

Mailing Lists Archives

	Web lists-archives.org

Mail Thread Index

• Date Index

[Prev Page][Next Page]

---

• Re: [PATCH] Identify which executable object the userspace address belongs to. Store thread group leader id, and use it to lookup the address in the process's map. We could have looked up the address on thread's map, but the thread might not exist by the time we are called. The process might not exist either, but if you are reading trace_pipe, that is unlikely., (continued)
  • Re: [PATCH] Identify which executable object the userspace address belongs to. Store thread group leader id, and use it to lookup the address in the process's map. We could have looked up the address on thread's map, but the thread might not exist by the time we are called. The process might not exist either, but if you are reading trace_pipe, that is unlikely.,Török Edwin
  • Re: [PATCH] Identify which executable object the userspace address belongs to. Store thread group leader id, and use it to lookup the address in the process's map. We could have looked up the address on thread's map, but the thread might not exist by the time we are called. The process might not exist either, but if you are reading trace_pipe, that is unlikely.,Ingo Molnar
  • Re: [PATCH] Identify which executable object the userspace address belongs to. Store thread group leader id, and use it to lookup the address in the process's map. We could have looked up the address on thread's map, but the thread might not exist by the time we are called. The process might not exist either, but if you are reading trace_pipe, that is unlikely.,Mathieu Desnoyers
  • Re: [PATCH] Identify which executable object the userspace address belongs to. Store thread group leader id, and use it to lookup the address in the process's map. We could have looked up the address on thread's map, but the thread might not exist by the time we are called. The process might not exist either, but if you are reading trace_pipe, that is unlikely.,Peter Zijlstra
  • Re: [PATCH] Identify which executable object the userspace address belongs to. Store thread group leader id, and use it to lookup the address in the process's map. We could have looked up the address on thread's map, but the thread might not exist by the time we are called. The process might not exist either, but if you are reading trace_pipe, that is unlikely.,Arnaldo Carvalho de Melo
  • Re: [PATCH] Identify which executable object the userspace address belongs to. Store thread group leader id, and use it to lookup the address in the process's map. We could have looked up the address on thread's map, but the thread might not exist by the time we are called. The process might not exist either, but if you are reading trace_pipe, that is unlikely.,Török Edwin
• [git pull] IDE fixes #1,Bartlomiej Zolnierkiewicz
• AMD64 reboot regression,Michael B. Trausch
  • Re: [Bug 11910] AMD64 reboot regression,Simon Arlott
• [PATCH] ath5k: fix detection of jumbo frames,Bob Copeland
  • Re: [ath5k-devel] [PATCH] ath5k: fix detection of jumbo frames,Luis R. Rodriguez
    • Re: [ath5k-devel] [PATCH] ath5k: fix detection of jumbo frames,Bob Copeland
      • Re: [ath5k-devel] [PATCH] ath5k: fix detection of jumbo frames,Luis R. Rodriguez
      • Re: [ath5k-devel] [PATCH] ath5k: fix detection of jumbo frames,Bob Copeland
  • Re: [PATCH] ath5k: fix detection of jumbo frames,Pavel Roskin
    • Re: [ath5k-devel] [PATCH] ath5k: fix detection of jumbo frames,Bob Copeland
      • Re: [ath5k-devel] [PATCH] ath5k: fix detection of jumbo frames,Pavel Roskin
  • [PATCH] ath5k: correct handling of rx status fields,Bob Copeland
• 2.6.28-rc2-git7: Reported regressions 2.6.26 -> 2.6.27,Rafael J. Wysocki
  • [Bug #11207] VolanoMark regression with 2.6.27-rc1,Rafael J. Wysocki
  • [Bug #11220] Screen stays black after resume,Rafael J. Wysocki
  • [Bug #11215] INFO: possible recursive locking detected ps2_command,Rafael J. Wysocki
  • [Bug #11210] IRQ routing badness,Rafael J. Wysocki
  • [Bug #11209] 2.6.27-rc1 process time accounting,Rafael J. Wysocki
  • [Bug #11272] BUG: parport_serial in 2.6.27-rc1 for NetMos Technology PCI 9835,Rafael J. Wysocki
  • [Bug #11264] Invalid op opcode in kernel/workqueue,Rafael J. Wysocki
  • [Bug #11340] LTP overnight run resulted in unusable box,Rafael J. Wysocki
  • [Bug #11308] tbench regression on each kernel release from 2.6.22 -> 2.6.28,Rafael J. Wysocki
  • [Bug #11380] lockdep warning: cpu_add_remove_lock at:cpu_maps_update_begin+0x14/0x16,Rafael J. Wysocki
  • [Bug #11271] BUG: fealnx in 2.6.27-rc1,Rafael J. Wysocki
  • [Bug #11404] BUG: in 2.6.23-rc3-git7 in do_cciss_intr,Rafael J. Wysocki
    • Re: [Bug #11404] BUG: in 2.6.23-rc3-git7 in do_cciss_intr,Randy Dunlap
  • [Bug #11476] failure to associate after resume from suspend to ram,Rafael J. Wysocki
  • [Bug #11407] suspend: unable to handle kernel paging request,Rafael J. Wysocki
  • [Bug #11505] oltp ~10% regression with 2.6.27-rc5 on stoakley machine,Rafael J. Wysocki
  • [Bug #11543] kernel panic: softlockup in tick_periodic() ???,Rafael J. Wysocki
    • Re: [Bug #11543] kernel panic: softlockup in tick_periodic() ???,Cyrill Gorcunov
  • [Bug #11664] acpi errors and random freeze on sony vaio sr,Rafael J. Wysocki
    • Re: [Bug #11664] acpi errors and random freeze on sony vaio sr,Giovanni Pellerano
      • Re: [Bug #11664] acpi errors and random freeze on sony vaio sr,Giovanni Pellerano
  • [Bug #11550] pnp: Huge number of "io resource overlap" messages,Rafael J. Wysocki
  • [Bug #11608] 2.6.27-rc6 BUG: unable to handle kernel paging request,Rafael J. Wysocki
  • [Bug #11569] Panic stop CPUs regression,Rafael J. Wysocki
  • [Bug #11698] 2.6.27-rc7, freezes with > 1 s2ram cycle,Rafael J. Wysocki
  • [Bug #11699] 2.6.27-rc-7: BUG: scheduling while atomic, c1e_idle+0x98/0xe0,Rafael J. Wysocki
  • [Bug #11795] ks959-sir dongle no longer works under 2.6.27 (REGRESSION),Rafael J. Wysocki
  • [Bug #11805] mounting XFS produces a segfault,Rafael J. Wysocki
    • Re: [Bug #11805] mounting XFS produces a segfault,Christoph Hellwig
  • [Bug #11843] usb hdd problems with 2.6.27.2,Rafael J. Wysocki
  • [Bug #11830] disk statistics issue in 2.6.27,Rafael J. Wysocki
  • [Bug #11820] 2.6.27: 0 MHz CPU and wrong system time on AMD Geode system,Rafael J. Wysocki
  • [Bug #11829] Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE),Rafael J. Wysocki
  • [Bug #11832] 2.6.27: "irq 18: nobody cared" on Toshiba Satellite A100,Rafael J. Wysocki
  • [Bug #11836] Scheduler on C2D CPU and latest 2.6.27 kernel,Rafael J. Wysocki
  • [Bug #11904] upstream regression (IO-APIC?),Rafael J. Wysocki
  • [Bug #11907] NVRAM being corrupted on ppc64 preventing boot,Rafael J. Wysocki
    • Re: [Bug #11907] NVRAM being corrupted on ppc64 preventing boot,Paul Mackerras
      • Re: [Bug #11907] NVRAM being corrupted on ppc64 preventing boot,Rafael J. Wysocki
  • [Bug #11876] RCU hang on cpu re-hotplug with 2.6.27rc8,Rafael J. Wysocki
    • Re: [Bug #11876] RCU hang on cpu re-hotplug with 2.6.27rc8,Paul E. McKenney
• [PATCH] jffs2: force the jffs2 GC daemon to behave a bit better,Andres Salomon
  • Re: [PATCH] jffs2: force the jffs2 GC daemon to behave a bit better,Andrew Morton
• Strange fileystem problem,J.A. Magallón
• 2.6.28-rc2-git7: Reported regressions from 2.6.27,Rafael J. Wysocki
  • [Bug #11798] [Radeon Xpress 1100 IGP] DRI fail on recent kernel updates,Rafael J. Wysocki
  • [Bug #11799] xorg can not start up with stolen memory,Rafael J. Wysocki
  • [Bug #11824] raw1394: possible deadlock if accessed by multithreaded app,Rafael J. Wysocki
    • Re: [Bug #11824] raw1394: possible deadlock if accessed by multithreaded app,Stefan Richter
  • [Bug #11822] ACPI Warning (nspredef-0858): _SB_.PCI0.LPC_.EC__.BAT0._BIF: Return Package type mismatch at index 9 - found Buffer, expected String [20080926],Rafael J. Wysocki
  • [Bug #11806] iwl3945 fails with microcode error,Rafael J. Wysocki
    • Re: [Bug #11806] iwl3945 fails with microcode error,reinette chatre
  • [Bug #11826] extreme slowness of IO stuff using 2.6.28-rc1,Rafael J. Wysocki
  • [Bug #11834] iwl3945: if I leave my machine running overnight, wifi will not work in the morning,Rafael J. Wysocki
  • [Bug #11841] plenty of line "ACPI: EC: non-query interrupt received, switching to interrupt mode" in dmesg,Rafael J. Wysocki
  • [Bug #11845] Suspend regression on Lenovo x60,Rafael J. Wysocki
    • Re: [Bug #11845] Suspend regression on Lenovo x60,Carlos R. Mafra
      • Re: [Bug #11845] Suspend regression on Lenovo x60,Rafael J. Wysocki
      • Re: [Bug #11845] Suspend regression on Lenovo x60,Tomas Winkler
      • Re: [Bug #11845] Suspend regression on Lenovo x60,Ingo Molnar
  • [Bug #11847] 2.6.28-rc1 fails building on allnoconfig,Rafael J. Wysocki
  • [Bug #11849] default IRQ affinity change in v2.6.27 (breaking several SMP PPC based systems),Rafael J. Wysocki
  • [Bug #11854] v2.6.28-rc1: readlink /proc/*/exe returns uninitialized data to userspace,Rafael J. Wysocki
    • Re: [Bug #11854] v2.6.28-rc1: readlink /proc/*/exe returns uninitialized data to userspace,Vegard Nossum
      • Re: [Bug #11854] v2.6.28-rc1: readlink /proc/*/exe returns uninitialized data to userspace,Rafael J. Wysocki
  • [Bug #11852] v2.6.28-rc1: Regression in ext3/jbd,Rafael J. Wysocki
    • Re: [Bug #11852] v2.6.28-rc1: Regression in ext3/jbd,Vegard Nossum
      • Re: [Bug #11852] v2.6.28-rc1: Regression in ext3/jbd,Rafael J. Wysocki
  • [Bug #11856] seq_file does not handle pread(),Rafael J. Wysocki
  • [Bug #11858] Timeout regression introduced by 242f9dcb8ba6f68fcd217a119a7648a4f69290e9,Rafael J. Wysocki
  • [Bug #11873] unable to mount ext3 root filesystem due to htree_dirblock_to_tree,Rafael J. Wysocki
  • [Bug #11881] Linux 2.6.28-rc2 i/o error on /dev/ttyUSB0,Rafael J. Wysocki
  • [Bug #11875] radeonfb lockup in .28-rc (bisected),Rafael J. Wysocki
  • [Bug #11882] dbench 15% regression with 2.6.28-rc1,Rafael J. Wysocki
  • [Bug #11891] resume from disk broken on hp/compaq nx7000 (DRM problem),Rafael J. Wysocki
  • [Bug #11898] mke2fs hang on AIC79 device.,Rafael J. Wysocki
  • [Bug #11894] 2.6.28-rc2 / hso driver oops,Rafael J. Wysocki
    • Re: [Bug #11894] 2.6.28-rc2 / hso driver oops,Ben Hutchings
      • Re: [Bug #11894] 2.6.28-rc2 / hso driver oops,Rafael J. Wysocki
  • [Bug #11895] 2.6.28-rc2 regression: keyboard dead after reboot on Toshiba Portege 4000,Rafael J. Wysocki
  • [Bug #11899] sometime boot failed on T61 laptop,Rafael J. Wysocki
  • [Bug #11901] ath5k triggers WARN_ON in __ieee80211_rx,Rafael J. Wysocki
    • Re: [Bug #11901] ath5k triggers WARN_ON in __ieee80211_rx,Bob Copeland
  • [Bug #11905] lots of extra timer interrupts costing 2W,Rafael J. Wysocki
    • Re: [Bug #11905] lots of extra timer interrupts costing 2W,Theodore Tso
  • [Bug #11909] initrd fails to create bloc devices,Rafael J. Wysocki
  • [Bug #11903] regression: vmalloc easily fail,Rafael J. Wysocki
  • [Bug #11906] 2.6.28-rc2 seems to fail at powering down the monitor when it should,Rafael J. Wysocki
  • [Bug #11911] new PCMCIA device instance after resume - orinoco can't download firmware,Rafael J. Wysocki
  • [Bug #11910] System doesn't restart,Rafael J. Wysocki
  • [Bug #11908] linux-2.6.28-rc2 regression : oprofile doesnt work anymore,Rafael J. Wysocki
  • [Bug #11913] USB/INPUT: slab error in cache_alloc_debugcheck_after(): double free?,Rafael J. Wysocki
  • [Bug #11917] Asus Eee PC hotkeys stop working after prolonged usage,Rafael J. Wysocki
  • [Bug #11925] cdrom: missing compat ioctls,Rafael J. Wysocki
  • [Bug #11927] undefined reference to `save_stack_trace',Rafael J. Wysocki
  • [Bug #11928] ath5k gets lost with eeepc-laptop removal,Rafael J. Wysocki
  • [Bug #11937] ext3 __log_wait_for_space: no transactions,Rafael J. Wysocki
    • Re: [Bug #11937] ext3 __log_wait_for_space: no transactions,Theodore Tso
  • [Bug #11940] Unable to handle kernel paging request at iov_iter_copy_from_user_atomic,Rafael J. Wysocki
    • Re: [Bug #11940] Unable to handle kernel paging request at iov_iter_copy_from_user_atomic,David Miller
      • Re: [Bug #11940] Unable to handle kernel paging request at iov_iter_copy_from_user_atomic,Rafael J. Wysocki
• [PATCH] hp-wmi: Fix warnings,Larry Finger
  • Re: [PATCH] hp-wmi: Fix warnings,Andrew Morton
• Tracing framework regressions in 2.6.28-rc2,Pekka Paalanen
  • Re: Tracing framework regressions in 2.6.28-rc2,Frédéric Weisbecker
    • Re: Tracing framework regressions in 2.6.28-rc2,Pekka Paalanen
  • Tracing framework regression in 2.6.28-rc3,Pekka Paalanen
    • Re: Tracing framework regression in 2.6.28-rc3,Steven Rostedt
• [PATCH] crypto: Add Skein hash algorithm variants,Jeff Garzik
  • [PATCH] crypto: add test vectors for skein256/512/1024,Sebastian Andrzej Siewior
    • Re: [PATCH] crypto: add test vectors for skein256/512/1024,Jeff Garzik
    • Re: [PATCH] crypto: add test vectors for skein256/512/1024,Jeff Garzik
      • Re: [PATCH] crypto: add test vectors for skein256/512/1024,Sebastian Andrzej Siewior
      • Re: [PATCH] crypto: add test vectors for skein256/512/1024,Sebastian Andrzej Siewior
  • Re: [PATCH] crypto: Add Skein hash algorithm variants,David Wagner
    • Re: [PATCH] crypto: Add Skein hash algorithm variants,ray
• [PATCH 1/3] HPET: Convert WARN_ON to WARN_ON_ONCE,Matt Fleming
  • [PATCH 2/3] HPET: Enter hpet_interrupt_handler with interrupts disabled,Matt Fleming
    • [PATCH 3/3] HPET: Read from HPET_Tn_CMP() not HPET_T0_CMP,Matt Fleming
      • Re: [PATCH 3/3] HPET: Read from HPET_Tn_CMP() not HPET_T0_CMP,Matt Fleming
      • Re: [PATCH 3/3] HPET: Read from HPET_Tn_CMP() not HPET_T0_CMP,Thomas Gleixner
    • Re: [PATCH 2/3] HPET: Enter hpet_interrupt_handler with interrupts disabled,Will Newton
      • Re: [PATCH 2/3] HPET: Enter hpet_interrupt_handler with interrupts disabled,Matt Fleming
      • Re: [PATCH 2/3] HPET: Enter hpet_interrupt_handler with interrupts disabled,Takashi Iwai
• [microPATCH] linux/string.h: fix comment typo,Jeff Garzik
• [PATCH] 2.6.27: add a kernel hacking option to protect kernel memory between different modules,Pengfei Hu
  • Re: [PATCH] 2.6.27: add a kernel hacking option to protect kernel memory between different modules,Valdis . Kletnieks
    • Re: [PATCH] 2.6.27: add a kernel hacking option to protect kernel memory between different modules,Pengfei Hu
• [git patches] net driver fix for 2.6.28-rc,Jeff Garzik
  • Re: [git patches] net driver fix for 2.6.28-rc,David Miller
• Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Jeff Garzik
  • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Greg KH
  • <Possible follow-ups>
  • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Subbu Seetharaman
    • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Greg KH
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Jeff Garzik
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Greg KH
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Greg KH
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Jeff Garzik
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Greg KH
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Jeff Garzik
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Greg KH
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Ilpo Järvinen
      • Re: [RESEND] benet: BladeEngine 10Gb NIC driver,Greg KH
• [PATCH] uvesafb: fix selecting mode with the vbemode option,Michal Januszewski
• kuroboxHG.dts compile FATAL ERROR on 2.6.26,The Peach
  • Re: kuroboxHG.dts compile FATAL ERROR on 2.6.26,Guennadi Liakhovetski
    • Re: kuroboxHG.dts compile FATAL ERROR on 2.6.26,The Peach
• [PATCH] nets: clean up net/ipv4/*,Jianjun Kong
• powerpc: struct device - replace bus_id with dev_name(), dev_set_name(),Kay Sievers
  • Re: powerpc: struct device - replace bus_id with dev_name(), dev_set_name(),Geoff Levand
• rapidio: struct device - replace bus_id with dev_name(), dev_set_name(),Kay Sievers
• regulator: struct device - replace bus_id with dev_name(), dev_set_name(),Kay Sievers
  • Re: regulator: struct device - replace bus_id with dev_name(), dev_set_name(),Liam Girdwood
• [PATCH 0/6] x86: unify fixmap.h,Gustavo F. Padovan
  • [PATCH 1/6] x86: rename __FIXADDR_SIZE and __FIXADDR_BOOT_SIZE,Gustavo F. Padovan
    • [PATCH 2/6] x86: define FIXADDR_BOOT_* and redefine FIX_ADDR_SIZE,Gustavo F. Padovan
      • [PATCH 3/6] x86: define reserve_top_address for x86_64,Gustavo F. Padovan
      • [PATCH 4/6] x86: Add CONFIG_X86_{LOCAL,IO}_APIC,Gustavo F. Padovan
      • [PATCH 5/6] x86: Add CONFIG_EFI,Gustavo F. Padovan
      • [PATCH 6/6] x86: Unify fixmap.h,Gustavo F. Padovan
    • Re: [PATCH 1/6] x86: rename __FIXADDR_SIZE and __FIXADDR_BOOT_SIZE,Ingo Molnar
      • Re: [PATCH 1/6] x86: rename __FIXADDR_SIZE and __FIXADDR_BOOT_SIZE,Gustavo F. Padovan
• [PATCH 1/1] USBHID: correct start/stop cycle,Jiri Slaby
  • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Jiri Kosina
    • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Jiri Slaby
      • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Helge Deller
      • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Jiri Slaby
      • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Helge Deller
      • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Denys Vlasenko
      • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Jiri Kosina
      • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Denys Vlasenko
      • Who broke cb8f488c33 patch? (was Re: [PATCH 1/1] USBHID: correct start/stop cycle),Jiri Kosina
      • Re: Who broke cb8f488c33 patch? (was Re: [PATCH 1/1] USBHID: correct start/stop cycle),Andrew Morton
      • Re: Who broke cb8f488c33 patch? (was Re: [PATCH 1/1] USBHID: correct start/stop cycle),Jiri Slaby
      • Re: Who broke cb8f488c33 patch? (was Re: [PATCH 1/1] USBHID: correct start/stop cycle),Helge Deller
      • Re: Who broke cb8f488c33 patch? (was Re: [PATCH 1/1] USBHID: correct start/stop cycle),Linus Torvalds
  • Re: [PATCH 1/1] USBHID: correct start/stop cycle,Jiri Kosina
• Re: [RFC PATCH] ide-floppy partitions,Borislav Petkov
  • Re: [RFC PATCH] ide-floppy partitions,Tejun Heo
    • Re: [RFC PATCH] ide-floppy partitions,Borislav Petkov
      • Subject: [PATCH] block: fix __blkdev_get() for removable devices,Tejun Heo
      • Re: Subject: [PATCH] block: fix __blkdev_get() for removable devices,Borislav Petkov
      • Re: Subject: [PATCH] block: fix __blkdev_get() for removable devices,Jens Axboe
• [STAGING]: How does one set CONFIG_STAGING=y in 2.6.28-rc2 ?,f . duncan . m . haldane
  • Re: [STAGING]: How does one set CONFIG_STAGING=y in 2.6.28-rc2 ?,Jiri Kosina
• Ralink RT2700E driver,Artur Szymczak
  • Re: Ralink RT2700E driver,J.R. Mauro
• [PATCH] ftrace: sysrq-z to dump the buffers,Peter Zijlstra
  • Re: [PATCH] ftrace: sysrq-z to dump the buffers,Steven Rostedt
    • Re: [PATCH] ftrace: sysrq-z to dump the buffers,Peter Zijlstra
• [mm][PATCH 0/4] Memory cgroup hierarchy introduction,Balbir Singh
  • [mm] [PATCH 1/4] Memory cgroup hierarchy documentation,Balbir Singh
    • Re: [mm] [PATCH 1/4] Memory cgroup hierarchy documentation,Paul Menage
      • Re: [mm] [PATCH 1/4] Memory cgroup hierarchy documentation,Paul Menage
      • Re: [mm] [PATCH 1/4] Memory cgroup hierarchy documentation,Balbir Singh
  • [mm] [PATCH 2/4] Memory cgroup resource counters for hierarchy,Balbir Singh
    • Re: [mm] [PATCH 2/4] Memory cgroup resource counters for hierarchy,KAMEZAWA Hiroyuki
      • Re: [mm] [PATCH 2/4] Memory cgroup resource counters for hierarchy,Balbir Singh
      • Re: [mm] [PATCH 2/4] Memory cgroup resource counters for hierarchy,KAMEZAWA Hiroyuki
      • Re: [mm] [PATCH 2/4] Memory cgroup resource counters for hierarchy,Balbir Singh
  • [mm] [PATCH 3/4] Memory cgroup hierarchical reclaim,Balbir Singh
    • Re: [mm] [PATCH 3/4] Memory cgroup hierarchical reclaim,KAMEZAWA Hiroyuki
      • Re: [mm] [PATCH 3/4] Memory cgroup hierarchical reclaim,Balbir Singh
      • Re: [mm] [PATCH 3/4] Memory cgroup hierarchical reclaim,KAMEZAWA Hiroyuki
      • Re: [mm] [PATCH 3/4] Memory cgroup hierarchical reclaim,Balbir Singh
      • Re: [mm] [PATCH 3/4] Memory cgroup hierarchical reclaim,KAMEZAWA Hiroyuki
      • Re: [mm] [PATCH 3/4] Memory cgroup hierarchical reclaim,Balbir Singh
  • [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,Balbir Singh
    • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,KAMEZAWA Hiroyuki
      • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,Balbir Singh
      • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,KAMEZAWA Hiroyuki
      • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,Balbir Singh
      • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,Paul Menage
      • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,Balbir Singh
      • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,Balbir Singh
      • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,Balbir Singh
      • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector,KAMEZAWA Hiroyuki
  • Re: [mm][PATCH 0/4] Memory cgroup hierarchy introduction,KAMEZAWA Hiroyuki
    • Re: [mm][PATCH 0/4] Memory cgroup hierarchy introduction,Balbir Singh
      • Re: [mm][PATCH 0/4] Memory cgroup hierarchy introduction,KAMEZAWA Hiroyuki
      • Re: [mm][PATCH 0/4] Memory cgroup hierarchy introduction,Balbir Singh
      • Re: [mm][PATCH 0/4] Memory cgroup hierarchy introduction,KAMEZAWA Hiroyuki
  • [patch 1/2] memcg: hierarchy, yet another one.,KAMEZAWA Hiroyuki
  • [patch 1/2] memcg: hierarchy, yet another one.,KAMEZAWA Hiroyuki
• [PATCH] section fixes for cirrusfb,Al Viro
• [PATCH] [sparc32] kernel/trace/trace.c wants DIE_OOPS,Al Viro
  • Re: [PATCH] [sparc32] kernel/trace/trace.c wants DIE_OOPS,David Miller
• [PATCH] el3_common_init() should be __devinit, not __init,Al Viro
  • Re: [PATCH] el3_common_init() should be __devinit, not __init,Alexey Dobriyan
    • Re: [PATCH] el3_common_init() should be __devinit, not __init,Al Viro
      • Re: [PATCH] el3_common_init() should be __devinit, not __init,Alexey Dobriyan
      • Re: [PATCH] el3_common_init() should be __devinit, not __init,Al Viro
      • Re: [PATCH] el3_common_init() should be __devinit, not __init,Sam Ravnborg
      • Re: [PATCH] el3_common_init() should be __devinit, not __init,Linus Torvalds
      • Re: [PATCH] el3_common_init() should be __devinit, not __init,Al Viro
      • Re: [PATCH] el3_common_init() should be __devinit, not __init,Sam Ravnborg
  • Re: [PATCH] el3_common_init() should be __devinit, not __init,Jeff Garzik
• [PATCH] PM_TEST_SUSPEND should depend on RTC_CLASS, not RTC_LIB,Al Viro
• [PATCH] missing dependencies on HAS_CLK in drivers/mfd,Al Viro
  • Re: [PATCH] missing dependencies on HAS_CLK in drivers/mfd,Al Viro
• [PATCH] fix O_NONBLOCK in dmasound_core,Al Viro
• Problems with the block-layer timeouts,Alan Stern
  • Re: Problems with the block-layer timeouts,Mike Anderson
  • Re: Problems with the block-layer timeouts,Jens Axboe
    • Re: Problems with the block-layer timeouts,James Smart
      • Re: Problems with the block-layer timeouts,Jens Axboe
    • Re: Problems with the block-layer timeouts,Alan Stern
      • Re: Problems with the block-layer timeouts,Tejun Heo
      • Re: Problems with the block-layer timeouts,Alan Stern
      • Re: Problems with the block-layer timeouts,Jens Axboe
      • Re: Problems with the block-layer timeouts,Tejun Heo
    • Re: Problems with the block-layer timeouts,FUJITA Tomonori
      • Re: Problems with the block-layer timeouts,Jens Axboe
      • Re: Problems with the block-layer timeouts,FUJITA Tomonori
      • Re: Problems with the block-layer timeouts,Jens Axboe
      • Re: Problems with the block-layer timeouts,FUJITA Tomonori
      • Re: Problems with the block-layer timeouts,Alan Stern
      • Re: Problems with the block-layer timeouts,Jens Axboe
      • Re: Problems with the block-layer timeouts,FUJITA Tomonori
      • Re: Problems with the block-layer timeouts,Jens Axboe
      • Re: Problems with the block-layer timeouts,FUJITA Tomonori
• epoll behaviour after running out of descriptors,Olaf van der Spek
  • Re: epoll behaviour after running out of descriptors,Davide Libenzi
    • Re: epoll behaviour after running out of descriptors,Olaf van der Spek
      • Re: epoll behaviour after running out of descriptors,Davide Libenzi
      • Re: epoll behaviour after running out of descriptors,Olaf van der Spek
      • Re: epoll behaviour after running out of descriptors,Eric Dumazet
      • Re: epoll behaviour after running out of descriptors,Olaf van der Spek
      • Re: epoll behaviour after running out of descriptors,Davide Libenzi
      • Re: epoll behaviour after running out of descriptors,Olaf van der Spek
      • Re: epoll behaviour after running out of descriptors,Davide Libenzi
      • Re: epoll behaviour after running out of descriptors,Olaf van der Spek
      • Re: epoll behaviour after running out of descriptors,Davide Libenzi
      • Re: epoll behaviour after running out of descriptors,Olaf van der Spek
      • Re: epoll behaviour after running out of descriptors,Davide Libenzi
      • Re: epoll behaviour after running out of descriptors,Olaf van der Spek
• (BUG?) round_jiffies() is non-monotonic on SMP,Alan Stern
  • Re: (BUG?) round_jiffies() is non-monotonic on SMP,Arjan van de Ven
    • Re: (BUG?) round_jiffies() is non-monotonic on SMP,Alan Stern
      • Re: (BUG?) round_jiffies() is non-monotonic on SMP,Arjan van de Ven
      • Re: (BUG?) round_jiffies() is non-monotonic on SMP,Alan Stern
      • Re: (BUG?) round_jiffies() is non-monotonic on SMP,Arjan van de Ven
      • Re: (BUG?) round_jiffies() is non-monotonic on SMP,Alan Stern
• [PATCH] x86: nmi - nmi_watchdog boot param docs cleanup,Cyrill Gorcunov
  • Re: [PATCH] x86: nmi - nmi_watchdog boot param docs cleanup,Ingo Molnar
• 2.6.28-rc2: Unable to handle kernel paging request at iov_iter_copy_from_user_atomic,Alexander Beregalov
  • Re: 2.6.28-rc2: Unable to handle kernel paging request at iov_iter_copy_from_user_atomic,Hugh Dickins
    • Re: 2.6.28-rc2: Unable to handle kernel paging request at iov_iter_copy_from_user_atomic,Alexander Beregalov
      • Re: 2.6.28-rc2: Unable to handle kernel paging request at iov_iter_copy_from_user_atomic,David Miller
    • Re: 2.6.28-rc2: Unable to handle kernel paging request at iov_iter_copy_from_user_atomic,David Miller
• ↖風花雅韻☆ve性福生活☆嫵媚夜激情↖,林欣怡
• [PATCH] ftrace: ftrace_dump_on_oops=[tracer],Peter Zijlstra
  • Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer],Steven Rostedt
    • Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer],Peter Zijlstra
      • Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer],Steven Rostedt
      • Re: [PATCH] ftrace: ftrace_dump_on_oops=[tracer],Ingo Molnar
• Can you use the USB HID interface within a driver?,Adam Nielsen
  • Re: Can you use the USB HID interface within a driver?,Oliver Neukum
    • Re: Can you use the USB HID interface within a driver?,Adam Nielsen
      • Re: Can you use the USB HID interface within a driver?,Kay Sievers
  • Re: Can you use the USB HID interface within a driver?,Jiri Kosina
    • Re: Can you use the USB HID interface within a driver?,Adam Nielsen
      • Driver for new hid class (was: Can you use the USB HID interface within a driver?),Adam Nielsen
      • Re: Driver for new hid class,Jiri Slaby
• serial port problem,Dmitry Melekhov
  • Re: serial port problem,Adam Nielsen
• [PATCH] Many headers included multiple times,Steve Kemp
  • Re: [PATCH] Many headers included multiple times,Andrew Morton
• pcmcia: struct device - replace bus_id with dev_name(), dev_set_name(),Kay Sievers
  • Re: pcmcia: struct device - replace bus_id with dev_name(), dev_set_name(),Dominik Brodowski
    • Re: pcmcia: struct device - replace bus_id with dev_name(), dev_set_name(),Kay Sievers
      • Re: pcmcia: struct device - replace bus_id with dev_name(), dev_set_name(),Dominik Brodowski
• [PATCH/2] nets: fix problem of return value,Jianjun Kong
  • Re: [PATCH/2] nets: fix problem of return value,David Miller
• [PATCH/1] nets:clean up net/unix/af_unix.c garbage.c sysctl_net_unix.c,Jianjun Kong
  • Re: [PATCH/1] nets:clean up net/unix/af_unix.c garbage.c sysctl_net_unix.c,David Miller
• task sadc:1148 blocked for more than 120 seconds.,Toralf Förster
• For Embroidery Designs,Galileo
• ∵風花雅韻☆ve性福生活☆嫵媚夜激情∴,蔡志祥
• [PATCH] smc91x: add __init markings to smc_drv_probe(),Mike Frysinger
• removal of fs/proc/inode-alloc.txt,Peter Teoh
  • Re: removal of fs/proc/inode-alloc.txt,Randy Dunlap
• ALPS input driver problem with DualPoint on Dell E6400/E6500,Matthew Chapman
  • Re: ALPS input driver problem with DualPoint on Dell E6400/E6500,Frederik Himpe
  • <Possible follow-ups>
  • Re: ALPS input driver problem with DualPoint on Dell E6400/E6500,Alexander Hofbauer
• 2.6.28-rc2-git6 fails compile -- cpu/common.c,Pete Clements
  • Re: 2.6.28-rc2-git6 fails compile -- cpu/common.c,Jianjun Kong
    • Re: 2.6.28-rc2-git6 fails compile -- cpu/common.c,Jianjun Kong
• [PATCH] Staging: remove double #include,Alexander Beregalov
• Re: readahead in the 2.6.25+ kernel,Wu Fengguang
• [RFC git pull 1/2] Move CRIS header files,Jesper Nilsson
  • [RFC git pull 2/2] Remove CRIS build links,Jesper Nilsson
• [RFC][PATCH] saner FASYNC handling on file close,Al Viro
  • Re: [RFC][PATCH] saner FASYNC handling on file close,Linus Torvalds
• 2.6.8-rc2 build problem,Hans de Bruin
  • Re: 2.6.8-rc2 build problem,Hans de Bruin
• em28xx merge process issues with linuxtv and upstream kernel,Jelle de Jong
  • Re: [linux-dvb] em28xx merge process issues with linuxtv and upstream kernel,Thierry Merle
    • Re: [linux-dvb] em28xx merge process issues with linuxtv and upstream kernel,Markus Rechberger
      • Re: [linux-dvb] em28xx merge process issues with linuxtv and upstream kernel,Mauro Carvalho Chehab
      • Re: [linux-dvb] em28xx merge process issues with linuxtv and upstream kernel,Markus Rechberger
• [PATCH] Fix block dev compat ioctl handling,Andreas Schwab
• [patch] x86: Kill bogus MTRR warning when running under vmware,Chuck Ebbert
  • Re: [patch] x86: Kill bogus MTRR warning when running under vmware,Ingo Molnar
• Metadata in sys_sync_file_range and fadvise(DONTNEED),Chad Talbott
  • Re: Metadata in sys_sync_file_range and fadvise(DONTNEED),Andrew Morton
    • Re: Metadata in sys_sync_file_range and fadvise(DONTNEED),Chad Talbott
      • Re: Metadata in sys_sync_file_range and fadvise(DONTNEED),Andrew Morton
      • Re: Metadata in sys_sync_file_range and fadvise(DONTNEED),Chad Talbott
  • Re: Metadata in sys_sync_file_range and fadvise(DONTNEED),Dave Chinner
    • Re: Metadata in sys_sync_file_range and fadvise(DONTNEED),Chad Talbott
      • Re: Metadata in sys_sync_file_range and fadvise(DONTNEED),Dave Chinner
• [PATCH] x86: nmi - document lapic and ioapic parameters,Cyrill Gorcunov
  • Re: [PATCH] x86: nmi - document lapic and ioapic parameters,Aristeu Rozanski
  • Re: [PATCH] x86: nmi - document lapic and ioapic parameters,Yinghai Lu
    • Re: [PATCH] x86: nmi - document lapic and ioapic parameters,H. Peter Anvin
      • Re: [PATCH] x86: nmi - document lapic and ioapic parameters,Yinghai Lu
      • Re: [PATCH] x86: nmi - document lapic and ioapic parameters,Cyrill Gorcunov
      • Re: [PATCH] x86: nmi - document lapic and ioapic parameters,Cyrill Gorcunov
• [PATCH-linux-next] ia64: fix build breakage in smp.h,Luck, Tony
  • Re: [PATCH-linux-next] ia64: fix build breakage in smp.h,Ingo Molnar
• [PATCH] Use BIOS reboot on Toshiba Portege 4000,Andrey Borzenkov
  • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Ingo Molnar
    • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Avi Kivity
      • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Ingo Molnar
      • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Eduardo Habkost
      • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Avi Kivity
      • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Eric W. Biederman
      • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Eduardo Habkost
      • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Avi Kivity
      • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Eric W. Biederman
      • Re: [PATCH] Use BIOS reboot on Toshiba Portege 4000,Eduardo Habkost
• [PATCH] [RESEND] x86: add memory hotremove config option,Gary Hade
  • Re: [PATCH] [RESEND] x86: add memory hotremove config option,Ingo Molnar
• [Patch] ipc: clean up ipc/shm.c,Américo Wang
• [PATCH] tags: link from CONFIG_x to 'config x' as well,Alexey Dobriyan
  • Re: [PATCH] tags: link from CONFIG_x to 'config x' as well,Sam Ravnborg
• eeepc-laptop rfkill, stupid question #4 and 5,Alan Jenkins
  • Re: eeepc-laptop rfkill, stupid question #4 and 5,Matthew Garrett
    • Re: eeepc-laptop rfkill, stupid question #4 and 5,Alan Jenkins
      • Re: eeepc-laptop rfkill, stupid question #4 and 5,Alan Jenkins
      • Re: eeepc-laptop rfkill, stupid question #4 and 5,Henrique de Moraes Holschuh
      • Re: eeepc-laptop rfkill, stupid question #4,Alan Jenkins
      • Re: eeepc-laptop rfkill, stupid question #4,Matthew Garrett
      • Re: eeepc-laptop rfkill, stupid question #4,Alan Jenkins
      • Re: eeepc-laptop rfkill, stupid question #4,Matthew Garrett
      • Re: eeepc-laptop rfkill, stupid question #4,Henrique de Moraes Holschuh
      • Re: eeepc-laptop rfkill, stupid question #4,Henrique de Moraes Holschuh
      • Re: eeepc-laptop rfkill, stupid question #4,Matthew Garrett
      • Re: eeepc-laptop rfkill, stupid question #4,Alan Jenkins
      • Re: eeepc-laptop rfkill, stupid question #4,Henrique de Moraes Holschuh
      • Re: eeepc-laptop rfkill, stupid question #4,Matthew Garrett
      • Re: eeepc-laptop rfkill, stupid question #4,Henrique de Moraes Holschuh
      • Re: eeepc-laptop rfkill, stupid question #4,Matthew Garrett
      • Re: eeepc-laptop rfkill, stupid question #4,Henrique de Moraes Holschuh
      • Re: rfkill, stupid question #6,Alan Jenkins
      • Re: rfkill, stupid question #6,Henrique de Moraes Holschuh
      • Re: eeepc-laptop rfkill, stupid question #4,Luiz Fernando N. Capitulino
      • Re: eeepc-laptop rfkill, stupid question #4,Alan Jenkins
    • Re: eeepc-laptop rfkill, stupid question #4 and 5,Henrique de Moraes Holschuh
      • Re: eeepc-laptop rfkill, stupid question #4 and 5,Matthew Garrett
• alpha: undefined reference to `save_stack_trace',Alexey Dobriyan
  • Re: alpha: undefined reference to `save_stack_trace',Al Viro
    • Re: alpha: undefined reference to `save_stack_trace',Al Viro
      • [PATCH] Re: alpha: undefined reference to `save_stack_trace',Al Viro
      • Re: [PATCH] Re: alpha: undefined reference to `save_stack_trace',Al Viro
      • Re: [PATCH] Re: alpha: undefined reference to `save_stack_trace',Al Viro
      • Re: [PATCH] Re: alpha: undefined reference to `save_stack_trace',Steven Rostedt
      • Re: [PATCH] Re: alpha: undefined reference to `save_stack_trace',Al Viro
      • Re: [PATCH] Re: alpha: undefined reference to `save_stack_trace',Ingo Molnar
• sched domains oddness.,Dave Jones
  • Re: sched domains oddness.,Peter Zijlstra
    • Re: sched domains oddness.,Suresh Siddha
      • Re: sched domains oddness.,Dave Jones
      • Re: sched domains oddness.,Dave Jones
      • Re: sched domains oddness.,Suresh Siddha
      • Re: sched domains oddness.,Dave Jones
    • Re: sched domains oddness.,Dave Jones
• build issue #576 for v2.6.28-rc2-385-g721d5df :'boot_cpu_id' undeclared,Toralf Förster
  • Re: build issue #576 for v2.6.28-rc2-385-g721d5df :'boot_cpu_id' undeclared,Américo Wang
    • Re: build issue #576 for v2.6.28-rc2-385-g721d5df :'boot_cpu_id' undeclared,Cyrill Gorcunov
• data corruption: revalidating a (removable) hdd/flash on re-insert,Michael Tokarev
  • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Lennart Sorensen
    • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Michael Tokarev
      • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Lennart Sorensen
  • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Kay Sievers
    • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Michael Tokarev
      • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Kay Sievers
    • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Pavel Machek
      • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Kay Sievers
      • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Pavel Machek
      • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Michael Tokarev
      • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Pavel Machek
      • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Michael Tokarev
      • Re: data corruption: revalidating a (removable) hdd/flash on re-insert,Kay Sievers
• [PATCH][RESEND] checkpatch: Add warning for p0-patches,Wolfram Sang
  • Re: [PATCH][RESEND] checkpatch: Add warning for p0-patches,Andy Whitcroft
    • Re: [PATCH][RESEND] checkpatch: Add warning for p0-patches,Borislav Petkov
      • Re: [PATCH][RESEND] checkpatch: Add warning for p0-patches,Wolfram Sang
      • Re: [PATCH][RESEND] checkpatch: Add warning for p0-patches,Borislav Petkov
      • Re: [PATCH][RESEND] checkpatch: Add warning for p0-patches,Wolfram Sang
      • Re: [PATCH][RESEND] checkpatch: Add warning for p0-patches,Borislav Petkov
• Measuring boot time on beagle board with PRINTK_TIME,Shivdas Gujare
  • Re: Measuring boot time on beagle board with PRINTK_TIME,Shivdas Gujare
• 2.6.28-rc2-git1: spitz still won't boot,Pavel Machek
  • Re: 2.6.28-rc2-git1: spitz still won't boot,Rafael J. Wysocki
    • Re: 2.6.28-rc2-git1: spitz still won't boot,Pavel Machek
      • Re: 2.6.28-rc2-git1: spitz still won't boot,Russell King
      • Re: 2.6.28-rc2-git1: spitz still won't boot,Pavel Machek
  • Re: 2.6.28-rc3-git1: spitz still won't boot,Pavel Machek
    • Re: 2.6.28-rc3-git1: spitz still won't boot,Dmitry
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Pavel Machek
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Dmitry
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Pavel Machek
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Cyril Hrubis
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Eric Miao
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Pavel Machek
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Dmitry
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Russell King
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Richard Purdie
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Dmitry
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Russell King
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Dmitry
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Russell King
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Pavel Machek
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Pavel Machek
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Dmitry
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Pavel Machek
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Dmitry
      • Re: 2.6.28-rc3-git1: spitz still won't boot,Pavel Machek
• schedule tracing,Steven Rostedt
  • [PATCH] ftrace: trace sched.c,Peter Zijlstra
    • Re: [PATCH] ftrace: trace sched.c,Ingo Molnar
• console_sem locking annotations?,Geert Uytterhoeven
• [PATCH] fbdev: Fix fb_compat_ioctl() deadlocks (was: Re: [Linux-fbdev-devel] framebuffer compat_ioctl deadlock),Geert Uytterhoeven
• Staging: wlan-ng: remove unused #include <version.h>,Huang Weiyi
• SLAB vs. SLUB tbench regression (Was: [tbench regression fixes]: digging out smelly deadmen.),Pekka Enberg
  • Re: SLAB vs. SLUB tbench regression (Was: [tbench regression fixes]: digging out smelly deadmen.),Pekka Enberg
  • Re: SLAB vs. SLUB tbench regression (Was: [tbench regression fixes]: digging out smelly deadmen.),Evgeniy Polyakov
• [patch 0/2] Tracepoints updates for -tip,mathieu . desnoyers
  • [patch 2/2] tracepoint: introduce *_noupdate APIs. (v2),mathieu . desnoyers
  • [patch 1/2] tracepoint: simplify for tracepoint using RCU,mathieu . desnoyers
  • Re: [patch 0/2] Tracepoints updates for -tip,Ingo Molnar
• [PATCH 1/1] file caps: always start with clear bprm->caps_*,Serge E. Hallyn
• Re: HP WMI laptop extras driver,Matthew Garrett
  • <Possible follow-ups>
  • Re: HP WMI laptop extras driver,Daniel Perzynski
    • Re: HP WMI laptop extras driver,Matthew Garrett
  • Re: HP WMI laptop extras driver,Matthew Garrett
• [PATCH] Fix PCI resource mmaping on sparc64,Max Dmitrichenko
  • Re: [PATCH] Fix PCI resource mmaping on sparc64,David Miller
• Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ?,Shivdas Gujare
  • Re: Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ?,Alan Jenkins
  • Re: [beagleboard] Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ?,Ming Lei
    • Re: [beagleboard] Diff between Linux-2.6.27-omap1-dirty and Linux-2.6.27-omap1 ?,Tony Lindgren
• ath5k gets lost with eeepc-laptop removal,Luiz Fernando N. Capitulino
  • Re: ath5k gets lost with eeepc-laptop removal,Alan Jenkins
    • Re: ath5k gets lost with eeepc-laptop removal,Matthew Garrett
      • Re: ath5k gets lost with eeepc-laptop removal,Nick Kossifidis
      • Re: ath5k gets lost with eeepc-laptop removal,Matthew Garrett
  • Re: ath5k gets lost with eeepc-laptop removal,Nick Kossifidis
    • Re: ath5k gets lost with eeepc-laptop removal,Luiz Fernando N. Capitulino
      • Re: ath5k gets lost with eeepc-laptop removal,Nick Kossifidis
      • Re: ath5k gets lost with eeepc-laptop removal,Luiz Fernando N. Capitulino
      • Re: ath5k gets lost with eeepc-laptop removal,Luiz Fernando N. Capitulino
      • Re: ath5k gets lost with eeepc-laptop removal,Matthew Garrett
• [PATCH] small optimization to update_curr_rt,Dimitri Sivanich
  • Re: [PATCH] small optimization to update_curr_rt,Steven Noonan
    • Re: [PATCH] small optimization to update_curr_rt,Dimitri Sivanich
  • Re: [PATCH] small optimization to update_curr_rt,Peter Zijlstra
    • Re: [PATCH] small optimization to update_curr_rt,Ingo Molnar
• [PATCH][RESEND] tracing/ftrace: Fix a bug when switch current tracer to sched tracer,Frederic Weisbecker
• [PATCH][RESEND] tracing/ftrace: Types and naming corrections for sched tracer,Frederic Weisbecker
• [PATCH][RESEND] tracing/fastboot: Use sched switch tracer from boot tracer,Frederic Weisbecker
• [PATCH][RESEND] tracing/ftrace: Remove unused code in sched_switch tracer,Frederic Weisbecker
  • Re: [PATCH][RESEND] tracing/ftrace: Remove unused code in sched_switch tracer,Frédéric Weisbecker
• [PATCH][RESEND] tracing/ftrace: Fix a race condition in sched_switch tracer,Frederic Weisbecker
• [PATCH][RESEND] Tracing/fastboot: Enable boot tracing only during initcalls,Frederic Weisbecker
  • Re: [PATCH][RESEND] Tracing/fastboot: Enable boot tracing only during initcalls,Ingo Molnar
• Where is asm-ia64 directory in 2.6.27 kernel?,jidong xiao
  • Re: Where is asm-ia64 directory in 2.6.27 kernel?,Jike Song
  • Re: Where is asm-ia64 directory in 2.6.27 kernel?,Américo Wang
    • Re: Where is asm-ia64 directory in 2.6.27 kernel?,jidong xiao
• [PATCH] Avoid duplicate running of pud_offset and pmd_offset in one_md_table_init(),Zhaolei
  • Re: [PATCH] Avoid duplicate running of pud_offset and pmd_offset in one_md_table_init(),Ingo Molnar
• 山鉧科技網頁設計,陳佩孝
  • <Possible follow-ups>
  • 山鉧科技網頁設計,吳虹財
  • 山鉧科技網頁設計,謝珮蓁
• Ideas on printk_ratelimit(),Ulrich Windl
• [GIT PULL] sh updates for 2.6.28-rc3,Paul Mundt
• [PATCH] fork.c: cleanup for copy_sighand(),Zhaolei
  • Re: [PATCH] fork.c: cleanup for copy_sighand(),Andrew Morton
• linux-next: Tree for October 31,Stephen Rothwell
  • Re: linux-next: Tree for October 31 (repeat build failures),Randy Dunlap
  • Re: linux-next: Tree for October 31,Vegard Nossum
    • Re: linux-next: Tree for October 31,Christoph Lameter
      • Re: linux-next: Tree for October 31,Stephen Rothwell
• Weird behaviour on iwl3945 module,Rafael Cunha de Almeida
  • Re: Weird behaviour on iwl3945 module,Rafael Almeida
  • <Possible follow-ups>
  • RE: Weird behaviour on iwl3945 module,Carsten Niehaus
    • Re: Weird behaviour on iwl3945 module,Iain
• [PATCH 2.6.28-rc2] sata_promise: add ATA engine reset to reset ops,Mikael Pettersson
  • Re: [PATCH 2.6.28-rc2] sata_promise: add ATA engine reset to reset ops,Jeff Garzik
• [git patches] net driver updates for 2.6.29,Jeff Garzik
  • Re: [git patches] net driver updates for 2.6.29,David Miller
  • <Possible follow-ups>
  • [git patches] net driver updates for 2.6.29,Jeff Garzik
    • Re: [git patches] net driver updates for 2.6.29,David Miller
  • [git patches] net driver updates for 2.6.29,Jeff Garzik
    • Re: [git patches] net driver updates for 2.6.29,David Miller
      • Re: [git patches] net driver updates for 2.6.29,Jeff Garzik
      • Re: [git patches] net driver updates for 2.6.29,David Miller
• [git patches] net driver fixes for 2.6.28-rc,Jeff Garzik
  • Re: [git patches] net driver fixes for 2.6.28-rc,David Miller
  • <Possible follow-ups>
  • [git patches] net driver fixes for 2.6.28-rc,Jeff Garzik
    • Re: [git patches] net driver fixes for 2.6.28-rc,David Miller
    • Re: [git patches] net driver fixes for 2.6.28-rc,Marcel Holtmann
      • Re: [git patches] net driver fixes for 2.6.28-rc,David Miller
      • Re: [git patches] net driver fixes for 2.6.28-rc,Jeff Garzik
  • Re: [git patches] net driver fixes for 2.6.28-rc,Jonathan McDowell
    • Re: [git patches] net driver fixes for 2.6.28-rc,Marcel Holtmann
    • Re: [git patches] net driver fixes for 2.6.28-rc,Jeff Garzik
  • [git patches] net driver fixes for 2.6.28-rc,Jeff Garzik
    • Re: [git patches] net driver fixes for 2.6.28-rc,David Miller
  • [git patches] net driver fixes for 2.6.28-rc,Jeff Garzik
    • Re: [git patches] net driver fixes for 2.6.28-rc,David Miller
  • [git patches] net driver fixes for 2.6.28-rc,Jeff Garzik
    • Re: [git patches] net driver fixes for 2.6.28-rc,David Miller
• [GIT PULL] XFS update for 2.6.28,Lachlan McIlroy
  • Re: [GIT PULL] XFS update for 2.6.28,david
    • Re: [GIT PULL] XFS update for 2.6.28,Steven Noonan
      • Re: [GIT PULL] XFS update for 2.6.28,Lachlan McIlroy
  • Re: [xfs] [GIT PULL] XFS update for 2.6.28,Russell Cattelan
    • Re: [xfs] [GIT PULL] XFS update for 2.6.28,Lachlan McIlroy
      • Re: [xfs] [GIT PULL] XFS update for 2.6.28,Russell Cattelan
      • Re: [xfs] [GIT PULL] XFS update for 2.6.28,Lachlan McIlroy
  • <Possible follow-ups>
  • [GIT PULL] XFS update for 2.6.28,Lachlan McIlroy
    • Re: [GIT PULL] XFS update for 2.6.28,Christoph Hellwig
      • Re: [GIT PULL] XFS update for 2.6.28,Damien Wyart
      • Re: [GIT PULL] XFS update for 2.6.28,Christoph Hellwig
      • Re: [GIT PULL] XFS update for 2.6.28,Linus Torvalds
• [GIT PULL] ext4 fixes,Theodore Ts'o
  • <Possible follow-ups>
  • [GIT PULL] ext4 fixes,Theodore Ts'o
    • Re: [GIT PULL] ext4 fixes,Linus Torvalds
      • Re: [GIT PULL] ext4 fixes,Theodore Tso
      • Re: [GIT PULL] ext4 fixes,Theodore Tso
• [PATCH] Correct wrong function name of d_put in kernel document and source comment,Zhaolei
• [RFC][PATCH 0/5] memcg : some patches related to swap.,KAMEZAWA Hiroyuki
  • [RFC][PATCH 1/5] memcg : force_empty to do move account,KAMEZAWA Hiroyuki
    • Re: [RFC][PATCH 1/5] memcg : force_empty to do move account,Daisuke Nishimura
    • Re: [RFC][PATCH 1/5] memcg : force_empty to do move account,Paul Menage
      • Re: [RFC][PATCH 1/5] memcg : force_empty to do move account,KAMEZAWA Hiroyuki
      • Re: [RFC][PATCH 1/5] memcg : force_empty to do move account,Paul Menage
      • Re: [RFC][PATCH 1/5] memcg : force_empty to do move account,KAMEZAWA Hiroyuki
  • [RFC][PATCH 2/5] memcg : handle swap cache,KAMEZAWA Hiroyuki
    • Re: [RFC][PATCH 2/5] memcg : handle swap cache,Daisuke Nishimura
      • Re: [RFC][PATCH 2/5] memcg : handle swap cache,KAMEZAWA Hiroyuki
      • Re: [RFC][PATCH 2/5] memcg : handle swap cache,Daisuke Nishimura
      • Re: [RFC][PATCH 2/5] memcg : handle swap cache,KAMEZAWA Hiroyuki
      • Re: [RFC][PATCH 2/5] memcg : handle swap cache,KAMEZAWA Hiroyuki
  • [RFC][PATCH 3/5] memcg : mem+swap controller kconfig,KAMEZAWA Hiroyuki
    • Re: [RFC][PATCH 3/5] memcg : mem+swap controller kconfig,Daisuke Nishimura
      • Re: [RFC][PATCH 3/5] memcg : mem+swap controller kconfig,KAMEZAWA Hiroyuki
  • [RFC][PATCH 4/5] memcg : add swap_cgroup,KAMEZAWA Hiroyuki
  • [RFC][PATCH 5/5] memcg : mem+swap controller,KAMEZAWA Hiroyuki
  • [RFC][PATCH 6/5] memcg : synchronous LRU,KAMEZAWA Hiroyuki
• [PATCH] Add io-mapping functions to dynamically map large device apertures,Eric Anholt
  • [PATCH] i915: Use io-mapping interfaces instead of a variety of mapping kludges,Eric Anholt
  • Re: [PATCH] Add io-mapping functions to dynamically map large device apertures,Ingo Molnar
    • Re: [PATCH] Add io-mapping functions to dynamically map large device apertures,Keith Packard
      • Re: [PATCH] Add io-mapping functions to dynamically map large device apertures,Ingo Molnar
• [PATCH] x86: Add io_map_atomic on 32-bit using fixmaps,Eric Anholt
• nohz regression with upstream git,Venki Pallipadi
  • Re: nohz regression with upstream git,Simon Holm Thøgersen
• [PATCH 3/3 -v4] kexec/i386: setup kexec page table in C,Huang Ying
• [PATCH 2/3 -v4] kexec/i386: allocate page table pages dynamically,Huang Ying
• [PATCH 1/3 -v4] kexec/i386: remove PAGE_SIZE alignment from relocate_kernel,Huang Ying
• [PATCH 0/3 -v4] kexec/i386: kexec page table code clean up,Huang Ying
  • Re: [PATCH 0/3 -v4] kexec/i386: kexec page table code clean up,Ingo Molnar
• bugs in acroread and