Linux Kernel Newbies

• Thread Index

• Re: How to disable the CPU cache?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• no init found
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• RE: printk -- unable to print messages
  • From: "Sangameshwar Pujari" <Sangameshwar.Pujari@xxxxxxxxxxxx>
• RE: printk -- unable to print messages
  • From: <krishna.vamsi@xxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: how to prevent flushing of routing cache in linux FC3
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: persistent naming in initrd
  • From: Greg KH <greg@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: Bernhard Walle <bernhard.walle@xxxxxx>
• persistent naming in initrd
  • From: "Vikas Aggarwal" <vik.reck@xxxxxxxxx>
• Re: Re: __builtin_return_address(0) and schedule()
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: "Yang Huang" <justin8086@xxxxxxxxx>
• how to prevent flushing of routing cache in linux FC3
  • From: "Prabhat Hegde" <pubs.hegde@xxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: "Yang Huang" <justin8086@xxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: "Yang Huang" <justin8086@xxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: How to disable the CPU cache?
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• RE: How to disable the CPU cache?
  • From: <krishna.vamsi@xxxxxxxxx>
• How to disable the CPU cache?
  • From: "Yang Huang" <justin8086@xxxxxxxxx>
• Re: sk_buff checksum
  • From: "Nebi Senol Yilmaz" <nsyilmaz@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: sk_buff checksum
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: printk -- unable to print messages
  • From: Gowri Satish Adimulam <gowri@xxxxxxxxxxx>
• RE: printk -- unable to print messages
  • From: <krishna.vamsi@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: shivaligupta <shivaligupta308@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: "Ohad Ben-Cohen" <ohadbc@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: Gowri Satish Adimulam <gowri@xxxxxxxxxxx>
• PROBLEM how to sync page cache ?
  • From: "Ali Ahmed Thawerani" <aaht14@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: shivaligupta <shivaligupta308@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: "rohit hooda" <rohit13hooda@xxxxxxxxxxxxxx>
• Re: printk -- unable to print messages
  • From: Vamsi <krishna.vamsi@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: Gowri Satish Adimulam <gowri@xxxxxxxxxxx>
• Re: printk -- unable to print messages
  • From: shivaligupta <shivaligupta308@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: printk -- unable to print messages
  • From: "Ohad Ben-Cohen" <ohadbc@xxxxxxxxx>
• printk -- unable to print messages
  • From: Gowri Satish Adimulam <gowri@xxxxxxxxxxx>
• Re: __builtin_return_address(0) and schedule()
  • From: Mauricio Lin <mauriciolin2000@xxxxxxxxxxxx>
• Re: __builtin_return_address(0) and schedule()
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• how to add a new IP option
  • From: "Cristian Tapus" <cristian.tapus@xxxxxxxxx>
• __builtin_return_address(0) and schedule()
  • From: Mauricio Lin <mauriciolin2000@xxxxxxxxxxxx>
• sk_buff checksum
  • From: "Nebi Senol Yilmaz" <nsyilmaz@xxxxxxxxx>
• dead links
  • From: "alexander wang" <bienheureux@xxxxxxxxx>
• transmit skb - error
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• scsi command per lun and scsi command per HBA being same or different?
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• R: kernel tuning
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• Re: kernel tuning
  • From: topi <topi@xxxxxxxxxxxx>
• kernel tuning
  • From: "gangaraju.chowki" <gangaraju.chowki@xxxxxxxxxxxxxxxxxxx>
• locking between netfilter hook and kernel thread
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Re: Re: Scheduler question
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Resolved Re: someone can helpme with request_region() ?
  • From: ArYiX <aryixb@xxxxxxxxx>
• cmd_per_lun
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• _sinittext & _einittext
  • From: NAHieu <nahieu@xxxxxxxxx>
• Re: exit(), _exit() and sys_exit()
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: Scheduler question
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: how to create a device in an LKM
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• someone can helpme with request_region() ?
  • From: ArYiX <aryixb@xxxxxxxxx>
• Re: how to create a device in an LKM
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: sleeping function called from invalid context
  • From: Om <aum.nara@xxxxxxxxx>
• Re: exit(), _exit() and sys_exit()
  • From: Bernhard Walle <bernhard.walle@xxxxxx>
• exit(), _exit() and sys_exit()
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• vfsmount_lock in __d_path()
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Problem with schedule_timeout() and udelay() in kernel module
  • From: Ian Yap <d2army@xxxxxxxxx>
• Re: sleeping function called from invalid context
  • From: "Aum Nar" <aum.nara@xxxxxxxxx>
• Re: Problem Inesrting Module
  • From: Om <aum.nara@xxxxxxxxx>
• Re: Problem Inesrting Module
  • From: "Aum Nar" <aum.nara@xxxxxxxxx>
• Re: Problem Inesrting Module
  • From: Andi <a.platschek@xxxxxxxxxx>
• sleeping function called from invalid context
  • From: "Hareesh Nagarajan" <hareesh.nagarajan@xxxxxxxxx>
• Re: Re: dentry cache
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Re: dentry cache
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• howto use request_region() ?
  • From: ArYiX <aryixb@xxxxxxxxx>
• Re: Error message: "0-order allocation failed" ???
  • From: "Xiangfei Jia" <xjianz@xxxxxxxxx>
• Re: Translating Linear Address to Physical
  • From: "eliad lubovsky" <eliad.lubovsky@xxxxxxxxx>
• Re: Translating Linear Address to Physical
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Translating Linear Address to Physical
  • From: "Doron Bleiberg" <kernel.doron@xxxxxxxxx>
• Re: Error message: "0-order allocation failed" ???
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Linux Kernel Scalability for PPPoE server
  • From: "Shrikanth Ramanath" <shriek.007@xxxxxxxxx>
• Re: Module licence problem
  • From: Antonio Mancina <a.mancina@xxxxxxxx>
• Re: Error message: "0-order allocation failed" ???
  • From: Joe Knapka <jknapka@xxxxxxxxxxxxx>
• Error message: "0-order allocation failed" ???
  • From: "Xiangfei Jia" <xjianz@xxxxxxxxx>
• Re: Not a directory!
  • From: Richard Johnson <richj25@xxxxxxxxxxxxx>
• Re: Problem Inesrting Module
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• Re: use bit field or kernel *_bit()
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: use bit field or kernel *_bit()
  • From: Ming Zhang <mingz@xxxxxxxxxxx>
• Re: use bit field or kernel *_bit()
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: use bit field or kernel *_bit()
  • From: Ming Zhang <mingz@xxxxxxxxxxx>
• Problem Inesrting Module
  • From: <soumya.panigrahi@xxxxxxxxx>
• Re: use bit field or kernel *_bit()
  • From: Ming Zhang <mingz@xxxxxxxxxxx>
• Re: use bit field or kernel *_bit()
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: use bit field or kernel *_bit()
  • From: Ming Zhang <mingz@xxxxxxxxxxx>
• Re: Problem inserting module
  • From: "Anand H. Krishnan" <anandhkrishnan@xxxxxxxxx>
