Linux Kernel Newbies

• Thread Index

• Re: Generic Disk Driver in Linux
  • From: Ralf Baechle <ralf@xxxxxxxxxxxxxx>
• two flag
  • From: "liang yuanen" <linux.kernel.liang@xxxxxxxxx>
• Re: Generic Disk Driver in Linux
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: platform_device question
  • From: "Drasko Draskovic" <drasko.draskovic@xxxxxxxxx>
• Generic Disk Driver in Linux
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: Reading the GDT in kernel space?
  • From: mohanlal jangir <mohanlal@xxxxxxxxxxx>
• Re: Virtual address
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• calling __dev_get_by_name without holding locks...
  • From: "Anupam Kapoor" <anupam.kapoor@xxxxxxxxx>
• Re: Re: Trying to make kernel thread sleep
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kobject_uevent() usage?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: kobject_uevent() usage?
  • From: Arun Thomas <arun@xxxxxxxxxxxx>
• Re: Trying to make kernel thread sleep
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• Re: Virtual address
  • From: "Manisha Maheshwari" <maheshwari.manisha@xxxxxxxxx>
• Re: Virtual address
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Virtual address
  • From: "Manisha Maheshwari" <maheshwari.manisha@xxxxxxxxx>
• Re: kernel panic pleas help me
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• Re: kobject_uevent() usage?
  • From: Greg KH <greg@xxxxxxxxx>
• kobject_uevent() usage?
  • From: Arun Thomas <arun@xxxxxxxxxxxx>
• Re: Reading the GDT in kernel space?
  • From: Josef Sipek <jsipek@xxxxxxxxxxxxxxxxx>
• Reading the GDT in kernel space?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Question about aper_size_info structs in agp.h
  • From: "Gerhard Pircher" <gerhard_pircher@xxxxxxx>
• Re: Linux Kernel Panic ! Unable to mount root fs on 00:00
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: Re: Re: waitpid(2) and CLONE_THREAD
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel panic pleas help me
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: How to debug the bug in initrd?
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: Linux Kernel Panic ! Unable to mount root fs on 00:00
  • From: "Abid Younas" <abidyounas@xxxxxxxxx>
• How to debug the bug in initrd?
  • From: "Zhao Forrest" <forrest.zhao@xxxxxxxxx>
• rs_input and nd6_rs_input in neighbor discovery module of ipv6
  • From: "kernel learner" <kernellearner@xxxxxxxxx>
• RE: Linux Kernel Panic ! Unable to mount root fs on 00:00
  • From: "Abhijit Pawar" <apawar@xxxxxxxxxx>
• kernel panic pleas help me
  • From: "Rajath N R" <rajathnr@xxxxxxxxx>
• Re: virtual or physical - kernelbase address?
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: copy_to_user() returns an error
  • From: denz aberilla <denzzzhome@xxxxxxxxx>
• Trying to make kernel thread sleep
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• RE: connection synchronization in layer 7 load balancer
  • From: <anshu.malini@xxxxxxxxx>
• Re: Driver matching
  • From: Greg KH <greg@xxxxxxxxx>
• Driver matching
  • From: Makrydakis Giannhs <makryd@xxxxxxxxxx>
• Re: connection synchronization in layer 7 load balancer
  • From: "Mouhammad Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: copy_to_user() returns an error
  • From: "Manoj Awasthi" <lkml.manoj@xxxxxxxxx>
• copy_to_user() returns an error
  • From: "John Que" <qwejohn@xxxxxxxxx>
• Re: Linux Kernel Panic ! Unable to mount root fs on 00:00
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Linux Kernel Panic ! Unable to mount root fs on 00:00
  • From: "Abhijit Pawar" <apawar@xxxxxxxxxx>
• Trying to make kernel thread sleep
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• Re: platform_device question
  • From: "Clay Renko" <renkoc@xxxxxxxxx>
• Re: #ifdef statement inside #define
  • From: "Nelson Castillo" <nelsoneci@xxxxxxxxx>
• Re: #ifdef statement inside #define
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: #ifdef statement inside #define
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: #ifdef statement inside #define
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: #ifdef statement inside #define
  • From: toni <topi23@xxxxxxxxx>
• Re: Re: waitpid(2) and CLONE_THREAD
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: #ifdef statement inside #define
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: #ifdef statement inside #define
  • From: Mark Hounschell <markh@xxxxxxxxxx>
• Re: platform_device question
  • From: "Bahadir Balban" <bahadir.balban@xxxxxxxxx>
• ide disk driver
  • From: "Bahadir Balban" <bilgehan.balban@xxxxxxxxx>
• Re: #ifdef statement inside #define
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• #ifdef statement inside #define
  • From: Katharina Denkinger <kdenki@xxxxxx>
• Re: Relation between free() and remove_vm_struct()
  • From: Andy Whitcroft <apw@xxxxxxxxxxxx>
• Re: Whether Bottom Halves run in Process context ?
  • From: "Rajath N R" <rajathnr@xxxxxxxxx>
• Re: Whether Bottom Halves run in Process context ?
  • From: Bernhard Walle <bernhard.walle@xxxxxx>
• Re: platform_device question
  • From: "Drasko Draskovic" <drasko.draskovic@xxxxxxxxx>
• Re: platform_device question
  • From: "Clay Renko" <renkoc@xxxxxxxxx>
• Re: Whether Bottom Halves run in Process context ?
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: Whether Bottom Halves run in Process context ?
  • From: "Ranjan Sinha" <rnjn.sinha@xxxxxxxxx>
• connection synchronization in layer 7 load balancer
  • From: <anshu.malini@xxxxxxxxx>
• connection synchronization in layer 7 load balancer
  • From: <anshu.malini@xxxxxxxxx>
• Re: Re: time slice calculation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: time slice calculation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: "time <apps>", is it the right thing to do to measure timing latency?
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• Re: Bound Hardware with TTY Driver
  • From: Greg KH <greg@xxxxxxxxx>
• RE: Porting device drivers from 2.4 to 2.6
  • From: "Mohapatra, Hemant" <Hemant.Mohapatra@xxxxxxx>
• Re: Can we rely on RDTSC
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Porting device drivers from 2.4 to 2.6
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Porting device drivers from 2.4 to 2.6
  • From: Greg KH <greg@xxxxxxxxx>
• Can we rely on RDTSC
  • From: "Tharindu Rukshan Bamunuarachchi" <tharindunix@xxxxxxxxx>
• Porting device drivers from 2.4 to 2.6
  • From: Ashok Sharma <aks6d@xxxxxxxxxxx>
• Re: Whether Bottom Halves run in Process context ?
  • From: Bernhard Walle <bernhard.walle@xxxxxx>
• Is it possible to trace routing socket messages going from a kernel to a daemon ... ??
  • From: Shriek <shriek.007@xxxxxxxxx>
• Bound Hardware with TTY Driver
  • From: Ulises <uarcidiacono@xxxxxxxxx>
• Whether Bottom Halves run in Process context ?
  • From: "Madhukar" <madhukar.mythri@xxxxxxxxx>
• RE: Relation between free() and remove_vm_struct()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Relation between free() and remove_vm_struct()
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: waitpid(2) and CLONE_THREAD
  • From: Sergey Dolgov <solkaa@xxxxxxxxx>
• Re: waitpid(2) and CLONE_THREAD
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• "time <apps>", is it the right thing to do to measure timing latency?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: what is mean about __builtin_constant_p()?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• waitpid(2) and CLONE_THREAD
  • From: Sergey Dolgov <solkaa@xxxxxxxxx>
