Linux Kernel Newbies

• Thread Index

• Re: how does a filesystem submit a block IO request
  • From: Da Zheng <zhengda1936@xxxxxxxxx>
• from kernel newbie who wishes to help maintain wiki
  • From: Fabian Marin <fmg134s@xxxxxxxxx>
• color listing on serial terminal - Perhaps a silly question
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Using the same serial port for both serial console and kgdb debugging
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: I/O and memory barriers
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: I/O and memory barriers
  • From: Pei Lin <telent997@xxxxxxxxx>
• how does a filesystem submit a block IO request
  • From: Da Zheng <zhengda1936@xxxxxxxxx>
• Re: how does a filesystem submit a block IO request
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Fixed quantum scheduling
  • From: Vimal <j.vimal@xxxxxxxxx>
• Re: Using the same serial port for both serial console and kgdb debugging
  • From: luca ellero <lroluk@xxxxxxxxx>
• Using the same serial port for both serial console and kgdb debugging
  • From: Paul Fisher <r01.gjk@xxxxxxxxx>
• Re: updating online free-electrons docs -- feel free to lend a hand
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: updating online free-electrons docs -- feel free to lend a hand
  • From: Shaz <shazalive@xxxxxxxxx>
• Re: updating online free-electrons docs -- feel free to lend a hand
  • From: Shaz <shazalive@xxxxxxxxx>
• updating online free-electrons docs -- feel free to lend a hand
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Mapping a specific physical address into kernel VA space, in interrupt context
  • From: Mayank Kaushik <mayank.utexas@xxxxxxxxx>
• Query regarding "loops_per_jiffy"
  • From: Smital Desai <Smital.Desai@xxxxxxxxxxxxxxx>
• Re: Mapping a specific physical address into kernel VA space, in interrupt context
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Mapping a specific physical address into kernel VA space, in interrupt context
  • From: Mayank Kaushik <mayank.utexas@xxxxxxxxx>
• Re: Mapping a specific physical address into kernel VA space, in interrupt context
  • From: Mayank Kaushik <mayank.utexas@xxxxxxxxx>
• Mapping a specific physical address into kernel VA space, in interrupt context
  • From: Mayank Kaushik <mayank.utexas@xxxxxxxxx>
• Re: building 32 bit user mode linux in 64 bit environment
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: basic ques --- installation from rpm and source
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: basic ques --- installation from rpm and source
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: basic ques --- installation from rpm and source
  • From: amol verule <amol.debian@xxxxxxxxx>
• [Fwd: Re: I/O and memory barriers]
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: basic ques --- installation from rpm and source
  • From: Neependra Khare <neependra.khare@xxxxxxxxx>
• basic ques --- installation from rpm and source
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: building 32 bit user mode linux in 64 bit environment
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: building 32 bit user mode linux in 64 bit environment
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: building 32 bit user mode linux in 64 bit environment
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: building 32 bit user mode linux in 64 bit environment
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: get_pid problem
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• building 32 bit user mode linux in 64 bit environment
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: free electrons is now on twitter
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: free electrons is now on twitter
  • From: Shaz <shazalive@xxxxxxxxx>
• free electrons is now on twitter
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: how to request new kernel function
  • From: Dexter <dexter@xxxxxxxxx>
• Re: how to request new kernel function
  • From: Ralph Blach <rcblach@xxxxxxxxxxxxx>
• how to request new kernel function
  • From: Ralph Blach <rcblach@xxxxxxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: how to request new kernel function
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: Balachandar <bala1486@xxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: Balachandar <bala1486@xxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: Balachandar <bala1486@xxxxxxxxx>
• Re: error in loading a module in 2.6.34
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• error in loading a module in 2.6.34
  • From: Balachandar <bala1486@xxxxxxxxx>
• Re: how to request new kernel function
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• how to request new kernel function
  • From: Ralph Blach <rcblach@xxxxxxxxxxxxx>
• Re: some question about building kernel
  • From: Vineet Agarwal <vineetvagarwal8@xxxxxxxxx>
• Re: get_pid problem
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Re: get_pid problem
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Re: some question about building kernel
  • From: loody <miloody@xxxxxxxxx>
• Re: some question about building kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: get_pid problem
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• some question about building kernel
  • From: loody <miloody@xxxxxxxxx>
• Re: where is the request_irq in 2.6.30?
  • From: loody <miloody@xxxxxxxxx>
• Re: obtaining linux kernel command line from a module
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: obtaining linux kernel command line from a module
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• get_pid problem
  • From: Shyam Burkule <shyam.burkule@xxxxxxxxx>
• Re: obtaining linux kernel command line from a module
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: obtaining linux kernel command line from a module
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: obtaining linux kernel command line from a module
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: obtaining linux kernel command line from a module
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• obtaining linux kernel command line from a module
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: obtaining linux kernel command line from a module
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• NFS Export of RAMDisk
  • From: Tharindu Rukshan Bamunuarachchi <btharindu@xxxxxxxxx>
• Re: what's the most up-to-date tutorial on writing USB drivers?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: what's the most up-to-date tutorial on writing USB drivers?
  • From: leo liang <leoliang9@xxxxxxxxx>
• Re: where is the request_irq in 2.6.30?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Supporting async IO in block device driver.
  • From: Prasad Joshi <prasadjoshi124@xxxxxxxxx>
• Fwd: where is the request_irq in 2.6.30?
  • From: loody <miloody@xxxxxxxxx>
• where is the request_irq in 2.6.30?
  • From: loody <miloody@xxxxxxxxx>
• what's the most up-to-date tutorial on writing USB drivers?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• ip_local_port_range
  • From: Tharindu Rukshan Bamunuarachchi <btharindu@xxxxxxxxx>
• Re: Getting driver module name from device node?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• anyone know new network drivers receiving architecture
  • From: sri ram vemulpali <kishore.kernelmm.dev@xxxxxxxxx>
• Re: retaining messages from previous boot - /var/log/messages OR /var/log/boot.log
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: retaining messages from previous boot - /var/log/messages OR /var/log/boot.log
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Getting driver module name from device node?
  • From: Mayank Kaushik <mayank.utexas@xxxxxxxxx>
• Re: About struct blockgroup_lock
  • From: Ryan Wang <openspace.wang@xxxxxxxxx>
• Re: About struct blockgroup_lock
  • From: Ryan Wang <openspace.wang@xxxxxxxxx>
• I/O and memory barriers
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: try_module_get and module_put usage
  • From: vikas chauhan <presentisgood@xxxxxxxxx>