• Re: modules linkage problem
  • From: "Anand H. Krishnan" <anandhkrishnan@xxxxxxxxx>
• Re: Not a directory!
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• kexec x86_64: VFS: Cannot open root device, kernel panic
  • From: lnx lrn <lnxlrn@xxxxxxxxx>
• Re: mailer daemons in kernel
  • From: "Anupam Kapoor" <anupam.kapoor@xxxxxxxxx>
• Re: mailer daemons in kernel
  • From: "Hareesh Nagarajan" <hareesh.nagarajan@xxxxxxxxx>
• Re: proc filesystem souce code
  • From: "Hareesh Nagarajan" <hareesh.nagarajan@xxxxxxxxx>
• Re: how to create a device from an LKM
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: how to create a device in an LKM
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: use bit field or kernel *_bit()
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: how to use mknod in LKM's
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: how to use mknod in LKM's
  • From: Greg KH <greg@xxxxxxxxx>
• how to create a device in an LKM
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• how to use mknod in LKM's
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• mailer daemons in kernel
  • From: "sunny chawla" <sun4udee@xxxxxxxxx>
• use bit field or kernel *_bit()
  • From: Ming Zhang <mingz@xxxxxxxxxxx>
• Re: dentry cache
  • From: Ashish Khurange <ashishk@xxxxxxxxxxxxx>
• Re: dentry cache
  • From: Ashish Khurange <ashishk@xxxxxxxxxxxxx>
• Re: kernel source
  • From: "K.R. Foley" <kr@xxxxxxxxxx>
• Re: timer_function+timer_list
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: kernel source
  • From: "K.R. Foley" <kr@xxxxxxxxxx>
• Re: R: installing kernel source
  • From: "Fawad Lateef" <fawadlateef@xxxxxxxxx>
• Re: dentry cache
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: RE: RE: timer_function+timer_list
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: Problem in inserting module
  • From: Vin <pane.vinayak@xxxxxxxxx>
• Re: dentry cache
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Module licence problem
  • From: Antonio Mancina <a.mancina@xxxxxxxx>
• Re: timer_function+timer_list
  • From: "Hareesh Nagarajan" <hareesh.nagarajan@xxxxxxxxx>
• RE: RE: timer_function+timer_list
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: kernel source
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: dentry cache
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• dentry cache
  • From: Ashish Khurange <ashishk@xxxxxxxxxxxxx>
• Re: R: installing kernel source
  • From: "Prosenjit Kundu" <pkundu.kernel@xxxxxxxxx>
• RE: RE: RE: timer_function+timer_list
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: kernel source
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• Re: RE: timer_function+timer_list
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: kernel source
  • From: "Prosenjit Kundu" <pkundu.kernel@xxxxxxxxx>
• Re: proc filesystem souce code
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• Re: kernel source
  • From: "K.R. Foley" <kr@xxxxxxxxxx>
• Re: kernel source
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• kernel source
  • From: Gowri Satish Adimulam <gowri@xxxxxxxxxxx>
• Re: proc filesystem souce code
  • From: "Xiangfei Jia" <xjianz@xxxxxxxxx>
• Re: Executing user-space program from an LKM
  • From: "Ohad Ben-Cohen" <ohadbc@xxxxxxxxx>
• Re: proc filesystem souce code
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• Re: Executing user-space program from an LKM
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• Re: Module licence problem
  • From: Oldani Massimiliano <sgrakkyu@xxxxxxxxxx>
• Re: Executing user-space program from an LKM
  • From: Oldani Massimiliano <sgrakkyu@xxxxxxxxxx>
• Executing user-space program from an LKM
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• RE: .o vs .ko format changes
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: proc filesystem souce code
  • From: Mark-Walter@xxxxxxxxxxx (Mark Walter)
• RE: timer_function+timer_list
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: Fwd: Problem inserting module
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Module licence problem
  • From: Antonio Mancina <a.mancina@xxxxxxxx>
• Doubt regarding IOREMAP
  • From: "Vijay Ram.C" <cvijay@xxxxxxxxxxxxxxxxxx>
• timer_function+timer_list
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: proc filesystem souce code
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• proc filesystem souce code
  • From: "Xiangfei Jia" <xjianz@xxxxxxxxx>
• Re: Anybody know about i_flock?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Grep and Hidden files
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Anybody know about i_flock?
  • From: Richard Johnson <richj25@xxxxxxxxxxxxx>
• Re: disagrees about version of symbol struct_module
  • From: Richard Johnson <richj25@xxxxxxxxxxxxx>
• disagrees about version of symbol struct_module
  • From: Jose Luis Alarcon Sanchez <jlalarcon@xxxxxxxxx>
• Re: symbols of a module
  • From: Oldani Massimiliano <sgrakkyu@xxxxxxxxxx>
• symbols of a module
  • From: Jose Luis Alarcon Sanchez <jlalarcon@xxxxxxxxx>
• USB and usb_bulk_msg
  • From: Hossein Aminaiee <aminaiee@xxxxxxxxx>
• RE: Timer manipulation in 2.6.13
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• RE: Timer manipulation in 2.6.13
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Timer manipulation in 2.6.13
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• RE: Timer manipulation in 2.6.13
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• RE: Timer manipulation in 2.6.13
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: Timer manipulation in 2.6.13
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• parallel execution in rc.local
  • From: "Nilanjan Roychowdhury" <Nilanjan.Roychowdhury@xxxxxxxx>
• Re: Grep and Hidden files
  • From: apgo@xxxxxxxxxxxxx (Arthur Othieno)
• Re: Timer manipulation in 2.6.13
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: KERNEL COMPILATION
  • From: suman adak <suman@xxxxxxxxxxxxxx>
• Re: Grep and Hidden files
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• Re: Grep and Hidden files
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• Timer manipulation in 2.6.13
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• Re: KERNEL COMPILATION
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: KERNEL COMPILATION
  • From: suman adak <suman@xxxxxxxxxxxxxx>
• Re: KERNEL COMPILATION
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• KERNEL COMPILATION
  • From: SUMAN <suman@xxxxxxxxxxxxxx>
• Re: cannot mount rootfs !!
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: initrd
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: timerfunction-delay
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Re: Not a directory!
  • From: "prasad Musale" <prasad.musale@xxxxxxxxx>
• Re: Re: timerfunction-delay
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Can't access the superblock list.
  • From: "prasad Musale" <prasad.musale@xxxxxxxxx>
• initrd
  • From: "Sarith Lambu" <sarith.lambu@xxxxxxxxx>
• Re: timerfunction-delay
  • From: Andreas Gaupmann <andreas.gaupmann@xxxxxxx>
• RE: Problem in inserting module
  • From: "Steve Iribarne" <steve.iribarne@xxxxxxxxxxxxxxxxxxxxx>
• Problem inserting module
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• cannot mount rootfs !!
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: Problem in inserting module
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: Problem in inserting module
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• Re: Problem in inserting module
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• R: kernel compilation make error
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• How to split patch and whom to sent to
  • From: "Seewer Philippe" <philippe.seewer@xxxxxx>
