Linux Kernel Newbies

• Thread Index

• Classic confusion: initrd-initramfs
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Changing Kernel 3g / 1g memory split
  • From: Rick Brown <rick.brown.3@xxxxxxxxx>
• C question
  • From: Rick Brown <rick.brown.3@xxxxxxxxx>
• RE: Recursive makefiles for module spanning over multiple dir
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: strange code in linux kernel
  • From: Michal Nazarewicz <mina86@xxxxxxx>
• RE: How gdb attach command works?
  • From: askb <askb23@xxxxxxxxx>
• Re: Recursive makefiles for module spanning over multiple dir
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: How gdb attach command works?
  • From: Pranav Peshwe <pranavpeshwe@xxxxxxxxx>
• RE: How gdb attach command works?
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: how to pass the content of a file to kernel driver
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: How gdb attach command works?
  • From: Pranav Peshwe <pranavpeshwe@xxxxxxxxx>
• RE: Recursive makefiles for module spanning over multiple dir
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: Re: locking and interrupts
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Re: locking and interrupts
  • From: er krishna <erkrishna@xxxxxxxxx>
• RE: How gdb attach command works?
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• RE: How gdb attach command works?
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• RE: how to pass the content of a file to kernel driver
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: How gdb attach command works?
  • From: Pranav Peshwe <pranavpeshwe@xxxxxxxxx>
• Re: locking and interrupts
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: How gdb attach command works?
  • From: Krishan Malik <srikrishanmalik@xxxxxxxxx>
• Re: Re: locking and interrupts
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: Re: locking and interrupts
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: Re: locking and interrupts
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• Re: how to pass the content of a file to kernel driver
  • From: sandeep lahane <sandeep.lahane@xxxxxxxxx>
• Re: Re: locking and interrupts
  • From: er krishna <erkrishna@xxxxxxxxx>
• Recursive makefiles for module spanning over multiple dir
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: locking and interrupts
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: How gdb attach command works?
  • From: sandeep lahane <sandeep.lahane@xxxxxxxxx>
• how to pass the content of a file to kernel driver
  • From: vichy <vichy.kuo@xxxxxxxxx>
• How gdb attach command works?
  • From: Gaurav Aggarwal <grv.aggarwal@xxxxxxxxx>
• Re: locking and interrupts
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: Linux Kernel API testing
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Linux Kernel API testing
  • From: Vipul Jain <vipulsj@xxxxxxxxx>
• Re: sk_buff off by one confusion
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: locking and interrupts
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: Common makefiles for userspace and kernelspace code
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• RE: locking and interrupts
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: locking and interrupts
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• Re: locking and interrupts
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• Re: locking and interrupts
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: locking and interrupts
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: locking and interrupts
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: locking and interrupts
  • From: Rahul Ramasubramanian <ramasubramanian.rahul@xxxxxxxxx>
• Re: locking and interrupts
  • From: debian developer <debiandev@xxxxxxxxx>
• Re: locking and interrupts
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: locking and interrupts
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Common makefiles for userspace and kernelspace code
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• locking and interrupts
  • From: er krishna <erkrishna@xxxxxxxxx>
• RE: strange code in linux kernel
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: strange code in linux kernel
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• strange code in linux kernel
  • From: Rajat Jain <rajat.noida.india@xxxxxxxxx>
• Re: How to start user program after kernel booting (s3c2410 board)
  • From: Youngwhan <breadncup@xxxxxxxxx>
• RE: loading a kernel image on arm processor
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• How to start user program after kernel booting (s3c2410 board)
  • From: "J.H.Kim" <frog1120@xxxxxxxxx>
• Re: Per cpu data
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: linux developer conference reg.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: contributing to linux kernel.
  • From: Martin Møller Skarbiniks Pedersen <traxplayer@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: loading a kernel image on arm processor
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• sk_buff off by one confusion
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Search module in linux
  • From: askb <askb23@xxxxxxxxx>
• Re: Search module in linux
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Search module in linux
  • From: Deepak Mishra <dpux4linux@xxxxxxxxx>
• loading a kernel image on arm processor
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Re: contributing to linux kernel.
  • From: Davidlohr Bueso <dave@xxxxxxx>
• Re: kernel to kernel read page reading less bytes
  • From: Bob Beers <bob.beers@xxxxxxxxx>
• linux developer conference reg.
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• Re: kernel to kernel read page reading less bytes
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• kernel to kernel read page reading less bytes
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: Problem with mnt_list
  • From: Yan Wang <wy.micheal@xxxxxxxxx>
• Re: Problem with mnt_list
  • From: Yan Wang <micheal0917@xxxxxxxxx>
• Re: Problem with mnt_list
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: Problem with mnt_list
  • From: Henry Gebhardt <hsggebhardt@xxxxxxxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Greg KH <greg@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Fwd: facing a problem with irq handler,please help me
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Problem with mnt_list
  • From: Yan Wang <wy.micheal@xxxxxxxxx>
• Re: Query about /var/log/messages
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: KHz representation in Linux kernel
  • From: shankarGanesh <shankarganeshk@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Greg KH <greg@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Re: facing a problem with irq handler,please help me
  • From: Greg KH <greg@xxxxxxxxx>
• Re: KHz representation in Linux kernel
  • From: Pei Lin <telent997@xxxxxxxxx>
• facing a problem with irq handler,please help me
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Re: facing a problem with request _irq qnd enable_irq
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Query about /var/log/messages
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Query about /var/log/messages
  • From: Loránd Jakab <ljakab@xxxxxxxxxx>
• Re: Query about /var/log/messages
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Query about /var/log/messages
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: contributing to linux kernel.
  • From: debian developer <debiandev@xxxxxxxxx>
• facing a problem with request _irq qnd enable_irq
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Threaded Network Device Interrupts
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: development/hacking environment reg.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• after a couple weeks off, new kernel newbie column!
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Char device. poll() function question.
  • From: "Usman S. Ansari" <uansari@xxxxxxxxx>