• Re: try_module_get and module_put usage
  • From: vikas chauhan <presentisgood@xxxxxxxxx>
• Re: About struct blockgroup_lock
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Re: try_module_get and module_put usage
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Re: retaining messages from previous boot - /var/log/messages OR /var/log/boot.log
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: try_module_get and module_put usage
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• try_module_get and module_put usage
  • From: vikas chauhan <presentisgood@xxxxxxxxx>
• About struct blockgroup_lock
  • From: Ryan Wang <openspace.wang@xxxxxxxxx>
• Re: retaining messages from previous boot - /var/log/messages OR /var/log/boot.log
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: retaining messages from previous boot - /var/log/messages OR /var/log/boot.log
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: retaining messages from previous boot - /var/log/messages OR /var/log/boot.log
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: retaining messages from previous boot - /var/log/messages OR /var/log/boot.log
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• retaining messages from previous boot - /var/log/messages OR /var/log/boot.log
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: Key pressed
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Key pressed
  • From: Niko Rosvall <niko@xxxxxxxxxxxx>
• Re: Completely Debug Kernel
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• about io_context
  • From: "kernel.niko" <kernel.niko@xxxxxxxxx>
• Re: Completely Debug Kernel
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: Completely Debug Kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Completely Debug Kernel
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: Bounce buffer ?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Bounce buffer ?
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• How the kernel gives seg. fault for a scenario like this?
  • From: Balachandar <bala1486@xxxxxxxxx>
• Re: pthread with SCHED_FIFO calling select() causing system deadlock
  • From: Mohamad Tayssir Alkowatly <idoit.ief@xxxxxxxxx>
• Re: Doubts in System call mechanism in linux
  • From: "Understanding Linux !!!" <havefunwhileulearn@xxxxxxxxx>
• Re: Doubts in System call mechanism in linux
  • From: matthias <mensch0815@xxxxxxxxxxxxxx>
• Re: Doubts in System call mechanism in linux
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: Doubts in System call mechanism in linux
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Doubts in System call mechanism in linux
  • From: Balachandar <bala1486@xxxxxxxxx>
• Re: current state of kgdb in kernel?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• wiki spam prevention
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: current state of kgdb in kernel?
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• current state of kgdb in kernel?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: hi -- i was also a newbie once--thanks list.
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: hi -- i was also a newbie once--thanks list.
  • From: cheng chen <freakrobot@xxxxxxx>
• Re: hi -- i was also a newbie once--thanks list.
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: hi -- i was also a newbie once--thanks list.
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: hi -- i was also a newbie once--thanks list.
  • From: Tapas Mishra <mightydreams@xxxxxxxxx>
• Re: hi -- i was also a newbie once--thanks list.
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: hi -- i was also a newbie once--thanks list.
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• are there any screen casts available for developing device drivers ?
  • From: Tapas Mishra <mightydreams@xxxxxxxxx>
• Re: hi -- i was also a newbie once--thanks list.
  • From: Steven Zhou <lullaby2005@xxxxxxxxx>
• hi -- i was also a newbie once--thanks list.
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• understanding Block I/O
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: trace_block_remap ?
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• trace_block_remap ?
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• disable irq in Linux
  • From: Da Zheng <zhengda1936@xxxxxxxxx>
• Re: pthread with SCHED_FIFO calling select() causing system deadlock
  • From: Mohamad Tayssir Alkowatly <idoit.ief@xxxxxxxxx>
• Re: pthread with SCHED_FIFO calling select() causing system deadlock
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: System memory increased while process is running is not released back upon process exit
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re:System memory increased while process is running is not released back upon process exit
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• Linux IB Failover (with Verbs)
  • From: Tharindu Rukshan Bamunuarachchi <btharindu@xxxxxxxxx>
• Re: Fwd: System memory increased while process is running is not released back upon process exit
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• pthread with SCHED_FIFO calling select() causing system deadlock
  • From: Mohamad Tayssir Alkowatly <idoit.ief@xxxxxxxxx>
• USB HID gadget driver
  • From: Vivek <prabhakar.vivek@xxxxxxxxx>
• Need info: converting time in seconds from UTC to local time
  • From: san deep <sandeep.albur@xxxxxxxxx>
• Re: System memory increased while process is running is not released back upon process exit
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• Fwd: System memory increased while process is running is not released back upon process exit
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Shared buffer between user and kernel space
  • From: Arun KS <getarunks@xxxxxxxxx>
• Re: System memory increased while process is running is not released back upon process exit
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• Re: Stack Tracing using Ftrace
  • From: Neependra Khare <neependra.khare@xxxxxxxxx>
• Re: System memory increased while process is running is not released back upon process exit
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• Shared buffer between user and kernel space
  • From: Balachandar <bala1486@xxxxxxxxx>
• Re: Stack Tracing using Ftrace
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: System memory increased while process is running is not released back upon process exit
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• System memory increased while process is running is not released back upon process exit
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• Stack Tracing using Ftrace
  • From: Neependra Khare <neependra.khare@xxxxxxxxx>
• Re: read contents from user memory area from a module
  • From: Yang Fangkai <wolfgang.yang@xxxxxxxxx>
• Re: read contents from user memory area from a module
  • From: Sangman Kim <nemonemo@xxxxxxxxxxxxx>
• Re: read contents from user memory area from a module
  • From: Yang Fangkai <wolfgang.yang@xxxxxxxxx>
• Re: read contents from user memory area from a module
  • From: Sangman Kim <nemonemo@xxxxxxxxxxxxx>
• read contents from user memory area from a module
  • From: Yang Fangkai <wolfgang.yang@xxxxxxxxx>
• Re: repetitive log message
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Doubts in fast system call
  • From: Balachandar <bala1486@xxxxxxxxx>
• RE: Not able to boot Linux-2.6.33.2
  • From: "Bruce Blinn" <bruce.blinn@xxxxxxxxx>
• Re: about copy_from_user().
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• repetitive log message
  • From: mosta.me@xxxxxxxxxxxxxx
• Re: Not able to boot Linux-2.6.33.2
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• about copy_from_user().
  • From: "calix" <calix.chen@xxxxxxxxx>
• Re: question about get_user
  • From: mayank rana <mayank_rana_it@xxxxxxxxxxx>
• Timekeeping problem: time runs too fast
  • From: Stephane Lambert <stephane.lambert@xxxxxxxxxx>
• Re: question about get_user
  • From: Yang Fangkai <wolfgang.yang@xxxxxxxxx>