• Re: Scheduler question
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Grep and Hidden files
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: timerfunction-delay
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Scheduler question
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Grep and Hidden files
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• Re: replacing ioctl()
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: PCI DMA - memory-to-io data transfer
  • From: munees waran <munees40@xxxxxxxxxxx>
• Re: jiffies in linux2.6.13.2
  • From: Florin Malita <fmalita@xxxxxxxxx>
• Re: PCI DMA - memory-to-io data transfer
  • From: munees waran <munees40@xxxxxxxxxxx>
• Re: modules linkage problem
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: PCI DMA - memory-to-io data transfer
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: kernel_thread
  • From: "James Yu" <cyu021@xxxxxxxxx>
• timerfunction-delay
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: How to calculate memory usage?
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• Re: Not a directory!
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Scheduler question
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• kernel compilation make error
  • From: linux lover <linux_lover2004@xxxxxxxxx>
• Re: Can't access the superblock list.
  • From: Jan Hudec <bulb@xxxxxx>
• requesting another IRQ?
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: Grep and Hidden files
  • From: Matthew Percival <matthew@xxxxxxxxx>
• R: installing kernel source
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• Re: How do we profile our code?
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• Re: Scheduler question
  • From: Stavros Passas <stabat@xxxxxxxxxx>
• Re: please help: detecting the type of pci slot ?
  • From: "Gabriel Somlo" <gsomlo@xxxxxxxxx>
• modules linkage problem
  • From: "Arun Srinivasan" <arunlkml@xxxxxxxxx>
• Re: replacing ioctl()
  • From: Greg KH <greg@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: "Nate Diller" <nate.diller@xxxxxxxxx>
• Re: replacing ioctl()
  • From: Diego Calleja <diegocalleja@xxxxxxxxx>
• Can't access the superblock list.
  • From: "prasad Musale" <prasad.musale@xxxxxxxxx>
• Re: Scheduler question
  • From: "Hareesh Nagarajan" <hareesh.nagarajan@xxxxxxxxx>
• PCI DMA - Where to specify destination address (IO address)
  • From: munees waran <munees40@xxxxxxxxxxx>
• replacing ioctl()
  • From: "Bahadir Balban" <bilgehan.balban@xxxxxxxxx>
• Re: How do we find out the bus width of a processor ?
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• Re: kernel_thread
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: kernel_thread
  • From: "James Yu" <cyu021@xxxxxxxxx>
• Re: jiffies in linux2.6.13.2
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Re: Can't access the superblock list.
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: kernel compilation make error
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: kernel_thread
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Problem in inserting module
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: .o vs .ko format changes
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• .o vs .ko format changes
  • From: linux lover <linux_lover2004@xxxxxxxxx>
• Scheduler question
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: static compilation or as a module
  • From: "Hareesh Nagarajan" <hareesh.nagarajan@xxxxxxxxx>
• How-To Access The Names Database
  • From: access@xxxxxxxxxxxxxxxxx
• Re: How do we profile our code?
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: How do we profile our code?
  • From: Hayim Shaul <hayim@xxxxxxxxxxxxxx>
• Not a directory!
  • From: "prasad Musale" <prasad.musale@xxxxxxxxx>
• Re: kernel_thread
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: installing kernel source
  • From: Florin Malita <fmalita@xxxxxxxxx>
• Re: kernel_thread
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: munees waran <munees40@xxxxxxxxxxx>
• Re: requesting another IRQ?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: installing kernel source
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Can't access the superblock list.
  • From: "prasad Musale" <prasad.musale@xxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• installing kernel source
  • From: "Sarang Radke" <radke.s@xxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: munees waran <munees40@xxxxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: munees waran <munees40@xxxxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: munees waran <munees40@xxxxxxxxxxx>
• Re: kernel_thread
  • From: "James Yu" <cyu021@xxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: kernel_thread
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: kernel_thread
  • From: "James Yu" <cyu021@xxxxxxxxx>
• jiffies in linux2.6.13.2
  • From: "Hsieh Steve" <stevecfhsieh@xxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: PCI DMA - Where to specify destination address (IO address)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: How do we profile our code?
  • From: Hayim Shaul <hayim@xxxxxxxxxxxxxx>
• Re: How do we profile our code?
  • From: Manav Kataria <manav@xxxxxxxxxxxxx>
• reading cpu id
  • From: Hayim Shaul <hayim@xxxxxxxxxxxxxx>
• Re: static compilation or as a module
  • From: "Fawad Lateef" <fawadlateef@xxxxxxxxx>
• Re: static compilation or as a module
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: How to calculate memory usage?
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• RE: How to calculate memory usage?
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: How do we profile our code?
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: How do we find out the bus width of a processor ?
  • From: anil dahiya <ak_ait@xxxxxxxxx>
• Re: help needed- compilation issue
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: How do we find out the bus width of a processor ?
  • From: "Bob Copeland" <email@xxxxxxxxxxxxxxx>
• Re: How do we find out the bus width of a processor ?
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Re: please help: detecting the type of pci slot ?
  • From: Greg KH <greg@xxxxxxxxx>
• How do we find out the bus width of a processor ?
  • From: "Manav Kataria" <manav@xxxxxxxxxxxxx>
• Re: please help: detecting the type of pci slot ?
  • From: "Gabriel Somlo" <gsomlo@xxxxxxxxx>
• Re: How to calculate memory usage?
  • From: "Manav Kataria" <manav@xxxxxxxxxxxxx>
• How do we profile our code?
  • From: "Manav Kataria" <manav@xxxxxxxxxxxxx>
• Re: How do we profile our code?
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• How to calculate memory usage?
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: help needed- compilation issue
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: help needed- compilation issue
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: help needed- compilation issue
  • From: "Goldwyn Rodrigues" <rgoldwyn@xxxxxxxxx>
• Re: help needed- compilation issue
  • From: Gowri Satish Adimulam <gowri@xxxxxxxxxxx>
• Re: Re: need help with syslogd
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: help needed- compilation issue
  • From: Gowri Satish Adimulam <gowri@xxxxxxxxxxx>
• Re: please help: detecting the type of pci slot ?
  • From: Greg KH <greg@xxxxxxxxx>
• please help: detecting the type of pci slot ?
  • From: "Gabriel Somlo" <gsomlo@xxxxxxxxx>
• Re: need help with syslogd
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: need help with syslogd
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• need help with syslogd
  • From: "Arun Srinivasan" <arunlkml@xxxxxxxxx>
• Re: help needed- compilation issue
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: help needed- compilation issue
  • From: "Vinay Kalkoti" <kalkoti.vinay@xxxxxxxxx>
• help needed- compilation issue
  • From: Gowri Satish Adimulam <gowri@xxxxxxxxxxx>
• PCI DMA memory-to-memory transfer
  • From: munees waran <munees40@xxxxxxxxxxx>
• RE: Linux Security Module and System Response Time Tracking
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: address space size of running kernel
  • From: Jose Luis Alarcon Sanchez <jlalarcon@xxxxxxxxx>
• Re: address space size of running kernel
  • From: "Hareesh Nagarajan" <hareesh.nagarajan@xxxxxxxxx>