• Relation between free() and remove_vm_struct()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Relation between free() and remove_vm_struct()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: Relation between free() and remove_vm_struct()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: regarding process segment in kernel
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Fwd: /proc/pid/cmdline question
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• regarding process segment in kernel
  • From: "suman adak" <gnusuman@xxxxxxxxx>
• what is mean about __builtin_constant_p()?
  • From: "liang yuanen" <linux.kernel.liang@xxxxxxxxx>
• Re: /proc/pid/cmdline question
  • From: Jim Bauer <jfbauer@xxxxxxxxxxx>
• Re: WhiteWabbit In Wonderland
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• WhiteWabbit In Wonderland
  • From: WhiteWabbit In Wonderland <bluewire@xxxxxxxxx>
• I2C support - 'built-in' VS dynamic modules
  • From: "Drasko Draskovic" <drasko.draskovic@xxxxxxxxx>
• /proc/pid/cmdline question
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• Re: TTY Driver Vs. UART Driver
  • From: Alex Parra <aparra@xxxxxxxx>
• Re: TTY Driver Vs. UART Driver
  • From: Greg KH <greg@xxxxxxxxx>
• TTY Driver Vs. UART Driver
  • From: Ulises <uarcidiacono@xxxxxxxxx>
• Re: time slice calculation
  • From: Erich Focht <efocht@xxxxxxxxxxxx>
• time slice calculation
  • From: "Tharindu Rukshan Bamunuarachchi" <tharindunix@xxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: "Manu Garg" <manugarg@xxxxxxxxx>
• AMBA magic numbers
  • From: "Drasko Draskovic" <drasko.draskovic@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• Re: learning proc read write
  • From: "Keppler Alecrim" <alecrim@xxxxxxxxx>
• Re: About Slab Allocator
  • From: Mauricio Lin <mauriciolin2000@xxxxxxxxxxxx>
• call trace {.text.lock.spinlock+14}
  • From: Erich Focht <efocht@xxxxxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: NAHieu <nahieu@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• processors
  • From: "Proyecto Kernel Investigacion" <proyecto.kernel@xxxxxxxxx>
• Fwd: Kernel Thread and Kernel Module
  • From: "Anand H. Krishnan" <anandhkrishnan@xxxxxxxxx>
• Re: About Slab Allocator
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: NAHieu <nahieu@xxxxxxxxx>
• Re: About Slab Allocator
  • From: "Kuncoro Irawan" <timeshuang@xxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• Re: how to install grub to hard disk?
  • From: David Lee <live4thee@xxxxxxxxx>
• RE: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: "Abhijit Pawar" <apawar@xxxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: Hal <hal.ashburner@xxxxxxxxx>
• Booting of SUSE 10.1
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• Re: hrtimer example code
  • From: Bernhard Walle <bernhard.walle@xxxxxx>
• Re: hrtimer example code
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: how to install grub to hard disk?
  • From: "Min-Hua Chen" <orca.chen@xxxxxxxxx>
• Re: how to install grub to hard disk?
  • From: David Lee <live4thee@xxxxxxxxx>
• how to install grub to hard disk?
  • From: "Min-Hua Chen" <orca.chen@xxxxxxxxx>
• acess permission in vm_area_struct
  • From: "Manoj Awasthi" <lkml.manoj@xxxxxxxxx>
• Fwd: learning proc read write
  • From: "Manoj Awasthi" <lkml.manoj@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: Alan Shieh <ashieh@xxxxxxxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: Alan Shieh <ashieh@xxxxxxxxxxxxxx>
• Re: learning proc read write
  • From: "Keppler Alecrim" <alecrim@xxxxxxxxx>
• About Slab Allocator
  • From: Mauricio Lin <mauriciolin2000@xxxxxxxxxxxx>
• learning proc read write
  • From: "Keppler Alecrim" <alecrim@xxxxxxxxx>
• Re: VGER.KERNEL.ORG
  • From: cRaig <treehead@xxxxxxxxx>
• unknown host
  • From: "nicola" <nicola@xxxxxxxxxxxxxxxxxx>
• Re: how to debug a driver remotely?
  • From: "Alexandr Lebedev" <a.lebede@xxxxxxxxx>
• Re: has a good book about linux fs subsystem?
  • From: "arshad hussain" <arshad.super@xxxxxxxxx>
• VGER.KERNEL.ORG
  • From: "Kaushal Shriyan" <kaushalshriyan@xxxxxxxxx>
• how to debug a driver remotely?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: has a good book about linux fs subsystem?
  • From: Rahul Iyer <idlisambar@xxxxxxxxx>
• Re: has a good book about linux fs subsystem?
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• kernel panic question
  • From: "Bizhan Gholikhamseh \(bgholikh\)" <bgholikh@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: Donald Becker <becker@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: platform_device question
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Problem : flags in the .config file.
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: platform_device question
  • From: "Drasko Draskovic" <drasko.draskovic@xxxxxxxxx>
• Re: platform_device question
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• hrtimer example code
  • From: "Alejandro Parra Briones" <aparra@xxxxxxxx>
• Re: has a good book about linux fs subsystem?
  • From: Vincent Thomasset <vincent.thomasset@xxxxxxxxx>
• Re: platform_device question
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Problem : flags in the .config file.
  • From: "Swanand Shende" <swanandshende@xxxxxxxxxxxxxx>
• has a good book about linux fs subsystem?
  • From: "liang yuanen" <linux.kernel.liang@xxxxxxxxx>
• Re: ioremap addresses
  • From: "Rahul Iyer" <idlisambar@xxxxxxxxx>
• Re: ioremap addresses
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: "Rahul Iyer" <idlisambar@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: ioremap addresses
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: coaxing objdump to give useful offsets
  • From: "Anand H. Krishnan" <anandhkrishnan@xxxxxxxxx>
• Re: setting up a cross compilation environment in x86_64
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: ioremap addresses
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: ioremap addresses
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: ioremap addresses
  • From: Rahul Iyer <idlisambar@xxxxxxxxx>
• setting up a cross compilation environment in x86_64
  • From: "Om." <om.turyx@xxxxxxxxx>
• *** Warning: "hrtimer_start" ... undefined
  • From: Alex Parra <aparra@xxxxxxxx>
• Re: Re: coaxing objdump to give useful offsets
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: ide disk driver
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• Re: ioremap addresses
  • From: Sebastian Haas <haas@xxxxxxxxxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• Re: ioremap addresses
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: ioremap addresses
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: ioremap addresses
  • From: bora.sahin@xxxxxxxxxxx
• Locks for reading dentry->d_inode->i_uid?
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: RTAI use in industry?
  • From: Bernhard Walle <bernhard.walle@xxxxxx>
• Re: Re: coaxing objdump to give useful offsets
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: ioremap addresses
  • From: Sebastian Haas <haas@xxxxxxxxxxxxxxxx>
• Re: Beginning to code
  • From: "Mouhammad Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Issuing BIOS interrupts in Linux
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Beginning to code
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• RTAI use in industry?
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Beginning to code
  • From: "Kaushal Shriyan" <kaushalshriyan@xxxxxxxxx>
• Re: coaxing objdump to give useful offsets
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: Issuing BIOS interrupts in Linux
  • From: "David H. Lynch Jr." <dhlii@xxxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: RE: How to debug a daemon during its initialization :: gdb
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Totally confused about kmap, highmem, and VM in general
  • From: "Chris Littell" <chris.littell@xxxxxxxxx>