• Re: question about get_user
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: question about get_user
  • From: Yang Fangkai <wolfgang.yang@xxxxxxxxx>
• can someone tell me why should i use PAGE_ALIGN after kmalloc?
  • From: "calix" <calix.chen@xxxxxxxxx>
• Re: question about get_user
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: question about get_user
  • From: Yang Fangkai <wolfgang.yang@xxxxxxxxx>
• Re: question about get_user
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: Not able to boot Linux-2.6.33.2
  • From: Mukesh Yadav <mukesh224@xxxxxxxxx>
• Re: question about get_user
  • From: Yang Fangkai <wolfgang.yang@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: question about get_user
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• question about get_user
  • From: Yang Fangkai <wolfgang.yang@xxxxxxxxx>
• Re: how to call system call from kernelspace
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: how to call system call from kernelspace
  • From: rahul patil <rahul.deshmukhpatil@xxxxxxxxx>
• Re: how to call system call from kernelspace
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: how to call system call from kernelspace
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: Dynamic Kernel Module Section Addresses
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Dynamic Kernel Module Section Addresses
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: Not able to boot Linux-2.6.33.2
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Not able to boot Linux-2.6.33.2
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Re: Not able to boot Linux-2.6.33.2
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Not able to boot Linux-2.6.33.2
  • From: Mukesh Yadav <mukesh224@xxxxxxxxx>
• Re: Not able to boot Linux-2.6.33.2
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Not able to boot Linux-2.6.33.2
  • From: Mukesh Yadav <mukesh224@xxxxxxxxx>
• Re: Linux SMP Test Cases
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: how to call system call from kernelspace
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: how to call system call from kernelspace
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: how to call system call from kernelspace
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: how to call system call from kernelspace
  • From: Mahaveer Darade <mah.darade@xxxxxxxxx>
• how to call system call from kernelspace
  • From: rahul patil <rahul.deshmukhpatil@xxxxxxxxx>
• Re: Unable to change IRQ affinity
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Linux SMP Test Cases
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Unable to change IRQ affinity
  • From: Abraham Arce <abraham.arce.moreno@xxxxxxxxx>
• Re: Linux SMP Test Cases
  • From: Abraham Arce <abraham.arce.moreno@xxxxxxxxx>
• Re: best way to read kernel code
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: best way to read kernel code
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: best way to read kernel code
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: best way to read kernel code
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Re: best way to read kernel code
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Re: best way to read kernel code
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• delay calibration init/calibrate.c
  • From: Tapas Mishra <mightydreams@xxxxxxxxx>
• Re: best way to read kernel code
  • From: Mohammed Gamal <m.gamal005@xxxxxxxxx>
• Re: best way to read kernel code
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: best way to read kernel code
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: best way to read kernel code
  • From: thalib <hmthalib@xxxxxxxxx>
• Re: best way to read kernel code
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Re: best way to read kernel code
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• best way to read kernel code
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: Read block level storage via kernel modules
  • From: Naval <naval.dudhoria@xxxxxxxxx>
• Re: Read block level storage via kernel modules
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Read block level storage via kernel modules
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Read block level storage via kernel modules
  • From: Greg KH <greg@xxxxxxxxx>
• bootmem_data_t and __initdata qualifier
  • From: Himanshu Aggarwal <lkml.himanshu@xxxxxxxxx>
• Re: Read block level storage via kernel modules
  • From: Leon Romanovsky <leon@xxxxxxx>
• question about init/calibrate.c
  • From: Tapas Mishra <mightydreams@xxxxxxxxx>
• Re: Read block level storage via kernel modules
  • From: Greg KH <greg@xxxxxxxxx>
• Re: hooking system call.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: mmap and stacks
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: mmap and stacks
  • From: Andrei Matei <andreimatei1@xxxxxxxxx>
• Re: mmap and stacks
  • From: Andrei Matei <andreimatei1@xxxxxxxxx>
• Re: mmap and stacks
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: mmap and stacks
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: New to Kernel programming and device drivers
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• New to Kernel programming and device drivers
  • From: Tharanga Abeyseela <tharanga.abeyseela@xxxxxxxxx>
• Re: mmap and stacks
  • From: Andrei Matei <andreimatei1@xxxxxxxxx>
• Re: mmap and stacks
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: mmap and stacks
  • From: Dragos Tatulea <dragos.tatulea@xxxxxxxxx>
• Re: hlist_for_each_entry
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: mmap and stacks
  • From: Dragos Tatulea <dragos.tatulea@xxxxxxxxx>
• Re: mmap and stacks
  • From: Dragos Tatulea <dragos.tatulea@xxxxxxxxx>
• Re: mmap and stacks
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: How to deploy lttng on an embedded system
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: mmap and stacks
  • From: Andrei Matei <andreimatei1@xxxxxxxxx>
• Re: mmap and stacks
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: How to deploy lttng on an embedded system
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Researching ATA TRIM command
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: How to deploy lttng on an embedded system
  • From: jerome zh <jeromezhr@xxxxxxxxx>
• hlist_for_each_entry
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• mmap and stacks
  • From: Andrei Matei <andreimatei1@xxxxxxxxx>
• How to deploy lttng on an embedded system
  • From: jerome zh <jeromezhr@xxxxxxxxx>
• Re: device driver debugging : help required
  • From: ajay.hotchandani@xxxxxxxxxxxxxx
• Re: why INITIAL_JIFFIES is -300 * HZ?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: prefetch(x)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: prefetch(x)
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: why INITIAL_JIFFIES is -300 * HZ?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: [OOT] System forensic
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: why INITIAL_JIFFIES is -300 * HZ?
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Problem with applying Gcov tool to kernel module
  • From: boy tlay <tlayboy@xxxxxxxxx>
• why INITIAL_JIFFIES is -300 * HZ?
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: device driver debugging : help required
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: device driver debugging : help required
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: [OOT] System forensic
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• System forensic
  • From: Kousik Maiti <maiti.kousik@xxxxxxxxx>
• Re: suggestion on writing driver
  • From: Tapas Mishra <mightydreams@xxxxxxxxx>
• Re: Question on SDIO driver
  • From: selvamuthukumar v <v.selvamuthukumar@xxxxxxxxx>
• Re: suggestion on writing driver
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• device driver debugging : help required
  • From: yogeshwar sonawane <yogyas@xxxxxxxxx>
• Re: Difference between various superblock methods
  • From: Himanshu Aggarwal <lkml.himanshu@xxxxxxxxx>