• address space size of running kernel
  • From: Jose Luis Alarcon Sanchez <jlalarcon@xxxxxxxxx>
• Re: Kernel Compilation Problem
  • From: suman adak <suman@xxxxxxxxxxxxxx>
• kernel compilation problem
  • From: Deepak Barua <termin_t@xxxxxxxxxxx>
• Re: Kernel Compilation Problem
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Kernel Compilation Problem
  • From: Deepak Barua <termin_t@xxxxxxxxxxx>
• Re: static compilation or as a module
  • From: "Fawad Lateef" <fawadlateef@xxxxxxxxx>
• static compilation or as a module
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Linux Security Module and System Response Time Tracking
  • From: "Gaurav Dhiman" <gauravd.chd@xxxxxxxxx>
• Re: Linux Security Module and System Response Time Tracking
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: i has some problem about sock_sendmsg and sock_recvmsg
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Do read-write semaphores prefer writers over readers?
  • From: "Hareesh Nagarajan" <hareesh.nagarajan@xxxxxxxxx>
• Linux Security Module and System Response Time Tracking
  • From: Mauricio Lin <mauriciolin2000@xxxxxxxxxxxx>
• Re: IRQ autodetection
  • From: Greg KH <greg@xxxxxxxxx>
• IRQ autodetection
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Page cache and adress_space
  • From: Mauricio Lin <mauriciolin2000@xxxxxxxxxxxx>
• Re: Module Compatibility
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• Re: module compile
  • From: "Fawad Lateef" <fawadlateef@xxxxxxxxx>
• generic question on API testing
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Do read-write semaphores prefer writers over readers?
  • From: Hareesh Nagarajan <hareesh.nagarajan@xxxxxxxxx>
• Re: MACRO - How is it working in Linux
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: MACRO - How is it working in Linux
  • From: Mandeep Sandhu <Mandeep_Sandhu@xxxxxxxxxxx>
• Kernel Timers and Affix
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: MACRO - How is it working in Linux
  • From: "Abu M. Muttalib" <abum@xxxxxxxxx>
• RE: MACRO - How is it working in Linux
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Re: MACRO - How is it working in Linux
  • From: Momchil Velikov <velco@xxxxxxxxx>
• Re: MACRO - How is it working in Linux
  • From: Fabiano Ramos <fabiano.ramos@xxxxxxxxx>
• Re: MACRO - How is it working in Linux
  • From: webmaster@xxxxxxxxxxxx
• Re: MACRO - How is it working in Linux
  • From: Askadar <askadar@xxxxxxxxxxxxxxxx>
• MACRO - How is it working in Linux
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Re: module compile
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• module compile
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: Why does not select() work on SysV Message Queues?
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• Re: Why does not select() work on SysV Message Queues?
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Why does not select() work on SysV Message Queues?
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• schedule_timeout
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: error: dereferencing pointer to incomplete type
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxxx>
• Re: describing each irq uniquely
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: error: dereferencing pointer to incomplete type
  • From: Vincent Thomasset <vincent.thomasset@xxxxxxxxx>
• error: dereferencing pointer to incomplete type
  • From: Sun Agham <agham.sunil@xxxxxxxxx>
• reg. flash card with SPI and interfacing to PC
  • From: vinay kumar <aekalavya@xxxxxxxxx>
• static compilation / module
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Fwd: static compilation / module
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Sound Recording Problem in linux-2.6.13
  • From: AnupM <anupm@xxxxxxxxx>
• Re: hi
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: Module Compatibility
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxxx>
• describing each irq uniquely
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• Re: insmod error
  • From: Jim Bauer <jfbauer@xxxxxxx>
• Re: insmod error
  • From: Greg KH <greg@xxxxxxxxx>
• insmod error
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Re: Module Compatibility
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• Re: Parallel Port Interrupt Generation.
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: Module Compatibility
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Ethernet Checksum
  • From: Stavros Passas <stabat@xxxxxxxxxx>
• Module Compatibility
  • From: Sunil Agham <sunil.agham@xxxxxxxxx>
• Re: time delay
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• time delay
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Parallel Port Interrupt Generation.
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: module parameters
  • From: Aman Wardak <aman.wardak@xxxxxxxxx>
• Re: i has some problem about sock_sendmsg and sock_recvmsg
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• i has some problem about sock_sendmsg and sock_recvmsg
  • From: "sasin janpungtong" <sasin324@xxxxxxxxxxx>
• Re: hi
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: version disagreement in insmod
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• Re: module makefile examples
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: hi
  • From: Ashok Sharma <aks6d@xxxxxxxxxxx>
• Re: version disagreement in insmod
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: time delay
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: hi
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: time delay
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Ethernet Checksum
  • From: Krishna Pattabiraman <pkrishna@xxxxxxxxxxxxx>
• hi
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• time delay
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: Ethernet Checksum
  • From: mohanlal jangir <mohanlal@xxxxxxxxxxx>
• Re: Calling work queue in a tasklet?
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• RE: Calling work queue in a tasklet?
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Re: Calling work queue in a tasklet?
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Calling work queue in a tasklet?
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• KERNEL: assertion (tp->retrans_out == 0) failed at net/ipv4/tcp_input.c
  • From: Rajesh Mahajan <rajeshmahajan09@xxxxxxxxx>
• Re: module parameters
  • From: Aman Wardak <aman.wardak@xxxxxxxxx>
• Ethernet Checksum
  • From: Krishna Pattabiraman <pkrishna@xxxxxxxxxxxxx>
• Device Mapper and queue running
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxxx>
• Re: error no inside a module
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Fwd: Page Tables Documentation
  • From: Ohad Ben-Cohen <ohad@xxxxxxxxxxxx>
• Re: Page Tables Documentation
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Page Tables Documentation
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Re: Badness in sleep_on_timeout on kernel 2.6.9-1.667 ( fedora core 3)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: module parameters
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• module parameters
  • From: Aman Wardak <aman.wardak@xxxxxxxxx>
• Re: Are kfree(), kmem_cache_free() operations that are guaranteed not to sleep?
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• module makefile examples
  • From: Jared Greenwald <greenwaldjared@xxxxxxxxx>
• Re: R: Linux kernel 2.6.11 and external module error
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• version disagreement in insmod
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• Are kfree(), kmem_cache_free() operations that are guaranteed not to sleep?
  • From: Hareesh Nagarajan <hareesh.nagarajan@xxxxxxxxx>
• Re: error no inside a module
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: error no inside a module
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• error no inside a module
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: is PTP gadget availble?
  • From: Vishal Borker <vishal.borker@xxxxxxxxx>
• handling 16 bit addresses
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: Can we hold a spin lock and call up() (on a semaphore)
  • From: Stavros Passas <stabat@xxxxxxxxxx>
• Re: Can we hold a spin lock and call up() (on a semaphore)
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Restoring the bashrc contents
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Can we hold a spin lock and call up() (on a semaphore)
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: is PTP gadget availble?
  • From: Learner <ruxyz@xxxxxxxxx>