• Re: max throughput achievable with outb()
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: max throughput achievable with outb()
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: max throughput achievable with outb()
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Char device. poll() function question.
  • From: Denis Borisevich <dennisfen@xxxxxxxxx>
• Re: Char device. poll() function question.
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Re: Char device. poll() function question.
  • From: Denis Borisevich <dennisfen@xxxxxxxxx>
• Re: Char device. poll() function question.
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: development/hacking environment reg.
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• Char device. poll() function question.
  • From: Denis Borisevich <dennisfen@xxxxxxxxx>
• Re: How to build DocBook in Linux kernel?
  • From: chaitanya <surya.namuduri@xxxxxxxxx>
• CONFIG_ASYNC_XOR not visible through menuconfig/gconfig
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• Re: How to build DocBook in Linux kernel?
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• How to build DocBook in Linux kernel?
  • From: NAHieu <nahieu@xxxxxxxxx>
• contributing to linux kernel.
  • From: Pete <greg.petr@xxxxxxxxx>
• Re: max throughput achievable with outb()
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• Re: KHz representation in Linux kernel
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: KHz representation in Linux kernel
  • From: Deven T <drt80d@xxxxxxxxx>
• Re: KHz representation in Linux kernel
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: KHz representation in Linux kernel
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: max throughput achievable with outb()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: max throughput achievable with outb()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: max throughput achievable with outb()
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: development/hacking environment reg.
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• KHz representation in Linux kernel
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• development/hacking environment reg.
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• max throughput achievable with outb()
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• Re: retain mounted initrd after booting?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Query on linux PCI
  • From: "Rajesh" <rajesh.zinzuwadia@xxxxxxxxxxxxxxxx>
• RE: interrupt/tasklet issue in custom driver on recent kernels
  • From: "Kodel Oleg" <oleg.kodel@xxxxxxxxxxxxxxxx>
• Re: different processes using same file object
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• Re: different processes using same file object
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• Re: different processes using same file object
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• Re: retain mounted initrd after booting?
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• Re: different processes using same file object
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: ext3 data=journal?
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Ioctls for data transfer
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: different processes using same file object
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: retain mounted initrd after booting?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: ext3 data=journal?
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Ioctls for data transfer
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: retain mounted initrd after booting?
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• Re: Ioctls for data transfer
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: buffer and page retrievel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: different processes using same file object
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Re: different processes using same file object
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• Re: retain mounted initrd after booting?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Kmalloc while holding a spinlock
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: retain mounted initrd after booting?
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• different processes using same file object
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• retain mounted initrd after booting?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Kmalloc while holding a spinlock
  • From: askb <askb23@xxxxxxxxx>
• Re: ext3 data=journal?
  • From: Venkatesh Srinivas <me@xxxxxxxxxxx>
• Kmalloc while holding a spinlock
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: ext3 data=journal?
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: "driver model" confusion
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: "driver model" confusion
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• Re: Trim the kernel source tree
  • From: Mena Soliko <solikoman@xxxxxxxxx>
• Re: Trim the kernel source tree
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• Re: buffer and page retrievel
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Trim the kernel source tree
  • From: Mena Soliko <solikoman@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: buffer and page retrievel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: implementation of 'mmap' on '/dev/zero'
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: implementation of 'mmap' on '/dev/zero'
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: implementation of 'mmap' on '/dev/zero'
  • From: Bruce Majia <bruce.majia@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• buffer and page retrievel
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• implementation of 'mmap' on '/dev/zero'
  • From: MaJia <bruce.majia@xxxxxxxxx>
• Re: "driver model" confusion
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• how to retain the initrd contents after booting?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: core dump
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Readahead - is 128KB the limit ?
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Readahead - is 128KB the limit ?
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: Readahead - is 128KB the limit ?
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Readahead - is 128KB the limit ?
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: Readahead - is 128KB the limit ?
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: "pseudo" file system versus "virtual" file system?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Readahead - is 128KB the limit ?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• "pseudo" file system versus "virtual" file system?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Readahead - is 128KB the limit ?
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: Readahead - is 128KB the limit ?
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Readahead - is 128KB the limit ?
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: does access_ok() even care about the READ/WRITE type anymore?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Passing struct time_t from kernel to userspace
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: does access_ok() even care about the READ/WRITE type anymore?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: does access_ok() even care about the READ/WRITE type anymore?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Video playing software
  • From: Douglas Schilling Landgraf <dougsland@xxxxxxxxx>
• Re: [NEWBIE]
  • From: Douglas Schilling Landgraf <dougsland@xxxxxxxxx>
• Re: Paid Kernel Development
  • From: Greg KH <greg@xxxxxxxxx>
• Passing struct time_t from kernel to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: how does kernel manages stack for threads?
  • From: CP YEH <ntdev74@xxxxxxxxx>
• Re: how does kernel manages stack for threads?
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: how does kernel manages stack for threads?
  • From: CP YEH <ntdev74@xxxxxxxxx>
• Kernel Cache Hit accouting
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Paid Kernel Development
  • From: debian developer <debiandev@xxxxxxxxx>
• ext3 data=journal?
  • From: Venkatesh Srinivas <me@xxxxxxxxxxx>
• Re: how does kernel manages stack for threads?
  • From: askb <askb23@xxxxxxxxx>
• how does kernel manages stack for threads?
  • From: CP YEH <ntdev74@xxxxxxxxx>
• Re: implementing mmap
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: implementing mmap
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: implementing mmap
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: implementing mmap
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: WANTED: Link kernel project
  • From: Donato Capitella <d.capitella@xxxxxx>
• Re: implementing mmap
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: implementing mmap
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: WANTED: Link kernel project
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• core dump
  • From: "Krzysztof Poc" <fajfusio@xxxxx>
• how to make hrtimer support on the board
  • From: jie zeng <zealcook@xxxxxxxxx>
• "driver model" confusion
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• Re: implementing mmap
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: implementing mmap
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: max mmap size for MAP_ANONYMOUS for amd64 ubuntu jaunty
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: implementing mmap
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• does access_ok() even care about the READ/WRITE type anymore?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: where is __chk_user_ptr() defined?
  • From: Pei Lin <telent997@xxxxxxxxx>