• Re: coaxing objdump to give useful offsets
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: Alan Shieh <ashieh@xxxxxxxxxxxxxx>
• RE: How to debug a daemon during its initialization :: gdb
  • From: "Mohapatra, Hemant" <Hemant.Mohapatra@xxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: "Manu Garg" <manugarg@xxxxxxxxx>
• How to debug a daemon during its initialization :: gdb
  • From: Shriek <shriek.007@xxxxxxxxx>
• ioremap addresses
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: Device driver registratation problem
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: How can DMA help CPU to do other useful work when DMA is accessing memory?
  • From: "Mouhammad Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: How can DMA help CPU to do other useful work when DMA is accessing memory?
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: Univeral Protocol Driver (using UNDI) in Linux
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Kernel Thread and Kernel Module
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Stat in kernel space
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: Stat in kernel space
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• How can DMA help CPU to do other useful work when DMA is accessing memory?
  • From: "Chandrashekar MC" <mc.chandrashekar@xxxxxxxxx>
• RE: Stat in kernel space
  • From: "Mohapatra, Hemant" <Hemant.Mohapatra@xxxxxxx>
• coaxing objdump to give useful offsets
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: Stat in kernel space
  • From: "Avinash Ramanath" <avinashr@xxxxxxxxx>
• Stat in kernel space
  • From: "Avinash Ramanath" <avinashr@xxxxxxxxx>
• Re: Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: [Fwd: Re: pci_register_driver question(s)]
  • From: Jeffry Molanus <gila@xxxxxxx>
• [Fwd: Re: pci_register_driver question(s)]
  • From: Jeffry Molanus <gila@xxxxxxx>
• Re: pci_register_driver question(s)
  • From: Bernhard Walle <bernhard.walle@xxxxxx>
• pci_register_driver question(s)
  • From: Jeffry Molanus <gila@xxxxxxx>
• Re: Zeroing data blocks
  • From: Ian Stirling <ian.stirling@xxxxxxxxxxxxxx>
• Re: Zeroing data blocks
  • From: "Avinash Ramanath" <avinashr@xxxxxxxxx>
• Re: Issuing BIOS interrupts in Linux
  • From: "Nilesh Agrawal" <nilesh.agrawal@xxxxxxxxx>
• Re: Issuing BIOS interrupts in Linux
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Issuing BIOS interrupts in Linux
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: Issuing BIOS interrupts in Linux
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Totally confused about kmap, highmem, and VM in general
  • From: borasahin@xxxxxxxxxxx
• LVM, drive mapper internals
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: Zeroing data blocks
  • From: "Avinash Ramanath" <avinashr@xxxxxxxxx>
• Kernel Thread and Kernel Module
  • From: Dinesh Ahuja <mdlinux7@xxxxxxxxxxx>
• Re: Totally confused about kmap, highmem, and VM in general
  • From: Patrick Toomey <ptoomey3@xxxxxxxxxxx>
• Re: Totally confused about kmap, highmem, and VM in general
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: Issuing BIOS interrupts in Linux
  • From: Rahul Iyer <idlisambar@xxxxxxxxx>
• Re: pci_resource_flags()
  • From: Greg KH <greg@xxxxxxxxx>
• Re: pci_resource_flags()
  • From: "Myrto Zehnder" <myrto.zehnder@xxxxxxxxx>
• page table tracing
  • From: "Linux Learner" <learner.kernel@xxxxxxxxx>
• Totally confused about kmap, highmem, and VM in general
  • From: "Patrick Toomey" <ptoomey3@xxxxxxxxxxx>
• Re: Device probing
  • From: Greg KH <greg@xxxxxxxxx>
• Article Announcement - Sysenter Based System Call Mechanism in Linux 2.6
  • From: "Manu Garg" <manugarg@xxxxxxxxx>
• Re: ide disk driver
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• ide disk driver
  • From: "Bahadir Balban" <bilgehan.balban@xxxxxxxxx>
• Re: Allocation of Kernel stack
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Issuing BIOS interrupts in Linux
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Device probing
  • From: Makrydakis Giannhs <makryd@xxxxxxxxxx>
• ioctl() hangs in lite5200b FEC driver
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Allocation of Kernel stack
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: Re: Re: Regarding the gfp mask "GFP_NOFS"
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Query regarding interrupts on a dual core machine
  • From: "Ranjan Sinha" <rnjn.sinha@xxxxxxxxx>
• How to get rid of modpost "undefined" warning ?
  • From: "Ranger, Jean-Marc" <jeanmarc.ranger@xxxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: Rahul Iyer <idlisambar@xxxxxxxxx>
• Re: Reentrant code / Critical section / Atomic Section
  • From: Rahul Iyer <idlisambar@xxxxxxxxx>
• Re: Help
  • From: Rahul Iyer <idlisambar@xxxxxxxxx>
• Re: error inserting module.
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: pci_resource_flags()
  • From: Greg KH <greg@xxxxxxxxx>
• Re: SPI Flash
  • From: Greg KH <greg@xxxxxxxxx>
• Re: error inserting module.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: hi
  • From: Balaji <balajirrao@xxxxxxxxx>
• error inserting module.
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• SPI Flash
  • From: Rizvan <rizzkhan@xxxxxxxxx>
• Re: Help
  • From: Rizvan <rizzkhan@xxxxxxxxx>
• Re: Help
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• pci_resource_flags()
  • From: "Myrto Zehnder" <myrto.zehnder@xxxxxxxxx>
• Help
  • From: Deepak Pandey <deepak.pandey@xxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: Rajendra <rpm@xxxxxxxxxxxxx>
• Reentrant code / Critical section / Atomic Section
  • From: "Miguel Angel Alvarez" <ma.alvarez@xxxxxx>
• Re: Reentrant code / Critical section / Atomic Section
  • From: "Miguel Angel Alvarez" <ma.alvarez@xxxxxx>
• [question] rwsem status
  • From: Frederik Deweerdt <deweerdt@xxxxxxx>
• Re: Why "high memory" in x86?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Reentrant code / Critical section / Atomic Section
  • From: "Manoj Awasthi" <lkml.manoj@xxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• Setting kernel config variables
  • From: Richard Wolf <rwolf@xxxxxxxxxxxxxxxxx>
• Reentrant code / Critical section / Atomic Section
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: Regarding the gfp mask "GFP_NOFS"
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: Rajendra <rpm@xxxxxxxxxxxxx>
• tcp_tw_recycle and tcp_tw_reuse
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• Re: Query regarding interrupts on a dual core machine
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Greg KH talks about Kernelnewbies
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Network card driver compilation problem
  • From: Greg KH <greg@xxxxxxxxx>
• RE: Query regarding interrupts on a dual core machine
  • From: "Mohapatra, Hemant" <Hemant.Mohapatra@xxxxxxx>
• Re: Why "high memory" in x86?
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• Re: Regarding the gfp mask "GFP_NOFS"
  • From: Jiri Kosina <jikos@xxxxxxxx>
• Network card driver compilation problem
  • From: Ashok Sharma <aks6d@xxxxxxxxxxx>
• Re: Scheduling of fork()ed process
  • From: Jiri Kosina <jikos@xxxxxxxx>
• Re: Re: Regarding the gfp mask "GFP_NOFS"
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: RE: binfmt_elf.o as loadable module in 2.4.20
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: Regarding the gfp mask "GFP_NOFS"
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: down() and down_interruptible( ) difference
  • From: "Miguel Angel Alvarez" <ma.alvarez@xxxxxx>