• suggestion on writing driver
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Question on SDIO driver
  • From: dinesh bhaskar <pdineshb@xxxxxxxxx>
• Re: prefetch(x)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• prefetch(x)
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: can you turn off compile-time optimization entirely?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: can you turn off compile-time optimization entirely?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Difference between various superblock methods
  • From: Neependra Khare <neependra.khare@xxxxxxxxx>
• Re: can you turn off compile-time optimization entirely?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• can you turn off compile-time optimization entirely?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Difference between various superblock methods
  • From: Himanshu Aggarwal <lkml.himanshu@xxxxxxxxx>
• Re: how to develop against linux-next
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• Re: GPT fdisk
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• RE: Researching ATA TRIM command
  • From: Bill Weiler <weilerb@xxxxxxxxxxx>
• Re: Researching ATA TRIM command
  • From: Simon Kitching <simon.kitching@xxxxxxxxxx>
• Researching ATA TRIM command
  • From: Bill Weiler <weilerb@xxxxxxxxxxx>
• Re: Struct Super_Operations Changes in 2.6.25 Kernel
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: Memory is not becoming available even after freeing it.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Query regarding memory allocation techniques of kernel
  • From: Himanshu Aggarwal <lkml.himanshu@xxxxxxxxx>
• Re: Struct Super_Operations Changes in 2.6.25 Kernel
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Struct Super_Operations Changes in 2.6.25 Kernel
  • From: Abhijit Pawar <abhijitcpawar@xxxxxxxxx>
• Re: Memory is not becoming available even after freeing it.
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• Re: linux0.01 build failed
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: linux0.01 build failed
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: linux0.01 build failed
  • From: Manish Regmi <regmi.manish@xxxxxxxxx>
• Re: linux0.01 build failed
  • From: Manish Regmi <regmi.manish@xxxxxxxxx>
• linux0.01 build failed
  • From: Sameer Rahmani <lxsameer@xxxxxxxxx>
• Re: Memory is not becoming available even after freeing it.
  • From: Manish Regmi <regmi.manish@xxxxxxxxx>
• Re: Memory is not becoming available even after freeing it.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Memory is not becoming available even after freeing it.
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• Re: doubt regarding mmap/mmap2 system call and implementation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: doubt regarding mmap/mmap2 system call and implementation
  • From: Dragos Tatulea <dragos.tatulea@xxxxxxxxx>
• Re: FATAL:modpost: GPL-incompatible module testdr.ko uses GPL-only symbol ‘lockdep_init_map’
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• FATAL:modpost: GPL-incompatible module testdr.ko uses GPL-only symbol ‘lockdep_init_map’
  • From: san deep <sandeep.albur@xxxxxxxxx>
• Re: __read_mostly
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: __read_mostly
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: __read_mostly
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Unable to change IRQ affinity
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: doubt regarding mmap/mmap2 system call and implementation
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: how to develop against linux-next
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: kernel hash function algorithm
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• kernel hash function algorithm
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: data sheet for SATA drive
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: data sheet for SATA drive
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: data sheet for SATA drive
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: data sheet for SATA drive
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: doubt regarding mmap/mmap2 system call and implementation
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: doubt regarding mmap/mmap2 system call and implementation
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• doubt regarding mmap/mmap2 system call and implementation
  • From: Himanshu Aggarwal <lkml.himanshu@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Himanshu Aggarwal <lkml.himanshu@xxxxxxxxx>
• Re: how to develop against linux-next
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: how to hook a syscall in kernel 2.6
  • From: George Kadianakis <desnacked@xxxxxxxxx>
• Re: how to develop against linux-next
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• how to develop against linux-next
  • From: vorad <vorad.1100@xxxxxxxxx>
• Re: list query
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: list query
  • From: Cédric Augonnet <cedric.augonnet@xxxxxxxxx>
• Re: BH_Boundary flag
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: delete from hlist ???
  • From: ZhangMeng <jammy.linux@xxxxxxxxx>
• Re: delete from hlist ???
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: BH_Boundary flag
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: BH_Boundary flag
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• BH_Boundary flag
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• delete from hlist ???
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• list query
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Nobin Mathew <nobin.mathew@xxxxxxxxx>
• Re: how to hook a syscall in kernel 2.6
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Unable to change IRQ affinity
  • From: Abraham Arce <abraham.arce.moreno@xxxxxxxxx>
• Re: how to hook a syscall in kernel 2.6
  • From: "Elvis Y. Tamayo Moyares" <etmoyares@xxxxxxxxxx>
• Re: how to hook a syscall in kernel 2.6
  • From: Sangman Kim <nemonemo@xxxxxxxxx>
• how to hook a syscall in kernel 2.6
  • From: "Elvis Y. Tamayo Moyares" <etmoyares@xxxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Himanshu Aggarwal <lkml.himanshu@xxxxxxxxx>
• Re: __read_mostly
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: __read_mostly
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: data sheet for SATA drive
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Xianghua Xiao <xiaoxianghua@xxxxxxxxx>
• Re: hlist_node v/s list_head
  • From: Neependra Khare <neependra.khare@xxxxxxxxx>
• hlist_node v/s list_head
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: need to get blocks per group in user space
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• __read_mostly
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: need to get blocks per group in user space
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: need to get blocks per group in user space
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: need to get blocks per group in user space
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• need to get blocks per group in user space
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Siddu <siddu.sjce@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: data sheet for SATA drive
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Youngwhan Song <breadncup@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: why choose 896MB to the start point of ZONE_HIGHMEM
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• why choose 896MB to the start point of ZONE_HIGHMEM
  • From: hayfeng Lee <teklife.kernel@xxxxxxxxx>
• Re: data sheet for SATA drive
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Google Summer of Code 2010 / Lunatik
  • From: Lourival Vieira Neto <lourival.neto@xxxxxxxxx>
• Re: Google Summer of Code 2010 / Lunatik
  • From: Lourival Vieira Neto <lourival.neto@xxxxxxxxx>
• Re: Google Summer of Code 2010 / Lunatik
  • From: Gergely Buday <gbuday@xxxxxxxxx>
• Re: Google Summer of Code 2010 / Lunatik
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Can we remove the Zone_DMA?
  • From: Adam Jiang <jiang.adam@xxxxxxxxx>
• Re: Google Summer of Code 2010 / Lunatik
  • From: Lourival Vieira Neto <lourival.neto@xxxxxxxxx>
• data sheet for SATA drive
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: registers and cache memory
  • From: Nobin Mathew <nobin.mathew@xxxxxxxxx>