• RE: Can we hold a spin lock and call up() (on a semaphore)
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Re: Restoring the bashrc contents
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: Restoring the bashrc contents
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Restoring the bashrc contents
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: is PTP gadget availble?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: is PTP gadget availble?
  • From: jun wang <conan.maillist@xxxxxxxxx>
• Re: is PTP gadget availble?
  • From: "rohit hooda" <rohit13hooda@xxxxxxxxxxxxxx>
• Re: is PTP gadget availble?
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• is PTP gadget availble?
  • From: jun wang <conan.maillist@xxxxxxxxx>
• Re: Restore kdbg - how?
  • From: Prosenjit Kundu <pkundu.kernel@xxxxxxxxx>
• Re: Can we hold a spin lock and call up() (on a semaphore)
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Can we hold a spin lock and call up() (on a semaphore)
  • From: Naveed Latif <kernelmail.naveed@xxxxxxxxx>
• RE: linux- about i/o
  • From: Konstantinos Pachopoulos <kostaspaxos@xxxxxxxx>
• RE: linux- about i/o
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• RE: Restore kdbg - how?
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: Restore kdbg - how?
  • From: Prosenjit Kundu <pkundu.kernel@xxxxxxxxx>
• RE: Restore kdbg - how?
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: Restore kdbg - how?
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Restore kdbg - how?
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: linux- about i/o
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: linux- about i/o
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• IOREMAP() a 16 bit address???
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• linux- about i/o
  • From: Konstantinos Pachopoulos <kostaspaxos@xxxxxxxx>
• Re: readonly filesystem
  • From: Essien Essien <essiene@xxxxxxxxx>
• Re: readonly filesystem
  • From: Sauro Salomoni <sauro@xxxxxxxxxxx>
• readonly filesystem
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Can we hold a spin lock and call up() (on a semaphore)
  • From: Hareesh Nagarajan <hareesh.nagarajan@xxxxxxxxx>
• PREMPT confusion... stilll hanging around me
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Re: Badness in sleep_on_timeout on kernel 2.6.9-1.667 ( fedora core 3)
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• RE: Compiling a specific module without compiling whole of the kernel
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: Badness in sleep_on_timeout on kernel 2.6.9-1.667 ( fedora core 3)
  • From: anil dahiya <ak_ait@xxxxxxxxx>
• RE: serial port problem?
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• RE: Compiling a specific module without compiling whole of the kernel
  • From: <kaustav.majumdar@xxxxxxxxx>
• add_to_swap(...) send page to swap
  • From: Systems Dev <systems.dev@xxxxxxxxx>
• serial port problem?
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Re: Badness in sleep_on_timeout on kernel 2.6.9-1.667 ( fedora core 3)
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Badness in sleep_on_timeout on kernel 2.6.9-1.667 ( fedora core 3)
  • From: anil dahiya <ak_ait@xxxxxxxxx>
• understanding kernel page tables
  • From: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
• Re: Compiling a specific module without compiling whole of the kernel
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: Query on Kernel Timers and Process Context Code
  • From: Hareesh Nagarajan <hareesh.nagarajan@xxxxxxxxx>
• Re: Query on Kernel Timers and Process Context Code
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: A task_struct question
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: A task_struct question
  • From: Andreas Gaupmann <andreas.gaupmann@xxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: Query on Kernel Timers and Process Context Code
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Compiling a specific module without compiling whole of the kernel
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• Re: A task_struct question
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• A task_struct question
  • From: Andreas Gaupmann <andreas.gaupmann@xxxxxxx>
• RE: spinlock on uniprocessor systems
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• RE: spinlock on uniprocessor systems
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• RE: spinlock on uniprocessor systems
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Query on Kernel Timers and Process Context Code
  • From: Hareesh Nagarajan <hareesh.nagarajan@xxxxxxxxx>
• Expalin Schedule_work Working ....
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Re: some doubts on cache coherence
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: some doubts on cache coherence
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Exporting sys_call_table for 2.6.11
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• configfs
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Exporting sys_call_table for 2.6.11
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Exporting sys_call_table for 2.6.11
  • From: Σωτήριο Κοντογιάννη <skontog@xxxxxxxxxx>
• Re: Linux kernel 2.6.11 and external module error
  • From: Shinose Abdul Rahiman <shinose@xxxxxxxxx>
• Re: some doubts on cache coherence
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: Re: some doubts on cache coherence
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: Re: kernel preemption while returning from interrupts
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• serial port driver - testing flow control?
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Re: Re: kernel preemption while returning from interrupts
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• RE: device class related
  • From: "Suresh Shelvapille" <suri@xxxxxxxxxxxxxxxxxxx>
• Re: device class related
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• device class related
  • From: "Suresh Shelvapille" <suri@xxxxxxxxxxxxxxxxxxx>
• Re: some doubts on cache coherence
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: R: Linux kernel 2.6.11 and external module error
  • From: Σωτήριο Κοντογιάννη <skontog@xxxxxxxxxx>
• R: Linux kernel 2.6.11 and external module error
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• Re: Linux kernel 2.6.11 and external module error
  • From: Σωτήριο Κοντογιάννη <skontog@xxxxxxxxxx>
• Re: Linux kernel 2.6.11 and external module error
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• R: Linux kernel 2.6.11 and external module error
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• Linux kernel 2.6.11 and external module error
  • From: Σωτήριο Κοντογιάννη <skontog@xxxxxxxxxx>
• can i hook "skb" before calling hard_start_xmit in tunnel module?
  • From: "Park, Jin Hyung" <jinhyung@xxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: some doubts on cache coherence
  • From: Prabhat Hegde <pubs.hegde@xxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: Re: some doubts on cache coherence
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: some doubts on cache coherence
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: PCI Device Driver: Porting to 2.6 kernel
  • From: Greg KH <greg@xxxxxxxxx>
• Re: PCI Device Driver: Porting to 2.6 kernel
  • From: John Klingler <john@xxxxxxxxxxx>
• How to read physical memory from daemon: during initrd stage of boot
  • From: Vikas Aggarwal <vik.reck@xxxxxxxxx>
• Re: hai....
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: Timer function
  • From: sanjay kumar <xs2sanjay@xxxxxxxxx>
• Timer function
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• R: hai....
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• hai....
  • From: Sivasankar Sankaran <sivasankar.s4u@xxxxxxxxx>
• IOREMAP ISSUE!!!!!
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: Re: kernel preemption while returning from interrupts
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: some doubts on cache coherence
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: need help
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: some doubtsabout cachce coherence & spinlocks - can anyone help?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• some doubtsabout cachce coherence & spinlocks - can anyone help?
  • From: Prabhat Hegde <pubs.hegde@xxxxxxxxx>
• RE: spinlock on uniprocessor systems
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• some doubts on cache coherence - can anyone answer?
  • From: Prabhat Hegde <pubs.hegde@xxxxxxxxx>
• RE: Sock_recvmsg() blocks and is not killable
  • From: "Jitesh Shah" <jitesh.shah@xxxxxxxxxx>
• RE: need help
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: Any debugger tool for a bootloader ?
  • From: Krishna Pattabiraman <pkrishna@xxxxxxxxxxxxx>