• Re: down() and down_interruptible( ) difference
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• down() and down_interruptible( ) difference
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: Query regarding interrupts on a dual core machine
  • From: "Ranjan Sinha" <rnjn.sinha@xxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: Rajendra <rpm@xxxxxxxxxxxxx>
• Re: Query regarding interrupts on a dual core machine
  • From: "Ranjan Sinha" <rnjn.sinha@xxxxxxxxx>
• Re: Query regarding interrupts on a dual core machine
  • From: "Usman S. Ansari" <uansari@xxxxxxxxx>
• Re: Query regarding interrupts on a dual core machine
  • From: "Usman S. Ansari" <uansari@xxxxxxxxx>
• RE: binfmt_elf.o as loadable module in 2.4.20
  • From: <panthini.pandit@xxxxxxxxx>
• Re: Query regarding interrupts on a dual core machine
  • From: "Ranjan Sinha" <rnjn.sinha@xxxxxxxxx>
• Re: DEBUGFUNC messages in the e1000 driver
  • From: harsha srinath <harsha@xxxxxxx>
• DEBUGFUNC messages in the e1000 driver
  • From: harsha srinath <harsha@xxxxxxx>
• Re: Writing to file
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Address mapping for pci driver
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Scheduling of fork()ed process
  • From: "Daniel de Angelis Cordeiro" <dcordeiro@xxxxxxxxx>
• RE: Writing to file
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• Writing to file
  • From: "Rajesh Mahajan" <rajeshmahajan09@xxxxxxxxx>
• Re: Address mapping for pci driver
  • From: Bernhard Walle <bernhard.walle@xxxxxx>
• Address mapping for pci driver
  • From: "Thanh Tran" <ttran@xxxxxxxxxxxxx>
• Re: binfmt_elf.o as loadable module in 2.4.20
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Regarding the gfp mask "GFP_NOFS"
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• .text.lock.ip_output
  • From: "Linux Learner" <learner.kernel@xxxxxxxxx>
• Re: lsmod Used count
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: lsmod Used count
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Query regarding interrupts on a dual core machine
  • From: "Fabio Guarneri" <fabioguarneri@xxxxxxxxx>
• Re: Linux and Coldfire
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: lsmod Used count
  • From: Satish <satishr@xxxxxxxxx>
• Re: Single physical memory location has multiple virtual addresses?
  • From: Rajendra <rpm@xxxxxxxxxxxxx>
• Linux and Coldfire
  • From: "Miguel Angel Alvarez" <ma.alvarez@xxxxxx>
• Query regarding interrupts on a dual core machine
  • From: "Ranjan Sinha" <rnjn.sinha@xxxxxxxxx>
• the /proc/meminfo statistics
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: Rajendra <rpm@xxxxxxxxxxxxx>
• Re: Single physical memory location has multiple virtual addresses?
  • From: Rajendra <rpm@xxxxxxxxxxxxx>
• Re: lsmod Used count
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: Christophe Lucas <clucas@xxxxxxxxxxxxx>
• Re: Why "high memory" in x86?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Single physical memory location has multiple virtual addresses?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Why "high memory" in x86?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Regarding the gfp mask "GFP_NOFS"
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• binfmt_elf.o as loadable module in 2.4.20
  • From: <panthini.pandit@xxxxxxxxx>
• Re: spin_lock_irqsave query
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• spin_lock_irqsave query
  • From: "Linux Learner" <learner.kernel@xxxxxxxxx>
• Re: Linux Source Code Exploration - Help
  • From: Tim Bird <tim.bird@xxxxxxxxxxx>
• Re: lsmod Used count
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• Re: lsmod Used count
  • From: "Anupam Kapoor" <anupam.kapoor@xxxxxxxxx>
• Re: IP pkt forwarding question.
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• lsmod Used count
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: IP pkt forwarding question.
  • From: "Sandeep Mailk" <malik.mca@xxxxxxxxx>
• IP pkt forwarding question.
  • From: "Ming Chen" <tomingchen@xxxxxxxxx>
• Re: Kernelnewbies wiki update
  • From: "Om." <om.turyx@xxxxxxxxx>
• Kernelnewbies wiki update
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: BUG() function
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: Does cdrecord work with DVD Writers?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Does cdrecord work with DVD Writers?
  • From: Hari Prashanth <annabase@xxxxxxxxxxx>
• BUG() function
  • From: "liang yuanen" <linux.kernel.liang@xxxxxxxxx>
• Re: Does cdrecord work with DVD Writers?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Does cdrecord work with DVD Writers?
  • From: Hari Prashanth <hari.prashanth@xxxxxxxxxxx>
• Re: what mean vm_file in vm_area_struct structure?
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• what mean vm_file in vm_area_struct structure?
  • From: "liang yuanen" <linux.kernel.liang@xxxxxxxxx>
• Re: Linux Source Code Exploration - Help
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: Linux Source Code Exploration - Help
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: Logic3 USB Dance Mat
  • From: "Alan Jones" <skyphyr@xxxxxxxxx>
• Re: Logic3 USB Dance Mat
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Tracing IPv6 packets
  • From: Jay Cliburn <jacliburn@xxxxxxxxxxxxx>
• Re: Ip address notation
  • From: Paul Dickson <paul@xxxxxxxxxxxxxxxxx>
• Ip address notation
  • From: "Rajesh Mahajan" <rajeshmahajan09@xxxxxxxxx>
• Re:kernel programming - big endian and little endian issues
  • From: "Miguel Angel Alvarez" <ma.alvarez@xxxxxx>
• Re: Device driver registratation problem
  • From: "Vaibhav Nipunage" <linuxsyspro@xxxxxxxxx>
• SYSTEM_VECTOR and use
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: kernel programming - big endian and little endian issues
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Logic3 USB Dance Mat
  • From: "Alan Jones" <skyphyr@xxxxxxxxx>
• Re: kernel programming - big endian and little endian issues
  • From: Martin Röhricht <ml@xxxxxxxxxxx>
• Re: Re: unhandled page fault
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• kernel programming - big endian and little endian issues
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• real time linux
  • From: "Miguel Angel Alvarez" <ma.alvarez@xxxxxx>
• Re: how to write kernel module in hp-ux
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: how to write kernel module in hp-ux
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: unhandled page fault
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Re: unhandled page fault
  • From: Christian Boon <c.boon@xxxxxxxxxxxxxxxxxxxx>
• Re: how to write kernel module in hp-ux
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• how to write kernel module in hp-ux
  • From: "hari krishnan" <p.harikrishnan22@xxxxxxxxx>
• Re: Re: unhandled page fault
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: request_region() Error
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: What can and can't be done in kernel-mode
  • From: Josef Sipek <jsipek@xxxxxxxxxxxxxxxxx>
• What can and can't be done in kernel-mode
  • From: Elad Lahav <elad_lahav@xxxxxxxxxxxxxxxxxxxxx>
• request_region() Error
  • From: Ulises <uarcidiacono@xxxxxxxxx>
• Re: unhandled page fault
  • From: Christian Boon <chris.boon@xxxxxxxxxx>
• Re: Tracing IPv6 packets
  • From: "Avinash Ramanath" <avinashr@xxxxxxxxx>
• Re: unhandled page fault
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Re: unhandled page fault
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: unhandled page fault
  • From: Christian Boon <c.boon@xxxxxxxxxxxxxxxxxxxx>
• Re: Spinlock on single-processor machines
  • From: "Om." <om.turyx@xxxxxxxxx>