• where is __chk_user_ptr() defined?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: block size confusion -- in writing a basic simplest file system
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Kdb - Invalid address for breakpoint, ignoring bp command
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Kdb - Invalid address for breakpoint, ignoring bp command
  • From: Loic Pefferkorn <loic-kernelnewbies@xxxxxxxxxxxxx>
• Re: copy_to_user/copy_from_user in interrupt context
  • From: Belisko Marek <marek.belisko@xxxxxxxxx>
• copy_to_user/copy_from_user in interrupt context
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• WANTED: Link kernel project
  • From: Donato Capitella <d.capitella@xxxxxx>
• Re: /dev nodes deletion.
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Re: Auto loading of kernel modules COLD/HOT BOOT
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: implementing mmap
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: /dev nodes deletion.
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: Serial port implementation
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• implementing mmap
  • From: Andrea Gasparini <gaspa@xxxxxxxxxxx>
• Re: Ioctls for data transfer
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Auto loading of kernel modules COLD/HOT BOOT
  • From: Alan Jenkins <sourcejedi.lkml@xxxxxxxxxxxxxx>
• Serial port implementation
  • From: Mena Soliko <solikoman@xxxxxxxxx>
• Re: copy_to_user/copy_from_user in interrupt context
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: max mmap size for MAP_ANONYMOUS for amd64 ubuntu jaunty
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• /dev nodes deletion.
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Re: How can i see whether a process id is alive?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Is SSD a fear to storage enterprises?
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Kdb - Invalid address for breakpoint, ignoring bp command
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: copy_from_user and copy_to_user example
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: Pei Lin <telent997@xxxxxxxxx>
• How can i see whether a process id is alive?
  • From: Driver-Seeker <linuxdriverforme@xxxxxxxxx>
• Re: Ioctls for data transfer
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Ioctls for data transfer
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• mmap / page fault question
  • From: MK <stardust496@xxxxxxxxx>
• copy_from_user and copy_to_user example
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: Pei Lin <telent997@xxxxxxxxx>
• Kdb - Invalid address for breakpoint, ignoring bp command
  • From: Loic Pefferkorn <loic-kernelnewbies@xxxxxxxxxxxxx>
• max mmap size for MAP_ANONYMOUS for amd64 ubuntu jaunty
  • From: Mark Farnell <mark.farnell@xxxxxxxxx>
• Re: kernel Module autoloading - HOT and COLD BOOT
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: copy_to_user/copy_from_user in interrupt context
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• kernel Module autoloading - HOT and COLD BOOT
  • From: vprabu vprabu <prabu_online2005@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Ioctls for data transfer
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Ioctls for data transfer
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• how to implement malloc without glibc, uclibc and kernel support
  • From: loody <miloody@xxxxxxxxx>
• Re: Missing main function
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Basic USB doubt
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Ioctls for data transfer
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Missing main function
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Basic USB doubt
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Ioctls for data transfer
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Ioctls for data transfer
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Missing main function
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Basic USB doubt
  • From: loody <miloody@xxxxxxxxx>
• Re: Basic USB doubt
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Ioctls for data transfer
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: About Webcam module
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Missing main function
  • From: Frank DiMeo <frank_02019@xxxxxxxxx>
• Re: Basic USB doubt
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Locking and interrupt handlers
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: About Webcam module
  • From: Pei Lin <telent997@xxxxxxxxx>
• Locking and interrupt handlers
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: kernel boot delay
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Missing main function
  • From: consume.noise@xxxxxxxxxxxxxx
• Re: Basic USB doubt
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: PCI Issues
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: DEVFS permissions
  • From: shankarGanesh <shankarganeshk@xxxxxxxxx>
• Re: PCI Issues
  • From: Greg KH <greg@xxxxxxxxx>
• Re: About Webcam module
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: spinlocks and copy_to_user()
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: NEWBIE in kernel
  • From: Bian Jiang <border@xxxxxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: PCI Issues
  • From: Pei Lin <telent997@xxxxxxxxx>
• Basic USB doubt
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Missing main function
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: any example of CONFIG_GENERIC_HARDIRQS=n?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• any example of CONFIG_GENERIC_HARDIRQS=n?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: About Webcam module
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: About Webcam module
  • From: Jean-Francois Moine <moinejf@xxxxxxx>
• Re: multiple barrier bios to make_request_fn ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: PCI Issues
  • From: Greg KH <greg@xxxxxxxxx>
• Re: DEVFS permissions
  • From: Greg KH <greg@xxxxxxxxx>
• user/init with kernel 2.6?
  • From: Stephane Lambert <stephane.lambert@xxxxxxxxxx>
• Re: spinlocks and copy_to_user()
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: multiple barrier bios to make_request_fn ?
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: kernel boot delay
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: making a global structure
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Viewing page cache content
  • From: "Krzysztof Poc" <fajfusio@xxxxx>
• DEVFS permissions
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• making a global structure
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: multiple barrier bios to make_request_fn ?
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: Loránd Jakab <ljakab@xxxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Copying kernel module error messages to userspace
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Modules required for booting without initrd
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Modules required for booting without initrd
  • From: sky knight <sky_knight02@xxxxxxxxx>
• Re: Linux Podcast: http://www.linuxreality.com/archives.php
  • From: Adam Jiang <jiang.adam@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: e4defrag: file extent map : redundant loop???
  • From: Akira Fujita <a-fujita@xxxxxxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: e4defrag: file extent map : redundant loop???
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: ext4 extents: How to determine if an extent points to a hole.
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• PCI Issues
  • From: Mena Soliko <solikoman@xxxxxxxxx>
• Re: spinlocks and copy_to_user()
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• spinlocks and copy_to_user()
  • From: Mark Ryden <markryde@xxxxxxxxx>