• Re: need help
  • From: Sivasankar Sankaran <sivasankar.s4u@xxxxxxxxx>
• Re: Any debugger tool for a bootloader ?
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: dev_dbg etc with char drivers ?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: dev_dbg etc with char drivers ?
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• dev_dbg etc with char drivers ?
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Any debugger tool for a bootloader ?
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• tracing packets from wire up to the network stack
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• Re: Sock_recvmsg() blocks and is not killable
  • From: K S Sandeep <kssandeep@xxxxxxxxx>
• Re: spinlock on uniprocessor systems
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• RE: Sock_recvmsg() blocks and is not killable
  • From: "Jitesh Shah" <jitesh.shah@xxxxxxxxxx>
• Re: Make my own modules for kernel 2.4(.32)
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• RE: need help
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• R: need help
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• spinlock on uniprocessor systems
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• need help
  • From: Sivasankar Sankaran <sivasankar.s4u@xxxxxxxxx>
• Re: need help
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• how to map USB MOUSE EVENT in device driver
  • From: mayank rana <mayank_rana_it@xxxxxxxxxxx>
• Make my own modules for kernel 2.4(.32)
  • From: Massimo De Beni <maxdb82@xxxxxxxxx>
• Re: how to map USB MOUSE EVENT in device driver
  • From: Shinose Abdul Rahiman <shinose@xxxxxxxxx>
• Re: how to map USB MOUSE EVENT in device driver
  • From: Shinose Abdul Rahiman <shinose@xxxxxxxxx>
• Re: kernel preemption while returning from interrupts
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: kernel preemption while returning from interrupts
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: kernel preemption while returning from interrupts
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: kernel preemption while returning from interrupts
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: kernel preemption while returning from interrupts
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• RE: API for Disk head position
  • From: "James Stevenson" <james@xxxxxxxxxxxxxx>
• Re: some doubts on cache coherence
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel preemption while returning from interrupts
  • From: Joe Knapka <jknapka@xxxxxxxxxxxxx>
• Re: kernel preemption while returning from interrupts
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• some doubts on cache coherence
  • From: Prabhat Hegde <pubs.hegde@xxxxxxxxx>
• kernel preemption while returning from interrupts
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: Re: Please Help me in the Basics...
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: Re: Re: Re: Understanding non-preemptive kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: API for Disk head position
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Re: Re: Re: Understanding non-preemptive kernel
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• API for Disk head position
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Re: Entry function of the LINUX Code
  • From: Nauman Tahir <nauman.tahir@xxxxxxxxx>
• Re: Doubt regarding memory usage
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: COPY_TO_USER PROBLEMS!
  • From: Greg KH <greg@xxxxxxxxx>
• Re: bus error
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: SMP based kernel modules
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• SMP based kernel modules
  • From: Vijay Chauhan <kernel.vijay@xxxxxxxxx>
• Re: COPY_TO_USER PROBLEMS!
  • From: K S Sandeep <kssandeep@xxxxxxxxx>
• I/O Scheduling
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Re: COPY_TO_USER PROBLEMS!
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: Scheduler and user preemption
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: Re: Re: Re: Understanding non-preemptive kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Query related to BH_PrivateStart
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Re: Scheduler and user preemption
  • From: eliad lubovsky <eliad.lubovsky@xxxxxxxxx>
• Re: Scheduler and user preemption
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Scheduler and user preemption
  • From: Ashok Sharma <aks6d@xxxxxxxxxxx>
• Re: Sock_recvmsg() blocks and is not killable
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Please Help me in the Basics...
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: bus error
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• New URL for "Outline of the Linux VM"
  • From: Joe Knapka <jknapka@xxxxxxxxxxxxx>
• bus error
  • From: "mohit rastogi" <mohitr@xxxxxxxxxxxxxx>
• COPY_TO_USER PROBLEMS!
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: External Modules: undefined symbol problem
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Doubt regarding memory usage
  • From: srikanth <sri@xxxxxxxxxxxxxxxxxx>
• RE: Sock_recvmsg() blocks and is not killable
  • From: "Jitesh Shah" <jitesh.shah@xxxxxxxxxx>
• Help needed for PCI device driver
  • From: munees waran <munees40@xxxxxxxxxxx>
• Re: Sock_recvmsg() blocks and is not killable
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• Re: PCI Device Driver: Porting to 2.6 kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Re: Re: Re: Understanding non-preemptive kernel
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• RE: Sock_recvmsg() blocks and is not killable
  • From: "Jitesh Shah" <jitesh.shah@xxxxxxxxxx>
• RE: Sock_recvmsg() blocks and is not killable
  • From: "Jitesh Shah" <jitesh.shah@xxxxxxxxxx>
• shared memory implementation in Kernel 2.4.xx
  • From: Onkar N Mahajan <onkar.n.m@xxxxxxxxx>
• Re: What's the difference/relation between pid,tgid,pgid,sid?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: SIGUSR1 function call?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Please Help me in the Basics...
  • From: Mulyadi Santosa <a_mulyadi@xxxxxxxxxx>
• Re: PCI Device Driver: Porting to 2.6 kernel
  • From: Greg KH <greg@xxxxxxxxx>
• Re: PCI Device Driver: Porting to 2.6 kernel
  • From: John Klingler <john@xxxxxxxxxxx>
• Re: PCI Device Driver: Porting to 2.6 kernel
  • From: Greg KH <greg@xxxxxxxxx>
• PCI Device Driver: Porting to 2.6 kernel
  • From: John Klingler <john@xxxxxxxxxxx>
• Re: kernel/security/capability module?
  • From: Greg KH <greg@xxxxxxxxx>
• What's the difference/relation between pid,tgid,pgid,sid?
  • From: Cristian Tapus <cristian.tapus@xxxxxxxxx>
• kernel/security/capability module?
  • From: Nikola <root.admin1@xxxxxxxxxxx>
• Re: file access in kernel
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Sunil Agham <sunil.agham@xxxxxxxxx>
• Re: External Modules: undefined symbol problem
  • From: Lukas Ruf <ruf@xxxxxxxxx>
• Re: file access in kernel
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: file access in kernel
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Please Help me in the Basics...
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: [Unionfs] open, readdir in ramfs
  • From: hooanon05@xxxxxxxxxxx
• Re: open, readdir in ramfs
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: External Modules: undefined symbol problem
  • From: Lukas Ruf <ruf@xxxxxxxxx>
• Re: External Modules: undefined symbol problem
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• External Modules: undefined symbol problem
  • From: Lukas Ruf <ruf@xxxxxxxxx>
• open, readdir in ramfs
  • From: Sunil Agham <sunil.agham@xxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Sergey Semenov <sergey.semionov@xxxxxxxxx>