• unhandled page fault
  • From: Christian Boon <c.boon@xxxxxxxxxxxxxxxxxxxx>
• Re: Spinlock on single-processor machines
  • From: "s prashant" <sprashant16@xxxxxxxxx>
• Re: setsockopt - SO_REUSEADDR
  • From: JuanJo Ciarlante <jjo@xxxxxxxxxxxxxx>
• Re: setsockopt - SO_REUSEADDR
  • From: JuanJo Ciarlante <jjo@xxxxxxxxxxxxxx>
• Re: setsockopt - SO_REUSEADDR
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• setsockopt - SO_REUSEADDR
  • From: Chinmaya Mishra <chinmaya4@xxxxxxxxx>
• setsockopt - SO_REUSEADDR
  • From: Chinmaya Mishra <chinmaya4@xxxxxxxxx>
• Re: File Descriptors Limit
  • From: Hayim Shaul <hayim@xxxxxxxxxxxxxx>
• Re: Device driver registratation problem
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Tracing IPv6 packets
  • From: mohanlal jangir <mohanlal@xxxxxxxxxxx>
• Re: Device driver registratation problem
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Tracing IPv6 packets
  • From: Jay Cliburn <jacliburn@xxxxxxxxxxxxx>
• Re: Spinlock on single-processor machines
  • From: "Grob Team" <grobteam@xxxxxxxxx>
• Re: Device driver registratation problem
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Linux Source Code Exploration - Help
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Logic3 USB Dance Mat
  • From: "Alan Jones" <skyphyr@xxxxxxxxx>
• Device driver registratation problem
  • From: "Vaibhav Nipunage" <linuxsyspro@xxxxxxxxx>
• Re: Linux Source Code Exploration - Help
  • From: Hari Prashanth <hari.prashanth@xxxxxxxxxxx>
• Re: Linux Source Code Exploration - Help
  • From: Hari Prashanth <annabase@xxxxxxxxxxx>
• Re: Linux Source Code Exploration - Help
  • From: "Alexandr Lebedev" <a.lebede@xxxxxxxxx>
• File Descriptors Limit
  • From: Jeronimo Zucco <jczucco@xxxxxx>
• Linux Source Code Exploration - Help
  • From: Hari Prashanth <annabase@xxxxxxxxxxx>
• 2.6.14 not detecting keyboard on boot up!
  • From: "Rahul K" <rahulshrikar@xxxxxxxxx>
• Re: Spinlock on single-processor machines
  • From: "s prashant" <sprashant16@xxxxxxxxx>
• Re: virtual memory size reduction from 4GB to 512MB
  • From: "s prashant" <sprashant16@xxxxxxxxx>
• Re: Spinlock on single-processor machines
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Re: Re: counting swapped out pages from certain task
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Spinlock on single-processor machines
  • From: "Grob Team" <grobteam@xxxxxxxxx>
• Re: counting swapped out pages from certain task
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: kernel synchronization mechanisms in userspace ??
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: virtual memory size reduction from 4GB to 512MB
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: page locking from application
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: page locking from application
  • From: Mark Hounschell <dmarkh@xxxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• kernel synchronization mechanisms in userspace ??
  • From: arvind k <arvind_000@xxxxxxxxx>
• virtual memory size reduction from 4GB to 512MB
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: kthread_create() vs kernel_thread()
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• counting swapped out pages from certain task
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• kthread_create() vs kernel_thread()
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Rene Herman <rene.herman@xxxxxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Johannes Weiner <hnazfoo@xxxxxxxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: pack in structure or not?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Johannes Weiner <hnazfoo@xxxxxxxxxxxxxx>
• Re: pack in structure or not?
  • From: Johannes Weiner <hnazfoo@xxxxxxxxxxxxxx>
• Re: pack in structure or not?
  • From: Paul Drynoff <pauldrynoff@xxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: pack in structure or not?
  • From: Johannes Weiner <hnazfoo@xxxxxxxxxxxxxx>
• pack in structure or not?
  • From: Paul Drynoff <pauldrynoff@xxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Johannes Weiner <hnazfoo@xxxxxxxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Johannes Weiner <hnazfoo@xxxxxxxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: Integer Division In Module
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: altering CFLAGS in kbuild (makefile)?
  • From: "Om." <om.turyx@xxxxxxxxx>
• altering CFLAGS in kbuild (makefile)?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Faster kernel boot
  • From: Jeronimo Zucco <jczucco@xxxxxx>
• Re: Faster kernel boot
  • From: Mounir Bakkali <mounir.bakkali@xxxxxxxxx>
• Re: Faster kernel boot
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Faster kernel boot
  • From: Mounir Bakkali <mounir.bakkali@xxxxxxxxx>
• Re: Faster kernel boot
  • From: Mounir Bakkali <mounir.bakkali@xxxxxxxxx>
• Re: page locking from application
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Faster kernel boot
  • From: Mounir Bakkali <mounir.bakkali@xxxxxxxxx>
• Re: Faster kernel boot
  • From: William J Beksi <wjbeksi@xxxxxxxxxxxxxxxxxxxxx>
• Faster kernel boot
  • From: Mounir Bakkali <mounir.bakkali@xxxxxxxxx>
• Re: page locking from application
  • From: Jiri Kosina <jikos@xxxxxxxx>
• Re: read_proc 4k limit help
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Okay... there is something wrong with the mailing list
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• read_proc 4k limit help
  • From: "vinay salotagi" <yogi.penguin@xxxxxxxxx>
• Re: Integer Division In Module
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Re: Integer Division In Module
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Re: page locking from application
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: Integer Division In Module
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: page locking from application
  • From: Jiri Kosina <jikos@xxxxxxxx>
• Re: Integer Division In Module
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Integer Division In Module
  • From: "Talib Alim" <talibalm@xxxxxxxxxxx>
• Re: gbb for threaded programs
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Okay... there is something wrong with the mailing list
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: page locking from application
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: page locking from application
  • From: Mark Hounschell <markh@xxxxxxxxxx>
• Re: gbb for threaded programs
  • From: Kunal Parmar <kunal.parmar@xxxxxxxxxx>
• Re: Okay... there is something wrong with the mailing list
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: Can we not gdb investigate inline functions
  • From: Kunal Parmar <kunal.parmar@xxxxxxxxxx>
• Re: Okay... there is something wrong with the mailing list
  • From: "Ashok kumar" <ashokmudalister@xxxxxxxxx>
• Re: gbb for threaded programs
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: page locking from application
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: gbb for threaded programs
  • From: Kunal Parmar <kunal.parmar@xxxxxxxxxx>
• Re: Okay... there is something wrong with the mailing list
  • From: "Irfan Habib" <irfan.habib@xxxxxxxxx>
• Re: gbb for threaded programs
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: page locking from application
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Okay... there is something wrong with the mailing list
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• page locking from application
  • From: "Linux Learner" <learner.kernel@xxxxxxxxx>
• Okay... there is something wrong with the mailing list
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• gbb for threaded programs
  • From: "Irfan Habib" <irfan.habib@xxxxxxxxx>
• Re: Can we not gdb investigate inline functions
  • From: mohanlal jangir <mohanlal@xxxxxxxxxxx>
• Re: Can we not gdb investigate inline functions
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• Re: Can we not gdb investigate inline functions
  • From: "Shrikanth Kamath" <shrikanth07@xxxxxxxxx>
• Re: Can we not gdb investigate inline functions
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• Can we not gdb investigate inline functions
  • From: Shriek <shriek.007@xxxxxxxxx>