• Re: epoll on netlink sockets
  • From: Harishkumar V <harishpresent@xxxxxxxxx>
• Re: epoll on netlink sockets
  • From: Radhesh Kamath <rmk.list@xxxxxxxxx>
• Re: epoll on netlink sockets
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• epoll on netlink sockets
  • From: Radhesh Kamath <rmk.list@xxxxxxxxx>
• Re: Google Summer of Code 2010 / Lunatik
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Memory usage analysis
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Google Summer of Code 2010 / Lunatik
  • From: Lourival Vieira Neto <lourival.neto@xxxxxxxxx>
• Re: registers and cache memory
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: registers and cache memory
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: registers and cache memory
  • From: Nobin Mathew <nobin.mathew@xxxxxxxxx>
• Re: registers and cache memory
  • From: Nobin Mathew <nobin.mathew@xxxxxxxxx>
• Re: registers and cache memory
  • From: Nobin Mathew <nobin.mathew@xxxxxxxxx>
• Re: registers and cache memory
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: registers and cache memory
  • From: loody <miloody@xxxxxxxxx>
• Netlink Socket in Linux Kernel
  • From: Harishkumar V <harishpresent@xxxxxxxxx>
• Re: Memory usage analysis
  • From: Anand Raj Manickam <anandrm@xxxxxxxxx>
• registers and cache memory
  • From: Nobin Mathew <nobin.mathew@xxxxxxxxx>
• Re: Memory usage analysis
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Memory usage analysis
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Memory usage analysis
  • From: Anand Raj Manickam <anandrm@xxxxxxxxx>
• Bugzila help
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• Re: tutorials
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: tutorials
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: tutorials
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Re: tutorials
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• RE: tutorials
  • From: Smital Desai <Smital.Desai@xxxxxxxxxxxxxxx>
• Re: tutorials
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: tutorials
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• tutorials
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Re: Becoming a kernel contributor: is it still possible?
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• Re: why use spin_lock_{irq, irqsave}()
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: why use spin_lock_{irq, irqsave}()
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• 500kbps serial port
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• Re: How to begin ?
  • From: L. Alberto Giménez <lagimenez@xxxxxxxxx>
• why use spin_lock_{irq, irqsave}()
  • From: अनुज <anuj01@xxxxxxxxx>
• Re: Networking project
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Networking project
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: How to begin ?
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: test
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• How to begin ?
  • From: siddharth srivastava <akssps011@xxxxxxxxx>
• Re: Student Looking For Mentor
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Bootmem failed.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Bootmem failed.
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: cross compile error 2.6.28(about netfilter)
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Bootmem failed.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Bootmem failed.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Networking project
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Networking project
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• starting a new device driver: Issues, which should be considered?
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• cross compile error 2.6.28(about netfilter)
  • From: Shawn <citypw@xxxxxxxxx>
• Networking project
  • From: Onkar Mahajan <kern.devel@xxxxxxxxx>
• Student Looking For Mentor
  • From: Chandrakant Kumar <k.03chandra@xxxxxxxxx>
• Re: kernel compile failing on fedora 12
  • From: vorad <vorad.1100@xxxxxxxxx>
• Re: test
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• test
  • From: अनुज <anuj01@xxxxxxxxx>
• Bootmem failed.
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: Best way to communicate to a device.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Make error in linux device driver
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Best way to communicate to a device.
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• Make error in linux device driver
  • From: Gaurav Soni <grvlinux@xxxxxxxxx>
• Re: a conceptual confusion -- loop device
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Fwd: How to set up a debugging environment.
  • From: "become who you are born to be.... Chaitannya mahatme" <chaitannya@xxxxxxxxx>
• Re: How to set up a debugging environment.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: a conceptual confusion -- loop device
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: a conceptual confusion -- loop device
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: a conceptual confusion -- loop device
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• napi + dma ?
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: Help needed for setup a simulation environment.
  • From: Thomas Rega <mail@xxxxxxxxxx>
• Re: Help needed for setup a simulation environment.
  • From: Siddu <siddu.sjce@xxxxxxxxx>
• Re: Help needed for setup a simulation environment.
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: Help needed for setup a simulation environment.
  • From: Paraneetharan Chandrasekaran <paraneetharanc@xxxxxxxxx>
• Re: How to set up a debugging environment.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Help needed for setup a simulation environment.
  • From: Tonny Adhi Sabastian <tonny.adhi@xxxxxxxx>
• How to set up a debugging environment.
  • From: "become who you are born to be.... Chaitannya mahatme" <chaitannya@xxxxxxxxx>
• Re: Help needed for setup a simulation environment.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Becoming a kernel contributor: is it still possible?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Becoming a kernel contributor: is it still possible?
  • From: Paul Fisher <r01.gjk@xxxxxxxxx>
• Re: Help needed for setup a simulation environment.
  • From: Pavan Kandepet <pavankp@xxxxxxxxx>
• Help needed for setup a simulation environment.
  • From: Paraneetharan Chandrasekaran <paraneetharanc@xxxxxxxxx>
• what's with DECLARE_KFIFO, INIT_KFIFO, DEFINE_KFIFO?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Unhandled kernel unaligned access
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Kernel tunnel driver and routing?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Unhandled kernel unaligned access
  • From: Anoop <anoop.chargotra@xxxxxxxxx>
• Re: Kernel tunnel driver and routing?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Unhandled kernel unaligned access
  • From: Anoop <anoop.chargotra@xxxxxxxxx>
• USB uml support
  • From: Asim <linkasim@xxxxxxxxx>
• Re: a conceptual confusion -- loop device
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: a conceptual confusion -- loop device
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: a conceptual confusion -- loop device
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• a conceptual confusion -- loop device
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: BUG: scheduling while atomic
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• Re: BUG: scheduling while atomic
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• Re: Kernel tunnel driver and routing?
  • From: "Robin Gilks" <g8ecj@xxxxxxxxx>
• Re: Kernel tunnel driver and routing?
  • From: "Robin Gilks" <g8ecj@xxxxxxxxx>
• Re: latest kernel compile-- system panic
  • From: Shreyansh Jain <shrey.linux@xxxxxxxxx>
• Re: Linux Version - 32 bit OR 64 bit
  • From: Shreyansh Jain <shrey.linux@xxxxxxxxx>
• Re: Linux 2.6.32.9 kernel compilation issue on Redhat 5.4
  • From: Shreyansh Jain <shrey.linux@xxxxxxxxx>