• ext4 extents: How to determine if an extent points to a hole.
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• e4defrag: file extent map : redundant loop???
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Linux SMP Test Cases
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: module init code placement offset ? - Was : Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Stripped v Debug
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Linux SMP Test Cases
  • From: Abraham Arce <abraham.arce.moreno@xxxxxxxxx>
• Re: Linux Podcast: http://www.linuxreality.com/archives.php
  • From: 风随影动 <cosmoslx@xxxxxxxxx>
• Re: About Webcam module
  • From: Jean-Francois Moine <moinejf@xxxxxxx>
• Re: Linux Podcast: http://www.linuxreality.com/archives.php
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Why there is no realloc in kernel?
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Question on initramfs
  • From: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@xxxxxxxxx>
• Re: Why there is no realloc in kernel?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Why there is no realloc in kernel?
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• RE: Stripped v Debug
  • From: "Adrian Cornish" <adrianc@xxxxxxx>
• RE: Stripped v Debug
  • From: "Adrian Cornish" <adrianc@xxxxxxx>
• Re: kernel boot delay
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: Stripped v Debug
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: kernel boot delay
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Why there is no realloc in kernel?
  • From: Greg KH <greg@xxxxxxxxx>
• Linux Podcast: http://www.linuxreality.com/archives.php
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Stripped v Debug
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel boot delay
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: kernel boot delay
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: QUERY...!!
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• QUERY...!!
  • From: Harinderjit Singh Sandhu <harinderjitss@xxxxxxxxx>
• Re: kernel boot delay
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [NEWBIE]
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Stripped v Debug
  • From: "Adrian Cornish" <adrianc@xxxxxxx>
• Re: block size confusion -- in writing a basic simplest file system
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: NEWBIE in kernel
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: NEWBIE in kernel
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: About Webcam module
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: basic filesystem -- block size confusion
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• block size confusion -- in writing a basic simplest file system
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: About Webcam module
  • From: Loránd Jakab <ljakab@xxxxxxxxxx>
• Re: basic filesystem -- block size confusion
  • From: Steven Yao <yaohaiping.linux@xxxxxxxxx>
• Re: About Webcam module
  • From: Steven Yao <yaohaiping.linux@xxxxxxxxx>
• NEWBIE in kernel
  • From: Gaurav Soni <grvlinux@xxxxxxxxx>
• About Webcam module
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• kernel boot delay
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: basic filesystem -- sb_bread stucks
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: new kernel newbie column is up
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: basic filesystem -- sb_bread stucks
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• basic filesystem -- block size confusion
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: FS block size and Architecture Dependency
  • From: Rishi Agrawal <rishi.b.agrawal@xxxxxxxxx>
• Re: new kernel newbie column is up
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• problem with check_tty_count()
  • From: Stephane Lambert <stephane.lambert@xxxxxxxxxx>
• Re: Unable to use exported symbols
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: new kernel newbie column is up
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Unable to use exported symbols
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: [OOT] Link to my Linux.com "Uncover the meaning of top's statistics"
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: [NEWBIE]
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: difference bigphysarea patch and kmalloc
  • From: "Sven-Maurice Althoff" <maurice.althoff@xxxxxxxxxxxxxxxxxxxxx>
• Re: new kernel newbie column is up
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: new kernel newbie column is up
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: difference bigphysarea patch and kmalloc
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• new kernel newbie column is up
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• difference bigphysarea patch and kmalloc
  • From: mosta <mosta.me@xxxxxxxxxxxxxx>
• Re: [NEWBIE]
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: [NEWBIE]
  • From: Samudra Vishvajith <vishvaya@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: interrupt/tasklet issue in custom driver on recent kernels
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Why there is no realloc in kernel?
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Why there is no realloc in kernel?
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• interrupt/tasklet issue in custom driver on recent kernels
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• PMEM device
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: [NEWBIE]
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: FS block size and Architecture Dependency
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: [NEWBIE]
  • From: Deven <drt80d@xxxxxxxxx>
• Re: Video playing software
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: [NEWBIE]
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• [NEWBIE]
  • From: Chandrakant Kumar <k.03chandra@xxxxxxxxx>
• Video playing software
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Ip address assignment
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• RE: Ip address assignment
  • From: "Vivek Subbarao" <viveks@xxxxxxxxxxx>
• Re: Ip address assignment
  • From: Bruno Novais <ebnovais@xxxxxxxxx>
• RE: Ip address assignment
  • From: "Vivek Subbarao" <viveks@xxxxxxxxxxx>
• Re: Ip address assignment
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Ip address assignment
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: Ip address assignment
  • From: Gaurang Shastri <gmshastri@xxxxxxxxx>
• Ip address assignment
  • From: "Vivek Subbarao" <viveks@xxxxxxxxxxx>
• Re: Building Modules
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: Building Modules
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Building Modules - PLEASE IGNORE
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Building Modules
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: USB Doubt
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: trim in SSD's
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• any value in documenting deprecated _syscallN() calls?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: trim in SSD's
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• trim in SSD's
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: How morecore() works
  • From: Bryan Donlan <bdonlan@xxxxxxxxx>
• How morecore() works
  • From: Nitin Saxena <nitinsaxena1710@xxxxxxxxx>
• Re: USB Doubt
  • From: Greg KH <greg@xxxxxxxxx>
• Re: system calls that require disk access
  • From: Bryan Donlan <bdonlan@xxxxxxxxx>
• Re: FS block size and Architecture Dependency
  • From: Bryan Donlan <bdonlan@xxxxxxxxx>
• Re: Signal problem
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• USB Doubt
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: apparently, i don't know seq_files as well as i thought
  • From: Pei Lin <telent997@xxxxxxxxx>
• [OOT] Link to my Linux.com "Uncover the meaning of top's statistics"
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: decoding kernel oops
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: for swap only? /proc/sys/vm/pages_cluster
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: decoding kernel oops
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: for swap only? /proc/sys/vm/pages_cluster
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• for swap only? /proc/sys/vm/pages_cluster
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: Signal problem
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: FS block size and Architecture Dependency
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Subscription problem
  • From: Bian Jiang <border@xxxxxxxxxxxx>