• Re: "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Sunil Agham <sunil.agham@xxxxxxxxx>
• Re: "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Sunil Agham <sunil.agham@xxxxxxxxx>
• Re: file access in kernel
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• Re: "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: file access in kernel
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• Re: "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Sunil Agham <sunil.agham@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• "insmod: error inserting 'abc.ko' : -1 Invalid Format"
  • From: Sunil Agham <sunil.agham@xxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• Re: compile warning: could not find versions
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: compile warning: could not find versions
  • From: NaGp <nagp.lists@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Joe Knapka <jknapka@xxxxxxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Sock_recvmsg() blocks and is not killable
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• Re: Sock_recvmsg() blocks and is not killable
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Device Driver testing - Please CC the reply to my email address
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Device Driver testing - Please CC the reply to my email address
  • From: Arun Srinivasan <arunlkml@xxxxxxxxx>
• Re: compile warning: could not find versions
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Little Linux kernel projects
  • From: Eduardo Bezerra <edubezval@xxxxxxxxx>
• question about default_ldt
  • From: orca chen <orca.chen@xxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• virt_to_page doubt
  • From: "Sudharsan Vijayaraghavan" <sud_vijay@xxxxxxxxxxxxxx>
• Re: file access in kernel
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: file access in kernel
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: local_bh_enable with irq's disabled
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• file access in kernel
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• Re: __inte_lookup_established: kernel 2.6.15
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: compile warning: could not find versions
  • From: NaGp <nagp.lists@xxxxxxxxx>
• Re: compile warning: could not find versions
  • From: NaGp <nagp.lists@xxxxxxxxx>
• Re: compile warning: could not find versions
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: compile warning: could not find versions
  • From: NaGp <nagp.lists@xxxxxxxxx>
• Re: compile warning: could not find versions
  • From: Nagaprabhanjan Bellari <nagp.lists@xxxxxxxxx>
• Re: compile warning: could not find versions
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: compile warning: could not find versions
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• compile warning: could not find versions
  • From: Nagaprabhanjan Bellari <nagp.lists@xxxxxxxxx>
• Re: Re: Re: Re: Understanding non-preemptive kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Little Linux kernel projects
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• __inte_lookup_established: kernel 2.6.15
  • From: Vikas Aggarwal <vik.reck@xxxxxxxxx>
• Re: Need to arbitrary set a PCI bridge memory window
  • From: Greg KH <greg@xxxxxxxxx>
• Little Linux kernel projects
  • From: Andre Luiz da Silva <andrack@xxxxxxxxx>
• local_bh_enable with irq's disabled
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Need to arbitrary set a PCI bridge memory window
  • From: jfaslist <jfaslist@xxxxxxxx>
• Re: Please Help me in the Basics...
  • From: Sarith Lambu <sarith.lambu@xxxxxxxxx>
• Re: Questions/Suggestion regarding article "Interrupt Handling Internals in Linux Kernel"
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• RE: Sock_recvmsg() blocks and is not killable
  • From: "Jitesh Shah" <jitesh.shah@xxxxxxxxxx>
• RE: Sock_recvmsg() blocks and is not killable
  • From: "Jitesh Shah" <jitesh.shah@xxxxxxxxxx>
• Re: Sock_recvmsg() blocks and is not killable
  • From: "Gurmit Teotia" <gurmit.teotia@xxxxxxxxxxxxxx>
• Sock_recvmsg() blocks and is not killable
  • From: "Jitesh Shah" <jitesh.shah@xxxxxxxxxx>
• Re: Re: Re: Understanding non-preemptive kernel
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Re: Understanding non-preemptive kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: Re: Understanding non-preemptive kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: has anybody used Ixp400 library?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• has anybody used Ixp400 library?
  • From: "Park, Jin Hyung" <jinhyung@xxxxxxxxx>
• Re: Understanding non-preemptive kernel
  • From: Joe Knapka <jknapka@xxxxxxxxxxxxx>
• Re: How to start kernel programming And a test Environ
  • From: "Park, Jin Hyung" <jinhyung@xxxxxxxxx>
• Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Joe Knapka <jknapka@xxxxxxxxxxxxx>
• Re: How to start kernel programming And a test Environ
  • From: Ashok Sharma <aks6d@xxxxxxxxxxx>
• Changing the pid of a process generates an OOPS in other places
  • From: Cristian Tapus <cristian.tapus@xxxxxxxxx>
• Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Joe Knapka <jknapka@xxxxxxxxxxxxx>
• Re: Don't want usb device detection ( sorry, by mistake I asked this question in wrong thread)
  • From: Neependra Kumar Khare <neependra.khare@xxxxxxxxxxxxxx>
• Re: How to start kernel programming
  • From: Christophe Lucas <clucas@xxxxxxxxxxxxx>
• Routing problem with Multihomed machine
  • From: Satinder <jeet_sat12@xxxxxxxxxxx>
• Re: Please Help me in the Basics...
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: System hangs when kdb is invoked.
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Please Help me in the Basics...
  • From: Sarith Lambu <sarith.lambu@xxxxxxxxx>
• Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: How to start kernel programming
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: How to start kernel programming
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: How to start kernel programming
  • From: Dariusz Dwornikowski <tdi@xxxxxxxxx>
• Re: How to start kernel programming
  • From: Dariusz Dwornikowski <tdi@xxxxxxxxx>
• Re: How to start kernel programming
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• How to start kernel programming
  • From: Ashok Sharma <aks6d@xxxxxxxxxxx>
• Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Roman I Khimov <rik@xxxxxxxxx>
• Re: Re: Understanding non-preemptive kernel
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Entry function of the LINUX Code
  • From: K S Sandeep <kssandeep@xxxxxxxxx>
• Re: Re: Understanding non-preemptive kernel
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Article - Interrupt Handling Internals
  • From: Gaurav Dhiman <gauravd.chd@xxxxxxxxx>
• Re: MMUless Linux 2.6 for x86
  • From: "Carlo J. Calica" <ccalica@xxxxxxxxx>
• Re: Don't want usb device detection ( sorry, by mistake I asked this question in wrong thread)
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Re: Understanding non-preemptive kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: Re: Understanding non-preemptive kernel
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: maximum kernel addres space and its implication to user space memory allocation
  • From: eliad lubovsky <eliad.lubovsky@xxxxxxxxx>
• Re: debugging usb-storage
  • From: Greg KH <greg@xxxxxxxxx>
• Re: kernel development environment
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• struct bus_type registration in subsystem
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• debugging usb-storage
  • From: Bahadir Balban <bahadir.balban@xxxxxxxxx>
• Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Joe Knapka <jknapka@xxxxxxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: kernel development environment
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: USB read and write operation.. How?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: struct bus_type query!!!!
  • From: Greg KH <greg@xxxxxxxxx>
• Re: maximum kernel addres space and its implication to user space memory allocation
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• TCP congestion window
  • From: Saurabh Jain <jassduec@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: fragmentation && blocks "realloc"
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: Re: Understanding non-preemptive kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Understanding non-preemptive kernel
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: kernel development environment
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: kernel development environment
  • From: "satheesh paul" <satheesh_kernel@xxxxxxxxxxx>
• maximum kernel addres space and its implication to user space memory allocation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• fragmentation && blocks "realloc"
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: kernel development environment
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: System hangs when kdb is invoked.
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: System hangs when kdb is invoked.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: kernel development environment
  • From: "satheesh paul" <satheesh_kernel@xxxxxxxxxxx>