• Re: BUG: scheduling while atomic
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• Re: Linux 2.6.32.9 kernel compilation issue on Redhat 5.4
  • From: Belisko Marek <marek.belisko@xxxxxxxxx>
• Re: Kernel tunnel driver and routing?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Linux 2.6.32.9 kernel compilation issue on Redhat 5.4
  • From: san deep <sandeep.albur@xxxxxxxxx>
• Re: BUG: scheduling while atomic
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: BUG: scheduling while atomic
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• RE: User Level Threads implementation by Linux kernel
  • From: "Gaurav Dhiman" <gaurav.dhiman@xxxxxxxxxxx>
• Re: User Level Threads implementation by Linux kernel
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• Re: BUG: scheduling while atomic
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Allocating memory with spinlock held
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: User Level Threads implementation by Linux kernel
  • From: Sangman Kim <nemonemo@xxxxxxxxx>
• Re: Allocating memory with spinlock held
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• User Level Threads implementation by Linux kernel
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• Kernel tunnel driver and routing?
  • From: "Robin Gilks" <g8ecj@xxxxxxxxx>
• Allocating memory with spinlock held
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• User Level Threads implementation by Linux kernel
  • From: ravikumar <ravikumar.vallabhu@xxxxxxxxx>
• BUG: scheduling while atomic
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• Re: Allocating memory with spinlock held
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Allocating memory with spinlock held
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: UTS Version
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• UTS Version
  • From: Arigead <captain.deadly@xxxxxxxxx>
• Re: Are there any efficient methods to manage andriod code at normal kernel line?
  • From: Peter Chen <hzpeterchen@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• Re: Are there any efficient methods to manage andriod code at normal kernel line?
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxx>
• Re: [ANNOUNCE] Online Hierarchical Storage Manager (OHSM v1.2)
  • From: Jan Kara <jack@xxxxxx>
• Re: Linux Version - 32 bit OR 64 bit
  • From: Denis Borisevich <dennisfen@xxxxxxxxx>
• Re: [ANNOUNCE] Online Hierarchical Storage Manager (OHSM v1.2)
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: sysrq problem
  • From: Ram Sharma <ram99.sharma@xxxxxxxxx>
• Re: [ANNOUNCE] Online Hierarchical Storage Manager (OHSM v1.2)
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Linux Version - 32 bit OR 64 bit
  • From: Punit Kumar Jain <punitkr.jain@xxxxxxxxx>
• Re: Linux Version - 32 bit OR 64 bit
  • From: Neependra Khare <neependra.khare@xxxxxxxxx>
• Re: sysrq problem
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: sysrq problem
  • From: Ram Sharma <ram99.sharma@xxxxxxxxx>
• Re: sysrq problem
  • From: Punit Kumar Jain <punitkr.jain@xxxxxxxxx>
• Re: sysrq problem
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• RE: Linux Version - 32 bit OR 64 bit
  • From: "Saquib Imam" <saquib.imam@xxxxxxxxx>
• Linux Version - 32 bit OR 64 bit
  • From: Ajay Jain <ajay050@xxxxxxxxx>
• Re: pcap_inject over ethernet
  • From: Anand Raj Manickam <anandrm@xxxxxxxxx>
• sysrq problem
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Are there any efficient methods to manage andriod code at normal kernel line?
  • From: Peter Chen <hzpeterchen@xxxxxxxxx>
• Re: Copyright question
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Copyright question
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Copyright question
  • From: Ram Sharma <ram99.sharma@xxxxxxxxx>
• Re: Copyright question
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: [ANNOUNCE] Online Hierarchical Storage Manager (OHSM v1.2)
  • From: Dmitry Monakhov <dmonakhov@xxxxxxxxxx>
• Copyright question
  • From: Ram Sharma <ram99.sharma@xxxxxxxxx>
• [ANNOUNCE] Online Hierarchical Storage Manager (OHSM v1.2)
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Absolute Path from linux_dirent64
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Question about events
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• RE: Question about events
  • From: Bill Weiler <weilerb@xxxxxxxxxxx>
• Re: Question about events
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Question about events
  • From: Bill Weiler <weilerb@xxxxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: How to build static module
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: How to build static module
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• How to build static module
  • From: san deep <sandeep.albur@xxxxxxxxx>
• Re: How to control module loading at boot time during installation of linux?
  • From: shenghui <crosslonelyover@xxxxxxxxx>
• Re: How to control module loading at boot time during installation of linux?
  • From: shenghui <crosslonelyover@xxxxxxxxx>
• Re: How to control module loading at boot time during installation of linux?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• How to control module loading at boot time during installation of linux?
  • From: shenghui <crosslonelyover@xxxxxxxxx>
• Re: linux booting
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxx>
• Re: pcap_inject over ethernet
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• pcap_inject over ethernet
  • From: Vasilis Liaskovitis <vliaskov@xxxxxxxxx>
• Implementation of UDP en/de-capsulation of ESP packets?
  • From: Calvin Johnson <linux.cj@xxxxxxxxx>
• Re: implicit declaration of function ‘KBUILD_STR’
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• implicit declaration of function ‘KBUILD_STR’
  • From: Martin Knappe <martin.knappe@xxxxxxxxx>
• list etiquette
  • From: Rik van Riel <riel@xxxxxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: Schedule() call in driver context.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: schedule
  • From: Joshua Lock <josh@xxxxxxxxxxxxxxx>
• schedule
  • From: sri ram vemulpali <kishore.kernelmm.dev@xxxxxxxxx>
• Re: ieee papers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: ieee papers
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: ieee papers
  • From: Krushnaal Pai <krisonearth@xxxxxxxxx>
• Re: ieee papers
  • From: "chandrakant kumar" <k.03chandra@xxxxxxxxx>
• can we build external module with generic header?
  • From: vichy <vichy.kuo@xxxxxxxxx>
• lost bounds.h in include/linux
  • From: loody <miloody@xxxxxxxxx>
• Schedule() call in driver context.
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• Re: how to know what files build in one module?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: how to know what files build in one module?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: ieee papers
  • From: Krushnaal Pai <krisonearth@xxxxxxxxx>
• Re: ieee papers
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: linux booting
  • From: shankarGanesh <shankarganeshk@xxxxxxxxx>
• Re: ieee papers
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• how to know what files build in one module?
  • From: loody <miloody@xxxxxxxxx>
• Re: /sys file system not created
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• /sys file system not created
  • From: "J.Hwan.Kim" <j.hwan.kim99@xxxxxxxxx>