• Subscription problem
  • From: Niamathullah sharief <developersharief@xxxxxxxxx>
• FS block size and Architecture Dependency
  • From: Rishi Agrawal <rishi.b.agrawal@xxxxxxxxx>
• Re: Fwd: disable_irq in ndo_poll_controller
  • From: JiSheng Zhang <jszhang3@xxxxxxxxx>
• Re: Fwd: disable_irq in ndo_poll_controller
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Fwd: disable_irq in ndo_poll_controller
  • From: JiSheng Zhang <jszhang3@xxxxxxxxx>
• Re: Signal problem
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Signal problem
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Signal problem
  • From: Laurentziu Dascalu <dascalu.laurentziu@xxxxxxxxx>
• Re: Signal problem
  • From: Kent Tu <kachin2@xxxxxxxxx>
• Re: Signal problem
  • From: Laurentziu Dascalu <dascalu.laurentziu@xxxxxxxxx>
• Signal problem
  • From: Laurentziu Dascalu <dascalu.laurentziu@xxxxxxxxx>
• Booting issue on Omap3430 due to Initrd
  • From: zamir alam <zamir.alam@xxxxxxxxx>
• Re: pr_debug and "if (0)" statement
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: Fwd: disable_irq in ndo_poll_controller
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: pr_debug and "if (0)" statement
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Fwd: disable_irq in ndo_poll_controller
  • From: JiSheng Zhang <jszhang3@xxxxxxxxx>
• Re: pr_debug and "if (0)" statement
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: decoding kernel oops
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• apparently, i don't know seq_files as well as i thought
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: netconsole configuration problem in FC-8 and FC-10 with 2.6.28 and 2.6.30 versions
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: decoding kernel oops
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• decoding kernel oops
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: basic filesystem -- sb_bread stucks
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: pr_debug and "if (0)" statement
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: pr_debug and "if (0)" statement
  • From: Matteo Foppiano <matteo.foppy@xxxxxxxxx>
• Re: pr_debug and "if (0)" statement
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• basic filesystem -- sb_bread stucks
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: pr_debug and "if (0)" statement
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: pr_debug and "if (0)" statement
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• pr_debug and "if (0)" statement
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: /proc/kallsyms related question
  • From: "Usman S. Ansari" <uansari@xxxxxxxxx>
• Re: software for x86 instruction set
  • From: John M <john.meraj@xxxxxxxxx>
• netconsole configuration problem in FC-8 and FC-10 with 2.6.28 and 2.6.30 versions
  • From: Madhavi Manchala <madhavi.lscsi@xxxxxxxxx>
• Re: /proc/kallsyms related question
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: module init code placement offset ? - Was : Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• /proc/kallsyms related question
  • From: "Usman S. Ansari" <uansari@xxxxxxxxx>
• Re: module init code placement offset ? - Was : Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: module init code placement offset ? - Was : Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: New kernel newbie column is up
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• system calls that require disk access
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: OLS 2009: request for comments
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: New kernel newbie column is up
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• module init code placement offset ? - Was : Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: New kernel newbie column is up
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: OLS 2009 highlights
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: software for x86 instruction set
  • From: Ole Loots <ole@xxxxxxxxxxxxx>
• Re: software for x86 instruction set
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: OLS 2009 highlights
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• software for x86 instruction set
  • From: John M <john.meraj@xxxxxxxxx>
• Re: OLS 2009 highlights
  • From: Izik Eidus <ieidus@xxxxxxxxxx>
• Re: OLS 2009 highlights
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: OLS 2009 highlights
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: Doubt regarding signal handling
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: OLS 2009 highlights
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: how to make /dev/random work?
  • From: loody <miloody@xxxxxxxxx>
• Re: OLS 2009 highlights
  • From: Minchan Kim <minchan.kim@xxxxxxxxx>
• OLS 2009 highlights
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: how to make /dev/random work?
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: how to check whether execve is successful or not?
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Doubt regarding signal handling
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: elf working info?
  • From: John M <john.meraj@xxxxxxxxx>
• Re: how to check whether execve is successful or not?
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: Question about sendpage exploit
  • From: fisherman <ipconfigme@xxxxxxxxx>
• Re: how to check whether execve is successful or not?
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: how to check whether execve is successful or not?
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: Question about sendpage exploit
  • From: Bryan Donlan <bdonlan@xxxxxxxxx>
• Re: Question about sendpage exploit
  • From: Bryan Donlan <bdonlan@xxxxxxxxx>
• how to check whether execve is successful or not?
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: fixing daq driver dma access
  • From: mosta <mosta.me@xxxxxxxxxxxxxx>
• Re: Question about sendpage exploit
  • From: fisherman <ipconfigme@xxxxxxxxx>
• Re: Question about sendpage exploit
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: executables and its dependencies?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: how to make /dev/random work?
  • From: Florian Fainelli <florian@xxxxxxxxxxx>
• Re: Per cpu data
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• Re: how to make /dev/random work?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• executables and its dependencies?
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Fwd: how to make /dev/random work?
  • From: loody <miloody@xxxxxxxxx>
• Re: Per cpu data
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Per cpu data
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• Re: how to make /dev/random work?
  • From: consume.noise@xxxxxxxxxxxxxx
• how to make /dev/random work?
  • From: loody <miloody@xxxxxxxxx>
• Re: Question about sendpage exploit
  • From: fisherman <ipconfigme@xxxxxxxxx>
• Re: Question about sendpage exploit
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: elf working info?
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: memcpy
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Question about sendpage exploit
  • From: fisherman <ipconfigme@xxxxxxxxx>
• Re: Non-blocking IO
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Re: howto sendpages over network
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Adding delay to packets
  • From: Loránd Jakab <ljakab@xxxxxxxxxx>
• Re: Per cpu data
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• Re: Adding delay to packets
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Is the list broken?
  • From: Manish Rangankar <rangankarmanish@xxxxxxxxx>
• Re: memcpy
  • From: Peter Hüwe <PeterHuewe@xxxxxx>
• memcpy
  • From: Stoyan Gaydarov <sgayda2@xxxxxxxx>