• Re: Understanding non-preemptive kernel
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: kernel development environment
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: System hangs when kdb is invoked.
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: System hangs when kdb is invoked.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: kernel development environment
  • From: "satheesh paul" <satheesh_kernel@xxxxxxxxxxx>
• Re: Understanding non-preemptive kernel
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: kernel development environment
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: USB read and write operation.. How?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• struct bus_type query!!!!
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• USB read and write operation.. How?
  • From: AsHwAtH <itsmeash@xxxxxxxxx>
• Understanding non-preemptive kernel
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• clearing bss segment while booting linux kernel
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• System hangs when kdb is invoked.
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: struct bus_type query!!!!
  • From: Greg KH <greg@xxxxxxxxx>
• Re: struct bus_type query!!!!
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: Don't want usb device detection ( sorry, by mistake I asked this question in wrong thread)
  • From: Neependra Kumar Khare <neependra.khare@xxxxxxxxxxxxxx>
• TCP srtt least count
  • From: Saurabh Jain <jassduec@xxxxxxxxx>
• Re: Don't want usb device detection ( sorry, by mistake I asked this question in wrong thread)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: struct bus_type query!!!!
  • From: Greg KH <greg@xxxxxxxxx>
• Re: #define ... do { ... } while(0) : a corner case
  • From: Olav Kongas <ok@xxxxxxxxxxxxxx>
• struct bus_type query!!!!
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: #define ... do { ... } while(0) : a corner case
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• CHAR DRIVER LOADING PROBLEM
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• #define ... do { ... } while(0) : a corner case
  • From: Olav Kongas <ok@xxxxxxxxxxxxxx>
• Don't want usb device detection ( sorry, by mistake I asked this question in wrong thread)
  • From: Neependra Kumar Khare <neependra.khare@xxxxxxxxxxxxxx>
• Re: Don't want usb device detection
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Don't want usb device detection
  • From: Neependra Kumar Khare <neependra.khare@xxxxxxxxxxxxxx>
• Re: kernel development environment
  • From: "satheesh paul" <satheesh_kernel@xxxxxxxxxxx>
• Re: kernel development environment
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: kernel development environment
  • From: Raseel Bhagat <rabhagat@xxxxxxxxxx>
• Re: kernel development environment
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• kernel development environment
  • From: "satheesh paul" <satheesh_kernel@xxxxxxxxxxx>
• Re: printk??
  • From: eliad lubovsky <eliad.lubovsky@xxxxxxxxx>
• Re: printk??
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• RE: printk??
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• printk??
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: pls explain strcpy() assembly
  • From: Momchil Velikov <velco@xxxxxxxxx>
• Re: Analyzing the filesystem cache
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: pls explain strcpy() assembly
  • From: pankaj chauhan <chauhan_ait@xxxxxxxxxxx>
• Fwd: pls explain strcpy() assembly
  • From: pradeep sawlani <pradep@xxxxxxxxx>
• Re: pls explain strcpy() assembly
  • From: Momchil Velikov <velco@xxxxxxxxx>
• Re: pls explain strcpy() assembly
  • From: Vijay Subramanian <subramanian.vijay@xxxxxxxxx>
• Re: pls explain strcpy() assembly
  • From: Ashwin Rao <ashwin.shirvanthe@xxxxxxxxx>
• pls explain strcpy() assembly
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Wait Variable and Starvation
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Wait Variable and Starvation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: How can we redirect kernel console message to a file
  • From: Neependra Kumar Khare <neependra.khare@xxxxxxxxxxxxxx>
• Wait Variable and Starvation
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxxx>
• Analyzing the filesystem cache
  • From: Hunter Peress <hunterp@xxxxxxxxx>
• Re: writing device driver for USB MOUSE
  • From: sanjay kumar <xs2sanjay@xxxxxxxxx>
• Re: missing a module dependency after boot, rmmod+modprobe fixes it
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: missing a module dependency after boot, rmmod+modprobe fixes it
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• missing a module dependency after boot, rmmod+modprobe fixes it
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: How can we redirect kernel console message to a file
  • From: Vijay Subramanian <subramanian.vijay@xxxxxxxxx>
• Re: writing device driver for USB MOUSE
  • From: Greg KH <greg@xxxxxxxxx>
• Re: about cross referencing
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: writing device driver for USB MOUSE
  • From: mayank rana <mayank_rana_it@xxxxxxxxxxx>
• Re: How can we redirect kernel console message to a file
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: How can we redirect kernel console message to a file
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: How can we redirect kernel console message to a file
  • From: Neependra Kumar Khare <neependra.khare@xxxxxxxxxxxxxx>
• Re: How can we redirect kernel console message to a file
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: Check for kmalloc retrun values
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: writing device driver for USB MOUSE
  • From: "Narendra" <narendradv@xxxxxxxxxxxxx>
• Check for kmalloc retrun values
  • From: Hendrik Post <hendrik@xxxxxxxxxxxx>
• How can we redirect kernel console message to a file
  • From: Neependra Kumar Khare <neependra.khare@xxxxxxxxxxxxxx>
• about cross referencing
  • From: Sarang Radke <radke.s@xxxxxxxxx>
• Re: truncate implementation
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: truncate implementation
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: truncate implementation
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: ktimer not firing ?
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: truncate implementation
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• truncate implementation
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: writing device driver for USB MOUSE
  • From: sanjay kumar <xs2sanjay@xxxxxxxxx>
• Re: writing device driver for USB MOUSE
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Compiling kernel with floating point support
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Re: Compiling kernel with floating point support
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Compiling kernel with floating point support
  • From: Saurabh Jain <jassduec@xxxxxxxxx>
• Re: computing/comparing object size
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: computing/comparing object size
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• computing/comparing object size
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: writing device driver for USB MOUSE
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Fwd: git usage question
  • From: Greg KH <greg@xxxxxxxxx>
• Fwd: git usage question
  • From: Jan Koss <kossjan@xxxxxxxxx>
• writing device driver for USB MOUSE
  • From: mayank rana <mayank_rana_it@xxxxxxxxxxx>
• ktimer not firing ?
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• status return confusion!!!
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Reading or mmaping from /dev/kmem
  • From: embedded linux developer developer <em_li_de@xxxxxxxxxxx>
• Re: Question regarding packet socket
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Question regarding packet socket
  • From: Ram Krishna <dinu.krishna@xxxxxxxxx>
• Access to tcp_protocol handler (for kernel >= 2.6.10)
  • From: Saurabh Jain <jassduec@xxxxxxxxx>
• Access to tcp protocol handler
  • From: Saurabh Jain <jassduec@xxxxxxxxx>
• Re: Kernel Socket APIs
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: git usage question
  • From: Greg KH <greg@xxxxxxxxx>
• ST_READY status confusion in st.c
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• git usage question
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: Driver initializaton order
  • From: devzero@xxxxxx
• Re: /proc/interrupts
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: /proc/interrupts
  • From: Vijay Subramanian <subramanian.vijay@xxxxxxxxx>