• Re: linux booting
  • From: Jigar Jajal <jjajal@xxxxxxxxx>
• Re: linux booting
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• ieee papers
  • From: Krushnaal Pai <krisonearth@xxxxxxxxx>
• Re: linux booting
  • From: Kalpesh Rathod <kalpeshrathod@xxxxxxxxx>
• Re: linux booting
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• linux booting
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• scatter-gather I/O
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Interpreting Ii/Io usbmon output
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: USB detection
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: installing miro
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxx>
• Re: dbus compilation
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: dbus compilation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: zlib cross compilation
  • From: Rik van Riel <riel@xxxxxxxxxxxx>
• zlib cross compilation
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: dbus compilation
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: dbus compilation
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: dbus compilation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• dbus compilation
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: boost package missing
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• boost package missing
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: installing miro
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: USB detection
  • From: Greg KH <greg@xxxxxxxxx>
• Re: USB detection
  • From: Anoop <anoop.chargotra@xxxxxxxxx>
• Poll/Select system call
  • From: bineet <bineet.cusat@xxxxxxxxx>
• Absolute Path from linux_dirent64
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: USB detection
  • From: Greg KH <greg@xxxxxxxxx>
• Re: spinlock_bh question
  • From: Vipul Jain <vipulsj@xxxxxxxxx>
• Re: spinlock_bh question
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• spinlock_bh question
  • From: Vipul Jain <vipulsj@xxxxxxxxx>
• Re: installing miro
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxx>
• installing miro
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: modules installation
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: modules installation
  • From: Martin Møller Skarbiniks Pedersen <traxplayer@xxxxxxxxx>
• modules installation
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Ethernet driver and CONFIG_NET_ETHERNET
  • From: Stephane Lambert <stephane.lambert@xxxxxxxxxx>
• Re: USB detection
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• USB detection
  • From: Anoop <anoop.chargotra@xxxxxxxxx>
• Re: Any experience with GPS/GPRS/GSM application kits ?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: interrupt dependencies.
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: interrupt dependencies.
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: interrupt dependencies.
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: interrupt dependencies.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Interpreting Ii/Io usbmon output
  • From: George Kadianakis <desnacked@xxxxxxxxx>
• interrupt dependencies.
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: kernel upgrade woes (possibly SATA/IDE confusion)
  • From: hv@xxxxxxxxx
• Re: How to organize any project ?
  • From: m0n0 <ole@xxxxxxxxxxxxx>
• Any experience with GPS/GPRS/GSM application kits ?
  • From: Sarath Kamisetty <sarath.kamisetty@xxxxxxxxx>
• Re: Kernel logging
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Kernel logging
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Sysfs Device Attributes: Subdirectory under subdirectory
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Kernel logging
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Sysfs Device Attributes: Subdirectory under subdirectory
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• How to organize any project ?
  • From: Rishi Agrawal <rishi.b.agrawal@xxxxxxxxx>
• Re: DMA reordering possible ?
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: having some problem with nfs boot
  • From: Pei Lin <telent997@xxxxxxxxx>
• rmb, wmb & mb() equivalent calls available in user space ?
  • From: yogeshwar sonawane <yogyas@xxxxxxxxx>
• Re: Kernel logging
  • From: Neependra Khare <neependra.khare@xxxxxxxxx>
• Re: having some problem with nfs boot
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxx>
• Kernel logging
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• having some problem with nfs boot
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Sysfs Device Attributes: Subdirectory under subdirectory
  • From: Greg KH <greg@xxxxxxxxx>
• DMA reordering possible ?
  • From: yogeshwar sonawane <yogyas@xxxxxxxxx>
• Re: Sysfs Device Attributes: Subdirectory under subdirectory
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• Re: Sysfs Device Attributes: Subdirectory under subdirectory
  • From: Greg KH <greg@xxxxxxxxx>
• Sysfs Device Attributes: Subdirectory under subdirectory
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• Re: latest kernel compile-- system panic
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: latest kernel compile-- system panic
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: latest kernel compile-- system panic
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: latest kernel compile-- system panic
  • From: waqar afridi <afridi.waqar@xxxxxxxxx>
• Re: module using another module
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: module using another module
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: latest kernel compile-- system panic
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• latest kernel compile-- system panic
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: kernel upgrade woes (possibly SATA/IDE confusion)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: Greg KH <greg@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: kernel upgrade woes (possibly SATA/IDE confusion)
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: kernel upgrade woes (possibly SATA/IDE confusion)
  • From: hv@xxxxxxxxx
• Re: Needs the complete definition "user_path_walk()"
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: dentry & path name lookup
  • From: Neependra Khare <neependra.khare@xxxxxxxxx>
• Re: Needs the complete definition "user_path_walk()"
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: dentry & path name lookup
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Needs the complete definition "user_path_walk()"
  • From: waqar afridi <afridi.waqar@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: Needs the complete definition "user_path_walk()"
  • From: waqar afridi <afridi.waqar@xxxxxxxxx>
• dentry & path name lookup
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: Needs the complete definition "user_path_walk()"
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Needs the complete definition "user_path_walk()"
  • From: waqar afridi <afridi.waqar@xxxxxxxxx>
• Re: detecting usb host controller type/speed from a gadget driver
  • From: Sudheer Divakaran <sudheer.divakaran@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: kernel upgrade woes (possibly SATA/IDE confusion)
  • From: "Vaughn E. Clinton" <vclinton@xxxxxxx>
• Re: Blacklisting in-kernel drivers
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: kernel upgrade woes (possibly SATA/IDE confusion)
  • From: hv@xxxxxxxxx
• Re: automatic driver loading functionality in Linux
  • From: Greg KH <greg@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: Ozan Türkyılmaz <ozan.turkyilmaz@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: Greg KH <greg@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: sysfs_ops show vector: size of buffer not required?
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• how to direct input/output?
  • From: loody <miloody@xxxxxxxxx>
• Re: Small patches for Linux kernel
  • From: Greg KH <greg@xxxxxxxxx>
• Re: detecting usb host controller type/speed from a gadget driver
  • From: Greg KH <greg@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: Greg KH <greg@xxxxxxxxx>
• Re: sysfs_ops show vector: size of buffer not required?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Debugging the kernel modules !
  • From: "Leena M." <kernmonk@xxxxxxxxx>
• Re: Debugging the kernel modules !
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Debugging the kernel modules !
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Debugging the kernel modules !
  • From: "Leena M." <kernmonk@xxxxxxxxx>