• Adding delay to packets
  • From: Vilen Looga <vilen.looga@xxxxxxxxx>
• new kernel newbie column
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: elf working info?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Per cpu data
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: elf working info?
  • From: John M <john.meraj@xxxxxxxxx>
• Pagefault mechanism
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• RTLWS11, September 28-30, TU Dresden, Germany - Call for Participation
  • From: andi <andi.platschek@xxxxxxxxx>
• Per cpu data
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• Re: Non-blocking IO
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: tiny tty driver in ldd3
  • From: srinivas ramana <srinivas.ramana@xxxxxxxxx>
• elf working info?
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: Is the list broken?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: fixing daq driver dma access
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: New kernel newbie column is up
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Is the list broken?
  • From: Rik van Riel <riel@xxxxxxxxxxxx>
• Re: Is the list broken?
  • From: Rik van Riel <riel@xxxxxxxxxxxx>
• Re: Is the list broken?
  • From: Manish Rangankar <rangankarmanish@xxxxxxxxx>
• Re: getting started with drivers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Is the list broken?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: getting started with drivers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Question about C Programming.
  • From: Krishan Malik <srikrishanmalik@xxxxxxxxx>
• fixing daq driver dma access
  • From: Sven-Maurice Althoff <mosta.me@xxxxxxxxxxxxxx>
• Re: Is the list broken?
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Is the list broken?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Is the list broken?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Is the list broken?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Is the list broken?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Is the list broken?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Is the list broken?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• howto sendpages over network
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: getting started with drivers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• RE: getting started with drivers
  • From: "Rangankar, Manish" <manish.rangankar@xxxxxxxxx>
• Re: getting started with drivers
  • From: Radu <vorad.1100@xxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Question about C Programming.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Question about set/get cpu affinity tool by Robert love.
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: getting started with drivers
  • From: Ed Sesek <ed@xxxxxxxxx>
• RE: getting started with drivers
  • From: "Rangankar, Manish" <manish.rangankar@xxxxxxxxx>
• Re: getting started with drivers
  • From: Radu <vorad.1100@xxxxxxxxx>
• Re: getting started with drivers
  • From: Manish Rangankar <rangankarmanish@xxxxxxxxx>
• Non-blocking IO
  • From: Manish Rangankar <rangankarmanish@xxxxxxxxx>
• Re: Non-blocking IO
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Non-blocking IO
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• getting started with drivers
  • From: Radu <radu@xxxxxxxxxxxx>
• new kernel newbie column: debugging with proc files
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• debugging using OHCI-1394 firewire controller
  • From: John Meraj <john.meraj@xxxxxxxxx>
• Re: User space / Kernel space HZ difference?
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• User space / Kernel space HZ difference?
  • From: Mayuresh Kulkarni <stardust496@xxxxxxxxx>
• Re: error in sysfs node create
  • From: shankarGanesh <shankarganeshk@xxxxxxxxx>
• Re: error in sysfs node create
  • From: Greg KH <greg@xxxxxxxxx>
• Re: New kernel newbie column is up
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: New kernel newbie column is up
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: New kernel newbie column is up
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: New kernel newbie column is up
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: Writing device drivers temporarily in user space for better source level debug ?
  • From: Ivan Korzakow <ivan.korzakow@xxxxxxxxx>
• Re: allocating huge amount of memory
  • From: Devesh Sharma <devesh28@xxxxxxxxx>
• Re: allocating huge amount of memory
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: allocating huge amount of memory
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• error in sysfs node create
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: allocating huge amount of memory
  • From: Devesh Sharma <devesh28@xxxxxxxxx>
• Re: allocating huge amount of memory
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• allocating huge amount of memory
  • From: vadimbox@xxxxxxxx
• Re: 32-bit kernel
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: 32-bit kernel
  • From: Manish Rangankar <rangankarmanish@xxxxxxxxx>
• Re: Cache Size
  • From: Manish Rangankar <rangankarmanish@xxxxxxxxx>
• Re: ext3 structure mapping to block device
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Cache Size
  • From: Raz <raziebe@xxxxxxxxx>
• Re: zero copy on socket recv
  • From: Rahul K Patel <rahulk.patel@xxxxxxxxxxxxxx>
• Re: zero copy on socket recv
  • From: Raz <raziebe@xxxxxxxxx>
• Re: creating global variables in kernel
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: creating global variables in kernel
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• creating global variables in kernel
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• zero copy on socket recv
  • From: Rahul K Patel <rahulk.patel@xxxxxxxxxxxxxx>
• Cache Size
  • From: manish rangankar <rangankarmanish@xxxxxxxxx>
• Re: ext3 structure mapping to block device
  • From: ajit mote <mail2blackmen@xxxxxxxxx>
• Re: ext3 structure mapping to block device
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: ext3 structure mapping to block device
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• ext3 structure mapping to block device
  • From: ajit mote <mail2blackmen@xxxxxxxxx>
• Re: tiny tty driver in ldd3
  • From: Greg KH <greg@xxxxxxxxx>
• Re: POLL in char drivers
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: POLL in char drivers
  • From: shankarGanesh <shankarganeshk@xxxxxxxxx>
• Re: 32-bit kernel
  • From: manish <rangankarmanish@xxxxxxxxx>
• Re: some question about open fail on /dev/sda nodes
  • From: Siddu <siddu.sjce@xxxxxxxxx>
• Re: some question about open fail on /dev/sda nodes
  • From: John Meraj <john.meraj@xxxxxxxxx>
• Re: POLL in char drivers
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: some question about open fail on /dev/sda nodes
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: 32-bit kernel
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• some question about open fail on /dev/sda nodes
  • From: loody <miloody@xxxxxxxxx>
• Re: 32-bit kernel
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Single UART handling multiple devices.
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• 32-bit kernel
  • From: manish <rangankarmanish@xxxxxxxxx>
• Re: sending pid of user process to kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Question about kernel preemption
  • From: Mohammed Gamal <m.gamal005@xxxxxxxxx>