• Re: down() function and assembly implementation
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: down() function and assembly implementation
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: down() function and assembly implementation
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: Help regarding initrd
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: down() function and assembly implementation
  • From: "Om." <om.turyx@xxxxxxxxx>
• RE: Help regarding initrd
  • From: "Mohapatra, Hemant" <Hemant.Mohapatra@xxxxxxx>
• Re: overhead of process/task_struct in POSIX threads- why?
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• Re: Help regarding initrd
  • From: "Morphy Zhores" <morphy.zhores@xxxxxxxxx>
• PHY Howto ?
  • From: "David H. Lynch Jr." <dhlii@xxxxxxxxxx>
• down() function and assembly implementation
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: loff_t *offp in read and write
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: overhead of process/task_struct in POSIX threads- why?
  • From: Mark Hounschell <markh@xxxxxxxxxx>
• Re: Help regarding initrd
  • From: "Fabio Guarneri" <fabioguarneri@xxxxxxxxx>
• Re: Help regarding initrd
  • From: "Fabio Guarneri" <fabioguarneri@xxxxxxxxx>
• Re: Getting some information inside task_struct from a user application?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Getting some information inside task_struct from a user application?
  • From: "Hsin-An Chen@NTHU" <g946301@xxxxxxxxxxxxxx>
• base address of PGD
  • From: "Linux Learner" <learner.kernel@xxxxxxxxx>
• Re: GDB terminating with " ...xmalloc: out of virtual memory"
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Reg. International Conference on GPLv3
  • From: "Ashok kumar" <ashokmudalister@xxxxxxxxx>
• Reg. International Conference on GPLv3
  • From: "Ashok kumar" <ashokmudalister@xxxxxxxxx>
• Re: Re: overhead of process/task_struct in POSIX threads- why?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• loff_t *offp in read and write
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: overhead of process/task_struct in POSIX threads- why?
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: overhead of process/task_struct in POSIX threads- why?
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: overhead of process/task_struct in POSIX threads- why?
  • From: mohanlal jangir <mohanlal@xxxxxxxxxxx>
• Query regarding platform data
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: overhead of process/task_struct in POSIX threads- why?
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• RE: Help regarding initrd
  • From: "Mohapatra, Hemant" <Hemant.Mohapatra@xxxxxxx>
• Help regarding initrd
  • From: "Morphy Zhores" <morphy.zhores@xxxxxxxxx>
• overhead of process/task_struct in POSIX threads- why?
  • From: Parav Pandit <paravpandit@xxxxxxxxx>
• Re: Gettin own IP address thorugh ioctl in kernel space.
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Gettin own IP address thorugh ioctl in kernel space.
  • From: JuanJo Ciarlante <jjo@xxxxxxxxxxxxxx>
• Gettin own IP address thorugh ioctl in kernel space.
  • From: Chinmaya Mishra <chinmaya4@xxxxxxxxx>
• GDB terminating with " ...xmalloc: out of virtual memory"
  • From: Shriek <shriek.007@xxxxxxxxx>
• platform data
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Regarding MAL
  • From: "Sangameshwar Pujari" <Sangameshwar.Pujari@xxxxxxxxxxxx>
• Re: XML parser
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• RE: XML parser
  • From: "Mohapatra, Hemant" <Hemant.Mohapatra@xxxxxxx>
• XML parser
  • From: "Madhukar" <madhukar.mythri@xxxxxxxxx>
• Re: Free a list_head
  • From: "Om." <om.turyx@xxxxxxxxx>
• Fwd: Free a list_head
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• tcp_skb_cb flags and IPv4 TOS
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• tcp_skb_cb flags and rtt estimation
  • From: "Ritesh Kumar" <ritesh@xxxxxxxxxx>
• mmap in LDD3.
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Profiling and power management
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: ACPI_FUTURE_USAGE
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: kewlemer <kewlemer@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: kewlemer <kewlemer@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: kewlemer <kewlemer@xxxxxxxxx>
• inserting conntrack tuple
  • From: "Martin Schuhmacher" <broetchen25@xxxxxxx>
• skb allocation .
  • From: pankaj chauhan <chauhan_ait@xxxxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: kewlemer <kewlemer@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: Greg KH <greg@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: kewlemer <kewlemer@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: kewlemer <kewlemer@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: Greg KH <greg@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: Greg KH <greg@xxxxxxxxx>
• Re: E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: kewlemer <kewlemer@xxxxxxxxx>
• E1000's PSSTAT.SPEED (forced speed and duplex) Question
  • From: kewlemer <kewlemer@xxxxxxxxx>
• Re: Free a list_head
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Free a list_head
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: undefined symbol: __bad_udely (kernel modules)
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: undefined symbol: __bad_udely (kernel modules)
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: undefined symbol: __bad_udely (kernel modules)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• undefined symbol: __bad_udely (kernel modules)
  • From: "alfred hitch" <alfred.hitch@xxxxxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Mouhammad Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: f_pos passing as a fouth argument in read and write
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: f_pos passing as a fouth argument in read and write
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: undefined symbol: open (kernel modules)
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: f_pos passing as a fouth argument in read and write
  • From: "Om." <om.turyx@xxxxxxxxx>
• ACPI_FUTURE_USAGE
  • From: Rafał Bilski <rafalbilski@xxxxxxxxxx>
• RE: ioremap_nocache() returns 0xffffffff
  • From: "Muneeswaran P - TLS, Chennai" <muneeswaranp@xxxxxx>
• Re: merging of two memory regions-HOWTO
  • From: "Om." <om.turyx@xxxxxxxxx>
• how to find starting sector of a partition?
  • From: "Abid Younas" <abidyounas@xxxxxxxxx>
• Re: merging of two memory regions-HOWTO
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• merging of two memory regions-HOWTO
  • From: keshetti mahesh <k_mahesh85@xxxxxxxxxxx>
• Re: use of .owner field in fops for device drivers
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• phy howto
  • From: "David H. Lynch Jr." <dhlii@xxxxxxxxxx>
• Re: undefined symbol: open (kernel modules)
  • From: Greg KH <greg@xxxxxxxxx>
• undefined symbol: open (kernel modules)
  • From: "alfred hitch" <alfred.hitch@xxxxxxxxx>
• f_pos passing as a fouth argument in read and write
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• use of .owner field in fops for device drivers
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: Free a list_head
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Free a list_head
  • From: "Om." <om.turyx@xxxxxxxxx>
• RE: Free a list_head
  • From: "Mohapatra, Hemant" <Hemant.Mohapatra@xxxxxxx>
• Re: Free a list_head
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Free a list_head
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Free a list_head
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: Robin Holt <holt@xxxxxxx>
• Free a list_head
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: what is PCI to PCMCIA adaptor device name
  • From: "Simon Wu" <simonwu1@xxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: Chase Venters <chase.venters@xxxxxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: versions numbering confusion - regarding development & stable versions
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: versions numbering confusion - regarding development & stable versions
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: Simulating USB Unplug
  • From: Guennadi Liakhovetski <gl@xxxxxxxxx>
• versions numbering confusion - regarding development & stable versions
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• linkage errs ( inclusion order problem ? )
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Simulating USB Unplug
  • From: "Brian Cavagnolo" <brian@xxxxxxxxxxx>
• i8042 interrupt when booting
  • From: "John Que" <qwejohn@xxxxxxxxx>
• Re: Re: disable_irq() and local_disable_irq() : a quesion
  • From: "John Que" <qwejohn@xxxxxxxxx>