• Could /dev/mem mean all physical memory when I make a hole in ZONE_NORMAL
  • From: Adam Jiang <jiang.adam@xxxxxxxxx>
• Re: Small patches for Linux kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: accessing per-cpu variables from gdb
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Small patches for Linux kernel
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Small patches for Linux kernel
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• Re: accessing per-cpu variables from gdb
  • From: Robin Randhawa <robin.randhawa@xxxxxxxxx>
• Re: sysfs_ops show vector: size of buffer not required?
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• Re: sysfs_ops show vector: size of buffer not required?
  • From: Greg KH <greg@xxxxxxxxx>
• accessing per-cpu variables from gdb
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Blacklisting in-kernel drivers
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Chris Simmonds <chris@xxxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: where could I find the definition of PageSwapBacked()
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Problem with this code snippet.
  • From: Himanshu Chauhan <hschauhan@xxxxxxxxxxxxx>
• Re: where could I find the definition of PageSwapBacked()
  • From: Himanshu C <himanshu@xxxxxxxxxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: ZelluX <zellux@xxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: where could I find the definition of PageSwapBacked()
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• sysfs_ops show vector: size of buffer not required?
  • From: Himanshu Chauhan <himanshu@xxxxxxxxxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: ZelluX <zellux@xxxxxxxxx>
• Re: Fwd: Problem with headphones
  • From: Himanshu Chauhan <himanshu@xxxxxxxxxxxxxxxx>
• Re: Blacklisting in-kernel drivers
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Doubt regarding struct cdev
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: automatic driver loading functionality in Linux
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Blacklisting in-kernel drivers
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Doubt regarding struct cdev
  • From: Leelakrishna A <amudala.krishna@xxxxxxxxx>
• Fwd: Problem with headphones
  • From: Harshavardhan <harshu88@xxxxxxxxx>
• Fwd: Problem with headphones
  • From: Harshavardhan <harshu88@xxxxxxxxx>
• Re: where could I find the definition of PageSwapBacked()
  • From: Himanshu Chauhan <himanshu@xxxxxxxxxxxxxxxx>
• where could I find the definition of PageSwapBacked()
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• automatic driver loading functionality in Linux
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Blacklisting in-kernel drivers
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: Problem with headphones
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Marco Stornelli <marco.stornelli@xxxxxxxxx>
• file without O_LARGEFILE
  • From: santhosh kumar <santhu.linux@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: ZelluX <zellux@xxxxxxxxx>
• about not disabling shared interrupts while in ISR
  • From: Vipul Jain <vipulsj@xxxxxxxxx>
• Re: Blacklisting in-kernel drivers
  • From: Greg KH <greg@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Problem with headphones
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: Problem with headphones
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Blacklisting in-kernel drivers
  • From: luca ellero <lroluk@xxxxxxxxx>
• Problem with headphones
  • From: Harshavardhan <harshu88@xxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Is there any reference or documents about how Linux supports dynamic library?
  • From: Crossover Lonely <crosslonelyover@xxxxxxxxx>
• Is there any reference or documents about how Linux supports dynamic library?
  • From: ZelluX <zellux@xxxxxxxxx>
• Re: Blacklisting in-kernel drivers
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: browsing the kernel source with ctags?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: browsing the kernel source with ctags?
  • From: Tony Miller <mcfiredrill@xxxxxxxxx>
• Re: browsing the kernel source with ctags?
  • From: Syed Khader <sk.syed2@xxxxxxxxx>
• Re: pcie device driver for a solid state disk
  • From: Niel Acuna <amerei@xxxxxxxxx>
• kernel upgrade woes (possibly SATA/IDE confusion)
  • From: hv@xxxxxxxxx
• Re: Error in creating initial ramdisk
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Blacklisting in-kernel drivers
  • From: luca ellero <lroluk@xxxxxxxxx>
• pcie device driver for a solid state disk
  • From: Niel Acuna <amerei@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Marco Stornelli <marco.stornelli@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Error in creating initial ramdisk
  • From: Harshavardhan <harshu88@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Marco Stornelli <marco.stornelli@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Ricard Wanderlof <ricard.wanderlof@xxxxxxxx>
• Re: Kernel Build fail on Ubuntu
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Kernel Build fail on Ubuntu
  • From: Crossover Lonely <crosslonelyover@xxxxxxxxx>
• Re: browsing the kernel source with ctags?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: browsing the kernel source with ctags?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• browsing the kernel source with ctags?
  • From: Tony Miller <mcfiredrill@xxxxxxxxx>
• Re: Kernel Build fail on Ubuntu
  • From: amol verule <amol.debian@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: gdb doesn't load line number information from object (kgdb target)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Ricard Wanderlof <ricard.wanderlof@xxxxxxxx>
• Re: Kernel Build fail on Ubuntu
  • From: Vineet Agarwal <checkout.vineet@xxxxxxxxx>
• Re: Kernel Build fail on Ubuntu
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Kernel Build fail on Ubuntu
  • From: Ramya Desai <ramya.desai@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• mount ramdisk rootfs /etc directory to jffs2 filesystem.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• gdb doesn't load line number information from object (kgdb target)
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: xorg-server compilation
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: read problem in tty driver
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: xorg-server compilation
  • From: Zhu Yanhai <zhu.yanhai@xxxxxxxxx>
• read problem in tty driver
  • From: Jan Pazderník <valmorcz@xxxxxxxxx>
• Re: multimedia framework tutorial
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: preemption disable in spin_lock
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Disabling local apic timer
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Disabling local apic timer
  • From: Leonardo Alt <leonardoaltt@xxxxxxxxx>
• Re: preemption disable in spin_lock
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: u64 in linux_dirent64
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• u64 in linux_dirent64
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: preemption disable in spin_lock
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: preemption disable in spin_lock
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: CLONE_KERNEL flag - creating a new kernel thread
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• preemption disable in spin_lock
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• CLONE_KERNEL flag - creating a new kernel thread
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: use of USB screen monitor -- possible open source project (convert digital photo frame) ?
  • From: Kousik Maiti <maiti.kousik@xxxxxxxxx>
• Re: write access needed for ro mount, ext3
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• use of USB screen monitor -- possible open source project (convert digital photo frame) ?
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Clear screen from the kernel
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• multimedia framework tutorial
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• write access needed for ro mount, ext3
  • From: Ozan Türkyılmaz <ozan.turkyilmaz@xxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: A query regarding sysrq-trigger
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: A query regarding sysrq-trigger
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>