• Writing device drivers temporarily in user space for better source level debug ?
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Single UART handling multiple devices.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• sending pid of user process to kernel
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: Single UART handling multiple devices.
  • From: srinivasramana <srinivas.ramana@xxxxxxxxx>
• Re: Single UART handling multiple devices.
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Question about kernel preemption
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Question about kernel preemption
  • From: Mohammed Gamal <m.gamal005@xxxxxxxxx>
• Re: Question about kernel preemption
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• RE: Condition Variables
  • From: "Rangankar, Manish" <manish.rangankar@xxxxxxxxx>
• Re: Question about kernel preemption
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Single UART handling multiple devices.
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Question about kernel preemption
  • From: Mohammed Gamal <m.gamal005@xxxxxxxxx>
• Re: Question about kernel preemption
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Single UART handling multiple devices.
  • From: srinivasramana <srinivas.ramana@xxxxxxxxx>
• Re: Condition Variables
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Question about kernel preemption
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Condition Variables
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: POLL in char drivers
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Question about kernel preemption
  • From: Mohammed Gamal <m.gamal005@xxxxxxxxx>
• Condition Variables
  • From: "Rangankar, Manish" <manish.rangankar@xxxxxxxxx>
• Re: Automated Synchronization for pendrives
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: POLL in char drivers
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Automated Synchronization for pendrives
  • From: Rishi Agrawal <rishi.b.agrawal@xxxxxxxxx>
• POLL in char drivers
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• page locks to avoid data corruption
  • From: Tharindu Rukshan Bamunuarachchi <tharindu@xxxxxxxxxxxxx>
• Re: Is read-only initramfs root possible?
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Is read-only initramfs root possible?
  • From: David Wuertele <dave+gmane@xxxxxxxxxxxx>
• should some seq_file output operations be EXPORTed?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Queued Spin Lock.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Question about lock ordering.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Question about lock ordering.
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Question about lock ordering.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Is read-only initramfs root possible?
  • From: David Wuertele <dave+gmane@xxxxxxxxxxxx>
• Re: New kernel newbie column is up
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: New kernel newbie column is up
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: New kernel newbie column is up
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• New kernel newbie column is up
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Queued Spin Lock.
  • From: Devesh Sharma <devesh28@xxxxxxxxx>
• Queued Spin Lock.
  • From: Prasad Joshi <prasadjoshi124@xxxxxxxxx>
• Re: modprobe error with ndiswrapper [ please suggest why modprobe fails (or tell me the flow of modprobe)]
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: modprobe error with ndiswrapper [ please suggest why modprobe fails (or tell me the flow of modprobe)]
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Stack unwinding using kprobes
  • From: Basavaraj Dengi <basavarajdengi@xxxxxxxxx>
• taskset vs. numactl
  • From: Tharindu Rukshan Bamunuarachchi <tharindu@xxxxxxxxxxxxx>
• modprobe error with ndiswrapper [ please suggest why modprobe fails (or tell me the flow of modprobe)]
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: Stack unwinding using kprobes
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: LDD3 examples advice
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Stack unwinding using kprobes
  • From: Basavaraj Dengi <basavarajdengi@xxxxxxxxx>
• Re: LDD3 examples advice
  • From: Greg KH <gregkh@xxxxxxx>
• Re: Stack unwinding using kprobes
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Stack unwinding using kprobes
  • From: Basavaraj Dengi <basavarajdengi@xxxxxxxxx>
• Re: LDD3 examples advice
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Drive tester
  • From: Gwendal Grignou <gwendal@xxxxxxxxxx>
• Re: Stack unwinding using kprobes
  • From: Himanshu Chauhan <himanshu@xxxxxxxxxxxxxxx>
• Re: Stack unwinding using kprobes
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Stack unwinding using kprobes
  • From: Himanshu Chauhan <himanshu@xxxxxxxxxxxxxxx>
• Re: LDD3 examples advice
  • From: Greg KH <gregkh@xxxxxxx>
• Re: LDD3 examples advice
  • From: debian developer <debiandev@xxxxxxxxx>
• single server multiple clients at kernel level
  • From: krushnaal pai <krisonearth@xxxxxxxxx>
• Re: Avoid uml opening virtual consoles
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: How to configure usb as console
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Avoid uml opening virtual consoles
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: LDD3 examples advice
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Avoid uml opening virtual consoles
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: LDD3 examples advice
  • From: Greg KH <gregkh@xxxxxxx>
• Avoid uml opening virtual consoles
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Perplexed with a compilation problem.
  • From: Belisko Marek <marek.belisko@xxxxxxxxx>
• Re: LDD3 examples advice
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: LDD3 examples advice
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• LDD3 examples advice
  • From: Belisko Marek <marek.belisko@xxxxxxxxx>
• Re: Perplexed with a compilation problem.
  • From: Prasad Joshi <prasadjoshi124@xxxxxxxxx>
• Re: what about " $(Q)@ " in toplevel Makefile??? A resent mail..
  • From: "yihect" <yihect@xxxxxxx>
• Re: what about " $(Q)@ " in toplevel Makefile??? A resent mail..
  • From: Pei Lin <telent997@xxxxxxxxx>
• what about " $(Q)@ " in toplevel Makefile??? A resent mail..
  • From: "yihect" <yihect@xxxxxxx>
• Re: Netlink packet alignment purpose
  • From: Łukasz Jachymczyk <lfx@xxxxxxx>
• debugging loadable modules with simple "gdb"
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Questions about updating hisax drivers that use pci_find_device()
  • From: kevin granade <kevin.granade@xxxxxxxxx>
• a couple questions about kernel debugging with plain "gdb"
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Perplexed with a compilation problem.
  • From: Belisko Marek <marek.belisko@xxxxxxxxx>
• Perplexed with a compilation problem.
  • From: Prasad Joshi <prasadjoshi124@xxxxxxxxx>
• Re: status of u32 type in 2.6.29.4 ?
  • From: Pei Lin <telent997@xxxxxxxxx>