• Re: Zeroing data blocks
  • From: "Om." <om.turyx@xxxxxxxxx>
• RE: compilation problem
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• compilation problem
  • From: manish <rangankarmanish@xxxxxxxxx>
• Re: Zeroing data blocks
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Zeroing data blocks
  • From: "Avinash Ramanath" <avinashr@xxxxxxxxx>
• Re: Zeroing data blocks
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Zeroing data blocks
  • From: "Om.Turyx" <om.turyx@xxxxxxxxx>
• Re: Re: Zeroing data blocks
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: proc_mkdir
  • From: "Om.Turyx" <om.turyx@xxxxxxxxx>
• Re: Zeroing data blocks
  • From: "Avinash Ramanath" <avinashr@xxxxxxxxx>
• Re: proc_mkdir
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: proc_mkdir
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: proc_mkdir
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: proc_mkdir
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: Willy Tarreau <w@xxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: Willy Tarreau <w@xxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: Willy Tarreau <w@xxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: locking shared memory pages
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Re: Zeroing data blocks
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: Chase Venters <chase.venters@xxxxxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Automatic Kernel Bug Report
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: error during inserting module......invalid module format
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: Chase Venters <chase.venters@xxxxxxxxxxxx>
• RE: Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Zeroing data blocks
  • From: "Avinash Ramanath" <avinashr@xxxxxxxxx>
• Re: locking shared memory pages
  • From: "Om.Turyx" <om.turyx@xxxxxxxxx>
• Re: mem_map in NUMA -- where is it?
  • From: "Om.Turyx" <om.turyx@xxxxxxxxx>
• Re: Commenting out out_of_memory() function in __alloc_pages()
  • From: Robert Hancock <hancockr@xxxxxxx>
• ioremap_nocache() returns 0xffffffff
  • From: "Muneeswaran P - TLS, Chennai" <muneeswaranp@xxxxxx>
• Re: Re: disable_irq() and local_disable_irq() : a quesion
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• locking shared memory pages
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• mem_map in NUMA -- where is it?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: error during inserting module......invalid module format
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• error during inserting module......invalid module format
  • From: mayank rana <mayank_rana_it@xxxxxxxxxxx>
• Re: detect connected USB devices
  • From: Greg KH <greg@xxxxxxxxx>
• Commenting out out_of_memory() function in __alloc_pages()
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: detect connected USB devices
  • From: mgr@xxxxxxxxxxx
• Re: what is PCI to PCMCIA adaptor device name
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Ring 0 Protection ?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: detect attached devices
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: detect connected USB devices
  • From: Greg KH <greg@xxxxxxxxx>
• Re: detect connected USB devices
  • From: "George Zhim" <georgezhim@xxxxxxxxx>
• Re: disable_irq() and local_disable_irq() : a quesion
  • From: "John Que" <qwejohn@xxxxxxxxx>
• Re: Ring 0 Protection ?
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• what is PCI to PCMCIA adaptor device name
  • From: "Simon Wu" <simonwu1@xxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: "George Zhim" <georgezhim@xxxxxxxxx>
• Re: Ring 0 Protection ?
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• Re: Ring 0 Protection ?
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Re: struct cdev usage subtleties ?
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: detect attached devices
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: struct cdev usage subtleties ?
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Re: Ring 0 Protection ?
  • From: "Tharindu Rukshan Bamunuarachchi" <tharindub@xxxxxxxxx>
• struct cdev usage subtleties ?
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• detect attached devices
  • From: mgr@xxxxxxxxxxx
• Re: detect connected USB devices
  • From: Greg KH <greg@xxxxxxxxx>
• Re: proc_mkdir
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• detect connected USB devices
  • From: mgr@xxxxxxxxxxx
• Re: Ring 0 Protection ?
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• Re: Serial issue in 2.4 kernel
  • From: "lee nookx" <lnookx@xxxxxxxxxxxxxx>
• Re: Serial issue in 2.4 kernel
  • From: Jeronimo Zucco <jczucco@xxxxxx>
• Re: Problem reading file with O_DIRECT
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Daniel Drake <dsd@xxxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: Ring 0 Protection ?
  • From: "Tharindu Rukshan Bamunuarachchi" <tharindub@xxxxxxxxx>
• Re: /dev/mem contains physical memory addresses?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• /dev/mem contains physical memory addresses?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: Ring 0 Protection ?
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Re: Serial issue in 2.4 kernel
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Serial issue in 2.4 kernel
  • From: "lee nookx" <lnookx@xxxxxxxxxxxxxx>
• Re: Confusion regarding spin_lock_irqsave and spin_unlock_irqrestore.
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Confusion regarding spin_lock_irqsave and spin_unlock_irqrestore.
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Ring 0 Protection ?
  • From: "George Zhim" <georgezhim@xxxxxxxxx>
• Can someone elaborate how syncookies cause grief for mail relays
  • From: "Yusuf Goolamabbas" <yusufg@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Problem reading file with O_DIRECT
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Daniel Drake <dsd@xxxxxxxxxx>
• Re: Problem reading file with O_DIRECT
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Problem reading file with O_DIRECT
  • From: "Manisha Maheshwari" <maheshwari.manisha@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Problem reading file with O_DIRECT
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: proc_mkdir
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Daniel Drake <dsd@xxxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: disable_irq() and local_disable_irq() : a quesion
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Daniel Drake <dsd@xxxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• disable_irq() and local_disable_irq() : a quesion
  • From: "John Que" <qwejohn@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• proc_mkdir
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: Confusion regarding spin_lock_irqsave and spin_unlock_irqrestore.
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Confusion regarding spin_lock_irqsave and spin_unlock_irqrestore.
  • From: "Ranjan Sinha" <rnjn.sinha@xxxxxxxxx>
• Block layer strategy function
  • From: hans@xxxxxxxxx
• Re: Thread Context
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: change from bulk to interrupt endpoints
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Thread Context
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: data structure used in syscal and kernel thread
  • From: "Adrian - Razvan Deaconescu" <razvand@xxxxxxxxx>
• Re: Thread Context
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: data structure used in syscal and kernel thread
  • From: "Adrian - Razvan Deaconescu" <razvand@xxxxxxxxx>
• Thread Context
  • From: "Sikandar Khan" <sikandar032@xxxxxxxxx>
• Re: data structure used in syscal and kernel thread
  • From: "Adrian - Razvan Deaconescu" <razvand@xxxxxxxxx>
• Re: change from bulk to interrupt endpoints
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Greg KH <greg@xxxxxxxxx>
• Problem reading file with O_DIRECT
  • From: "Manisha Maheshwari" <maheshwari.manisha@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Greg KH <greg@xxxxxxxxx>
• Re: data structure used in syscal and kernel thread
  • From: "Om." <om.turyx@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: [OT] Re: Driver for Microsoft USB Fingerprint Reader
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: insmod question.
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Alon Bar-Lev <alon.barlev@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Daniel Bonekeeper" <thehazard@xxxxxxxxx>
• Re: USB device driver: change from bulk to int transfers
  • From: Greg KH <greg@xxxxxxxxx>
• [OT] Re: Driver for Microsoft USB Fingerprint Reader
  • From: Alistair John Strachan <s0348365@xxxxxxxxxxxx>
• USB device driver: change from bulk to int transfers
  • From: mgr@xxxxxxxxxxx
• Re: insmod question.
  • From: pankaj chauhan <chauhan_ait@xxxxxxxxxxx>