• Questions about updating hisax drivers that use pci_find_device()
  • From: kevin granade <kevin.granade@xxxxxxxxx>
• Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: how to list the current HZ value?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Changing path in kernel object & Debug of Kernel module with gdb
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: by default, does seq_file start() routine start at zero offset?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Changing path in kernel object & Debug of Kernel module with gdb
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: status of u32 type in 2.6.29.4 ?
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: by default, does seq_file start() routine start at zero offset?
  • From: Bruce Rowen <browen@xxxxxxxxxxxx>
• a couple more questions about seq_files
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: [uml-user] Compiling modules on UML
  • From: H M Thalib <hmthalib@xxxxxxxxx>
• this week's kernel newbie corner column at linux.com
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: by default, does seq_file start() routine start at zero offset?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: [uml-user] Compiling modules on UML
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: [uml-user] Compiling modules on UML
  • From: H M Thalib <hmthalib@xxxxxxxxx>
• Re: by default, does seq_file start() routine start at zero offset?
  • From: Bruce Rowen <browen@xxxxxxxxxxxx>
• Re: [uml-user] Compiling modules on UML
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Compiling modules on UML
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Compiling modules on UML
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• what about " $(Q)@ " in toplevel Makefile???
  • From: "yihect" <yihect@xxxxxxx>
• How to configure usb as console
  • From: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@xxxxxxxxx>
• Re: by default, does seq_file start() routine start at zero offset?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: by default, does seq_file start() routine start at zero offset?
  • From: Bruce Rowen <browen@xxxxxxxxxxxx>
• by default, does seq_file start() routine start at zero offset?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: clarifying the construction of read-only /proc files
  • From: Bruce Rowen <browen@xxxxxxxxxxxx>
• Re: clarifying the construction of read-only /proc files
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• clarifying the construction of read-only /proc files
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• [no subject]
  • From: Mark Ryden <markryde@xxxxxxxxx>
• make error in building sample code!
  • From: Greg Peter <greg.petr@xxxxxxxxx>
• Re: status of u32 type in 2.6.29.4 ?
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: architecture independent way to define task_struct
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: make error in building sample code!
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• architecture independent way to define task_struct
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• ioctl32.h on kernel 2.6.30 amd64
  • From: Bartek Dolewski <doles2@xxxxxxxxx>
• Kernel 2.6.30 and <linux/ioctl32.h> no such file or directory
  • From: Bartek Dolewski <doles2@xxxxxxxxx>
• Building a module outside the kernel source tree.
  • From: Mark Ryden <markryde@xxxxxxxxx>
• Re: how to list the current HZ value?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Help to read journal content
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: how to list the current HZ value?
  • From: Pei Lin <telent997@xxxxxxxxx>
• Netlink packet alignment purpose
  • From: ?ukasz Jachymczyk <lfx@xxxxxxx>
• Re: Need info on input keys
  • From: seshikanth varma <seshikanthvarma@xxxxxxxxx>
• Re: want to write a file system
  • From: "Davidlohr Bueso A." <dave@xxxxxxx>
• Re: user space way to determine "region" of allocated minors?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Help to read journal content
  • From: ranjith kannikara <ranjithkannikara@xxxxxxxxx>
• Re: want to write a file system
  • From: Raz <raziebe@xxxxxxxxx>
• Re: user space way to determine "region" of allocated minors?
  • From: Martyn Welch <martyn.welch@xxxxxxxxxxx>
• Re: want to write a file system
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: user space way to determine "region" of allocated minors?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: want to write a file system
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: want to write a file system
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• want to write a file system
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: Using system calls inside kernel
  • From: Methos <methos.oldest@xxxxxxxxx>
• Re: Using system calls inside kernel
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: user space way to determine "region" of allocated minors?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• 答复: 答复: 答复: 答复: Ecartis command results: appsub kernelnewbies FuXinRong@xxxxxxxxxxxx 4A71650B:26CF.1:xrearyarjovrf
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• Using system calls inside kernel
  • From: Methos <methos.oldest@xxxxxxxxx>
• user space way to determine "region" of allocated minors?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: a couple questions about "gdb vmlinux /proc/kcore"
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• anyone set up "cscout" for the kernel source tree?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: CONFIG_DEBUG_INFO versus not
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• dmesg to print on a separate console
  • From: H M Thalib <hmthalib@xxxxxxxxx>
• Re: a couple questions about "gdb vmlinux /proc/kcore"
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: how to list the current HZ value?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: a couple questions about "gdb vmlinux /proc/kcore"
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• a couple questions about "gdb vmlinux /proc/kcore"
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: how to list the current HZ value?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: how to list the current HZ value?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: how to list the current HZ value?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: CONFIG_DEBUG_INFO versus not
  • From: Siddu <siddu.sjce@xxxxxxxxx>
• Re: pause(), wait() and infinity
  • From: Siddu <siddu.sjce@xxxxxxxxx>
• Re: preemption
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: status of u32 type in 2.6.29.4 ?
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: preemption
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• 答复: 答复: 答复: Ecartis command results: appsub kernelnewbies FuXinRong@xxxxxxxxxxxx 4A71650B:26CF.1:xrearyarjovrf
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• Re: how to list the current HZ value?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: pause(), wait() and infinity
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: preemption
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: pause(), wait() and infinity
  • From: Andy Dalton <andy.dalton@xxxxxxxxx>
• Re: pause(), wait() and infinity
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: CONFIG_DEBUG_INFO and debugging the kernel with "gdb"
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• some question about kernel stack(following init_thread_union)
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• 答复: 答复: Ecartis command results: appsub kernelnewbies FuXinRong@xxxxxxxxxxxx 4A71650B:26CF.1:xrearyarjovrf
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• Re: how to list the current HZ value?
  • From: Karel Zak <kzak@xxxxxxxxxx>
• status of u32 type in 2.6.29.4 ?
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Question about set/get cpu affinity tool by Robert love.
  • From: Vipul Jain <vipulsj@xxxxxxxxx>
• CONFIG_DEBUG_INFO versus not
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Drive tester
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>