• change from bulk to interrupt endpoints
  • From: mgr@xxxxxxxxxxx
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Alon Bar-Lev <alon.barlev@xxxxxxxxx>
• Re: data structure used in syscal and kernel thread
  • From: "Om Narasimhan" <om.turyx@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Valdis.Kletnieks@xxxxxx
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: "Alon Bar-Lev" <alon.barlev@xxxxxxxxx>
• rdtscll and jiffies
  • From: "pradeep sawlani" <pradep@xxxxxxxxx>
• Re: Driver for Microsoft USB Fingerprint Reader
  • From: Daniel Drake <dsd@xxxxxxxxxx>
• Re: rdtscll and jiffies
  • From: "pradeep sawlani" <pradep@xxxxxxxxx>
• Re: insmod question.
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: data structure used in syscal and kernel thread
  • From: "Om Narasimhan" <om.turyx@xxxxxxxxx>
• Re: network prog qn...help!
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• data structure used in syscal and kernel thread
  • From: mzubair <mzubair173@xxxxxxxxx>
• Re: network prog qn...help!
  • From: "Rajesh Mahajan" <rajeshmahajan09@xxxxxxxxx>
• Re: what is MSI ? (apparently related to SMP and interrupts)
  • From: "Om Narasimhan" <om.turyx@xxxxxxxxx>
• [RFC] Network Transport Protocol - TCPXM
  • From: "Alan Menegotto" <macnish@xxxxxxxxx>
• Re: insmod question.
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: insmod question.
  • From: pankaj chauhan <chauhan_ait@xxxxxxxxxxx>
• Re: Linux Frame Buffer
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: insmod question.
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Linux Frame Buffer
  • From: manish <rangankarmanish@xxxxxxxxx>
• insmod question.
  • From: pankaj chauhan <chauhan_ait@xxxxxxxxxxx>
• network prog qn...help!
  • From: "Vivek Balakrishnan" <vivek.balakrishnan@xxxxxxxxx>
• Re: rdtscll and jiffies
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: suse linux 9.3 boot up problem
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• suse linux 9.3 boot up problem
  • From: "Muneeswaran P - TLS, Chennai" <muneeswaranp@xxxxxx>
• Re: context of init_module()
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: context of init_module()
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: context of init_module()
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: AW: accessing bios from kernel module
  • From: Seewer Philippe <philippe.seewer@xxxxxx>
• DMA buffers in >4G address space using ioremap?
  • From: "Michael Lilja" <ml@xxxxxxxxxxxx>
• Re: User-supplied stacks
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: issue about virt_to_page(addr) macro
  • From: "Manish Regmi" <regmi.manish@xxxxxxxxx>
• Re: rdtscll and jiffies
  • From: "Titus Chandramohan" <tituschandramohan@xxxxxxxxx>
• Re: issue about virt_to_page(addr) macro
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• context of init_module()
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: rdtscll and jiffies
  • From: "Om Narasimhan" <om.turyx@xxxxxxxxx>
• rdtscll and jiffies
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: rdtscll and jiffies
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: rdtscll and jiffies
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: Get all_bdevs from module?
  • From: "Carl Spalletta" <cspalletta@xxxxxxxxx>
• Re: AW: accessing bios from kernel module
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: issue about virt_to_page(addr) macro
  • From: Mauricio Lin <mauriciolin2000@xxxxxxxxxxxx>
• Re: Profiling and power management
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: accessing bios from kernel module
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: rdtscll and jiffies
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• accessing bios from kernel module
  • From: "Weber Matthias" <Matthias.Weber@xxxxxxxxxxxxxxxxxxxx>
• Re: rdtscll and jiffies
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Kernel module Makefile & a quick howto..
  • From: "Mark Harvey" <mark_harvey@xxxxxxxxxxxx>
• Re: Get all_bdevs from module?
  • From: Carl Spalletta <cspalletta@xxxxxxxxx>
• issue about virt_to_page(addr) macro
  • From: Mauricio Lin <mauriciolin2000@xxxxxxxxxxxx>
• Re: Profiling and power management
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Profiling and power management
  • From: Elad Lahav <elad_lahav@xxxxxxxxxxxxxxxxxxxxx>
• NIC failing to transmit
  • From: Hayim Shaul <hayim@xxxxxxxxxxxxxx>
• rdtscll and jiffies
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• RE: why Does Kernel Module should not do Floating Point operation?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• RE: why Does Kernel Module should not do Floating Point operation?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• how to export a symbol from data section
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• RE: why Does Kernel Module should not do Floating Point operation?
  • From: "Manjunath_Naik" <Manjunath_Naik@xxxxxxxxxx>
• Re: what is MSI ? (apparently related to SMP and interrupts)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: what is MSI ? (apparently related to SMP and interrupts)
  • From: Greg KH <greg@xxxxxxxxx>
• what is MSI ? (apparently related to SMP and interrupts)
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: why Does Kernel Module should not do Floating Point operation?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• RE: why Does Kernel Module should not do Floating Point operation?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: why Does Kernel Module should not do Floating Point operation?
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• Re: why Does Kernel Module should not do Floating Point operation?
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• RE: why Does Kernel Module should not do Floating Point operation?
  • From: "Manjunath_Naik" <Manjunath_Naik@xxxxxxxxxx>
• Re: why Does Kernel Module should not do Floating Point operation?
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• RE: why Does Kernel Module should not do Floating Point operation?
  • From: "Manjunath_Naik" <Manjunath_Naik@xxxxxxxxxx>
• Re: why Does Kernel Module should not do Floating Point operation?
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• why Does Kernel Module should not do Floating Point operation?
  • From: "Manjunath_Naik" <Manjunath_Naik@xxxxxxxxxx>
• Doubts regarding Interrupts
  • From: <kaustav.majumdar@xxxxxxxxx>
• Re: Expertise required:USB bulk-throughput and memory leak detection
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Expertise required:USB bulk-throughput and memory leak detection
  • From: <bhuvan.kumarmital@xxxxxxxxx>
• Expertise required:USB bulk-throughput and memory leak detection
  • From: <bhuvan.kumarmital@xxxxxxxxx>
• New Open Source Project - LEO-sysgen
  • From: "Pranav Sahasrabudhe" <pps.sub@xxxxxxxxx>
• Re: Example "short" of LDD / Parallel port
  • From: Clemens Buchacher <drizzd@xxxxxx>
• Re: Example "short" of LDD / Parallel port
  • From: "Thiago Figueredo Cardoso" <tfcardoso@xxxxxxxxxxxx>
• Re: How to make 2 kernels of same version coexist?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Get all_bdevs from module?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: How to make 2 kernels of same version coexist?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: How to make 2 kernels of same version coexist?
  • From: "Jinesh K J" <jineshkj.newsletters@xxxxxxxxx>
• How to make 2 kernels of same version coexist?
  • From: <bhuvan.kumarmital@xxxxxxxxx>
• Get all_bdevs from module?
  • From: NAHieu <nahieu@xxxxxxxxx>
• Re: Restrict memory region to some modules
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: unresolved symbol "irq_desc"
  • From: Mark Hounschell <markh@xxxxxxxxxx>
• Restrict memory region to some modules
  • From: Paolo <valerio.paolo@xxxxxxxxx>
• Reg: Route Cache hash key in Linux Network Code
  • From: "Pranjal Kumar Dutta" <pranjalkumardutta@xxxxxxxxx>
• Re: unresolved symbol "irq_desc"
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Re: Process memory
  • From: "Titus Chandramohan" <tituschandramohan@xxxxxxxxx>
• unresolved symbol "irq_desc"
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>