Linux Kernel Newbies

• Thread Index

• 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>
• Re: A query regarding sysrq-trigger
  • From: Syed Khader <sk.syed2@xxxxxxxxx>
• Re: Process, Lightweight Process and Thread
  • From: askb <askb23@xxxxxxxxx>
• Process, Lightweight Process and Thread
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• A query regarding sysrq-trigger
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: vmalloc space overlapping
  • From: Prashant Bhole <prashantsmailcenter@xxxxxxxxx>
• Re: Why the linux does not allow the access to a file in the device driver?
  • From: Jeffrey Cao <jcao.linux@xxxxxxxxx>
• Re: Clear screen from the kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Why the linux does not allow the access to a file in the devicedriver?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: vmalloc space overlapping
  • From: Syed Khader <sk.syed2@xxxxxxxxx>
• Re: Why the linux does not allow the access to a file in the devicedriver?
  • From: "snoppy1314" <snoppy1314@xxxxxxx>
• Re: Why the linux does not allow the access to a file in the device driver?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Why the linux does not allow the access to a file in the device driver?
  • From: askb <askb23@xxxxxxxxx>
• Why the linux does not allow the access to a file in the device driver?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: Clear screen from the kernel
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Clear screen from the kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Clear screen from the kernel
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Clear screen from the kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Is now : how to send HID kbd to tty1
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Clear screen from the kernel
  • From: Greg KH <greg@xxxxxxxxx>
• Clear screen from the kernel
  • From: Diego Woitasen <diego@xxxxxxxxxxxxxxx>
• How to study Routing subsystem?
  • From: Kapuddi <Kapuddi@xxxxxxxxx>
• Is now, how to send HID kbd stream to stdin from tty1 ?
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: xorg-server compilation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• HSM implementation
  • From: rohit vashist <rohitvashist2kk3@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• xorg-server compilation
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: piping HID kbd handler to stdin - is a daemon needed ?
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: How to get the number of free pages in a zone(2.6.18)?
  • From: Adam Jiang <jiang.adam@xxxxxxxxx>
• How to get the number of free pages in a zone(2.6.18)?
  • From: Adam Jiang <jiang.adam@xxxxxxxxx>
• piping HID kbd handler to stdin - is a daemon needed ?
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• how to support "module.param=val" on kernel command line?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Why can struct sock convert to struct tcp_sock?
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Suggestions for implementing a persistent binary tree
  • From: Bryan Donlan <bdonlan@xxxxxxxxx>
• Why can struct sock convert to struct tcp_sock?
  • From: Kapuddi <Kapuddi@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: askb <askb23@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: Pete <greg.petr@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Suggestions for implementing a persistent binary tree
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: copy-on-write overhead
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• copy-on-write overhead
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: compiling ext2 outside source tree
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: compiling ext2 outside source tree
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• compiling ext2 outside source tree
  • From: Onkar <onkar.n.m@xxxxxxxxx>
• Re: Out of memory vs memory leak
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Handling Strings Inside ?
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Handling Strings Inside ?
  • From: Siddu <siddu.sjce@xxxxxxxxx>
• Re: Embedded Linux development
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: Embedded Linux development
  • From: Yangkook Kim <yangkookkim@xxxxxxxxx>
• Re: Suggestions for implementing a persistent binary tree
  • From: Bryan Donlan <bdonlan@xxxxxxxxx>
• A question about tasklet's TASKLET_STATE_RUN state
  • From: Simon <wei.guo.simon@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Benjamin Campbell <benji.campbell@xxxxxxxxx>
• Re: kernel API and other update changes.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Durga Prasad <writexdp@xxxxxxxxx>
• Re: Out of memory vs memory leak
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Out of memory vs memory leak
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Out of memory vs memory leak
  • From: Anand Raj Manickam <anandrm@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• kernel API and other update changes.
  • From: amol verule <amol.debian@xxxxxxxxx>
• Out of memory vs memory leak
  • From: Anand Raj Manickam <anandrm@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: 'No such device or address' when writing to device driver
  • From: "chiachen" <luojiazhen@xxxxxxxxx>
• Re: anyone use "sparse" for static code analysis?
  • From: Greg KH <greg@xxxxxxxxx>
• How to transfer the Android color display into 16-level gray scale B/W display?
  • From: Wang Dennis <denniswang2010@xxxxxxxxx>
• vmalloc space overlapping
  • From: Prashant Bhole <prashantsmailcenter@xxxxxxxxx>
• Re: Fwd: Embedded Linux development
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Embedded Linux development
  • From: Robin Randhawa <robin.randhawa@xxxxxxxxx>
• Re: Fwd: Embedded Linux development
  • From: Pavan Kandepet <pavankp@xxxxxxxxx>
• 'No such device or address' when writing to device driver
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: Embedded Linux development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Fwd: Embedded Linux development
  • From: Jeevan <jeevanrk@xxxxxxxxx>
• Suggestions for implementing a persistent binary tree
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• anyone use "sparse" for static code analysis?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Fwd: Embedded Linux development
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• Re: Fwd: Embedded Linux development
  • From: Shaz <shazalive@xxxxxxxxx>
• spin_lock_string (of /include/asm-i386/spinlock.h) macro definition (not clear) of version <= 2.6.8
  • From: Sushil Mayengbam <hacker.mayengbam@xxxxxxxxx>
• Re: question about __v annotation
  • From: Greg KH <greg@xxxxxxxxx>
• Re: question about __v annotation
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: question about __v annotation
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Embedded Linux development
  • From: Kalpesh Rathod <kalpeshrathod@xxxxxxxxx>
• Re: question about __v annotation
  • From: Robin Randhawa <robin.randhawa@xxxxxxxxx>
• Re: question about __v annotation
  • From: Robin Randhawa <robin.randhawa@xxxxxxxxx>
• Re: question about __v annotation
  • From: Greg KH <greg@xxxxxxxxx>
• Re: jffs2 doubts
  • From: Syed Khader <sk.syed2@xxxxxxxxx>
• Re: question about __v annotation
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: question about __v annotation
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: question about __v annotation
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Fwd: Embedded Linux development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: question about __v annotation
  • From: Pei Lin <telent997@xxxxxxxxx>
• RE: question about __v annotation
  • From: "Bruce Blinn" <bruce.blinn@xxxxxxxxx>
• Re: question about __v annotation
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• Re: jffs2 doubts
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: question about __v annotation
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• Fwd: Embedded Linux development
  • From: topon topaz <lroluk@xxxxxxxxx>
• jffs2 doubts
  • From: Arun S <inbox1.arun@xxxxxxxx>
• Re: Embedded Linux development
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: question about __v annotation
  • From: Greg KH <greg@xxxxxxxxx>
• Re: question about __v annotation
  • From: Ryan Wang <openspace.wang@xxxxxxxxx>
• spin_lock_string (of /include/asm-i386/spinlock.h) macro definition (not clear) of version <= 2.6.8
  • From: Sushil Mayengbam <hacker.mayengbam@xxxxxxxxx>
• significance of BUF_CLEAN list
  • From: rahul dev <rahul_dev_agg@xxxxxxxxxxx>
• Re: question about __v annotation
  • From: Ryan Wang <openspace.wang@xxxxxxxxx>
• Re: question about __v annotation
  • From: Tadeusz Struk <tstruk@xxxxxxxxx>
• Re: question about __v annotation
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Writing to parallel port register
  • From: "Mohamed Thalib,,," <hmthalib@xxxxxxxxx>
• question about __v annotation
  • From: Shawn <citypw@xxxxxxxxx>
• Embedded Linux development
  • From: Pavan Kandepet <pavankp@xxxxxxxxx>
• Re: Location of source file
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• RE: kernel compilation help
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Location of source file
  • From: Pei Lin <telent997@xxxxxxxxx>
• weird way to reset a timer
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: LTIB missing packages
  • From: hmthalib <h.thalib@xxxxxxxxx>
• Re: unable to mount rootfs (was :Re: kernel compilation help)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: access to jiffies_64 atomic or not?
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• RE: kernel compilation help
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: kernel compilation help
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: unable to mount rootfs (was :Re: kernel compilation help)
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• unable to mount rootfs (was :Re: kernel compilation help)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: compiling older kernel on newer machine
  • From: mayur nande <mayur.nan@xxxxxxxxx>
• Re: access to jiffies_64 atomic or not?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: access to jiffies_64 atomic or not?
  • From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
• Re: access to jiffies_64 atomic or not?
  • From: "chiachen" <luojiazhen@xxxxxxxxx>
• Re: access to jiffies_64 atomic or not?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: any major changes in kernel timers over the last few releases?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: compiling older kernel on newer machine
  • From: mayur nande <mayur.nan@xxxxxxxxx>
• any major changes in kernel timers over the last few releases?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• access to jiffies_64 atomic or not?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• compiling older kernel on newer machine
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: kernel compilation help
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel compilation help
  • From: siddhesh divekar <siddhesh.divekar@xxxxxxxxx>
• Re: kernel compilation help
  • From: mayur nande <mayur.nan@xxxxxxxxx>
• kernel compilation help
  • From: Murali N <nalajala.murali@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Getting started with kernel development
  • From: Nicky Chorley <nick.chorley@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: Nicky Chorley <nick.chorley@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: Nicky Chorley <nick.chorley@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: Daniel Borkmann <d.borkmann@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: Nicky Chorley <nick.chorley@xxxxxxxxx>
• USB storage gadget problem
  • From: "J.H.Kim" <frog1120@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: Thomas Rega <mail@xxxxxxxxxx>
• Re: Getting started with kernel development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Getting started with kernel development
  • From: Himanshu Chauhan <himanshu@xxxxxxxxxxxxxxxx>
• Location of source file
  • From: sky knight <sky_knight02@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: David <bouncingcats@xxxxxxxxx>
• Re: Getting started with kernel development
  • From: Daniel Borkmann <d.borkmann@xxxxxxxxx>
• Getting started with kernel development
  • From: Nicky Chorley <nick.chorley@xxxxxxxxx>
• IBM Bluetooth PC Card II - configuration problem
  • From: Szigetvári János <jszigetvari@xxxxxxxxx>
• some help required in FOIP
  • From: er krishna <erkrishna@xxxxxxxxx>
• Gstreamer compilation
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: LTIB missing packages
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: LTIB missing packages
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: LTIB missing packages
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LTIB missing packages
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: LTIB missing packages
  • From: Microbit_Ubuntu <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• feasibility of initramfs support without initrd support?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Problem in makefile
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• LTIB missing packages
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Using kgdb to debug linux kernel modules
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Using kgdb to debug linux kernel modules
  • From: Grigory Makarevich <grigorymakarevich@xxxxxxxxx>
• kernel newbie column to resume in january sometime
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Kernel compilation problem.........
  • From: Rune V. Sjøen <rvsjoen@xxxxxxxxx>
• Re: Kernel compilation problem.........
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Kernel compilation problem.........
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Kernel compilation problem.........
  • From: bajrangi pandey <bajrangi12pandey@xxxxxxxxx>
• Re: private data structure [ in network driver and other driver ]
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• bluez & kernel compatibility
  • From: Arun S <inbox1.arun@xxxxxxxx>
• private data structure [ in network driver and other driver ]
  • From: er krishna <erkrishna@xxxxxxxxx>
• I/O Shared memory
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• Re: router + kernel networking
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: router + kernel networking
  • From: Ilya Dryomov <idryomov@xxxxxxxxx>
• router + kernel networking
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: What Char encoding type is used in EXT4?
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• What Char encoding type is used in EXT4?
  • From: Indraneel Mukherjee <indro.ml@xxxxxxxxx>
• sendfile / struct page confustion
  • From: Ansari Email <ansariemail@xxxxxxxxx>
• Re: Re[2]: kernel compile problem
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Problems while adding sysfs support to older device driver
  • From: Bjoern Hinrichs <bjh-kn@xxxxxxxxx>
• Re: Boting error in freescale board
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re[2]: kernel compile problem
  • From: +BigNose <bignose@xxxxxxxxxx>
• Re: What is difference between initrd and regular RAM disk?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: kernel compile problem
  • From: +BigNose <bignose@xxxxxxxxxx>
• kernel compile problem
  • From: +BigNose <bignose@xxxxxxxxxx>
• Re: page cache query
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: page cache query
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: page cache query
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: Boting error in freescale board
  • From: hmthalib <h.thalib@xxxxxxxxx>
• Re: Linux based development for New Hardware/board
  • From: Dhaval Shah <osbydhaval@xxxxxxxxx>
• Re: What is difference between initrd and regular RAM disk?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Boting error in freescale board
  • From: "chiachen" <luojiazhen@xxxxxxxxx>
• Re: Boting error in freescale board
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: Boting error in freescale board
  • From: "chiachen" <luojiazhen@xxxxxxxxx>
• What is difference between initrd and regular RAM disk?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: Boting error in freescale board
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• pcie hotplug
  • From: David Updegraff <dbu@xxxxxxxxx>
• Re: Probe method vs attach method.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Probe method vs attach method.
  • From: LKomz Komz <lkomz101@xxxxxxxxx>
• Re: page cache query
  • From: Darrin Thompson <darrinth@xxxxxxxxx>
• Re: Boting error in freescale board
  • From: abhijeet tripathi <abhijeet.tripathy@xxxxxxxxxxx>
• Re: Linux based development for New Hardware/board
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxxxxxxx>
• Re: Linux based development for New Hardware/board
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Linux based development for New Hardware/board
  • From: Alan Carvalho de Assis <acassis@xxxxxxxxx>
• Linux based development for New Hardware/board
  • From: Dhaval Shah <osbydhaval@xxxxxxxxx>
• Re: modules inside initrd
  • From: Belisko Marek <marek.belisko@xxxxxxxxx>
• modules inside initrd
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• Boting error in freescale board
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Kernel mode stack per process?
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: Kernel mode stack per process?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: How to send SCSI command from kernel thread.
  • From: Greg KH <greg@xxxxxxxxx>
• Kernel mode stack per process?
  • From: nascent mind <nascent.mind@xxxxxxxxx>
• Re: Problems while adding sysfs support to older device driver
  • From: Greg KH <greg@xxxxxxxxx>
• How to send SCSI command from kernel thread.
  • From: hari krishnan <p.harikrishnan22@xxxxxxxxx>
• Re: Problems while adding sysfs support to older device driver
  • From: Bjoern Hinrichs <bjh-kn@xxxxxxxxx>
• Re: Doubt in i2c
  • From: Nobin Mathew <nobin.mathew@xxxxxxxxx>
• Doubt in i2c
  • From: arun <p.arun@xxxxxxxxxxxxx>
• Re: 2 page kernel stacks in older kernels
  • From: Gopala Krishna <gopalakrishna.n.m@xxxxxxxxx>
• Re: Probe method vs attach method.
  • From: Pei Lin <telent997@xxxxxxxxx>
• Flag this message sendfile / struct page confustion
  • From: Ansari Email <ansariemail@xxxxxxxxx>
• Re: 2 page kernel stacks in older kernels
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: kernel panic
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• Re: 2 page kernel stacks in older kernels
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: 2 page kernel stacks in older kernels
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: Error while compiling 2.6.10 kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: Error while compiling 2.6.10 kernel
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: kernel panic
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: kernel panic
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• Re: kernel panic
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: kernel panic
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• RE: Query regarding 2.6.21.7 Compilation Patch
  • From: Himanshu Chauhan <himanshu.chauhan2@xxxxxxxxxxxx>
• Query regarding 2.6.21.7 Compilation Patch
  • From: Himanshu Chauhan <himanshu.chauhan2@xxxxxxxxxxxx>
• Query regarding large slowstart threshold value in tcp_ipv4.c and parameters returned by getsockopt
  • From: Ashwin Rao <ashwin.shirvanthe@xxxxxxxxx>
• Re: 2 page kernel stacks in older kernels
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: 2 page kernel stacks in older kernels
  • From: qieban qieban <qieban@xxxxxxxxx>
• Re: keyboard
  • From: Shahar Havivi <shaharh@xxxxxxxxx>
• 2 page kernel stacks in older kernels
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: page cache query
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: page cache query
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: page cache query
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: keyboard
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Decompressing Kernel image introduce data abort exception
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: kernel panic
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: kernel panic
  • From: "Vaughn E. Clinton" <vclinton@xxxxxxx>
• Re: kbuild - two obj's from one source
  • From: Greg KH <greg@xxxxxxxxx>
• Re: kernel panic
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• Re: slab_cache
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• kernel panic
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• Re: kbuild - two obj's from one source
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• Re: Need some help in interpreting a code snippet
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Need some help in interpreting a code snippet
  • From: Mohammed Gamal <m.gamal005@xxxxxxxxx>
• Need some help in interpreting a code snippet
  • From: Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx>
• Re: Problems while adding sysfs support to older device driver
  • From: Greg KH <greg@xxxxxxxxx>
• Re: kbuild - two obj's from one source
  • From: Greg KH <greg@xxxxxxxxx>
• Re: getting physical address acess from User space
  • From: Devesh Sharma <devesh28@xxxxxxxxx>
• getting physical address acess from User space
  • From: Vipul Jain <vipulsj@xxxxxxxxx>
• kbuild - two obj's from one source
  • From: Michal Ludvig <mludvig@xxxxxxxxxxxx>
• Re: Probe method vs attach method.
  • From: LKomz Komz <lkomz101@xxxxxxxxx>
• Re: Probe method vs attach method.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: question about vmlinux.lds.in
  • From: vichy <vichy.kuo@xxxxxxxxx>
• Re: question about vmlinux.lds.in
  • From: vichy <vichy.kuo@xxxxxxxxx>
• Re: Probe method vs attach method.
  • From: LKomz Komz <lkomz101@xxxxxxxxx>
• slab_cache
  • From: Darvin Denmian <darvin.denmian@xxxxxxxxx>
• Re: module using another module
  • From: "Matze" <mensch0815@xxxxxxxx>
• module using another module
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: what kernel subsystems use softirqs directly?
  • From: askb <askb23@xxxxxxxxx>
• Re: what kernel subsystems use softirqs directly?
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• what kernel subsystems use softirqs directly?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Problems while adding sysfs support to older device driver
  • From: Bjoern Hinrichs <bjh-kn@xxxxxxxxx>
• Re: RE: Re: Error while compiling 2.6.10 kernel
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• Re: Linux SCSI LUNs Question
  • From: Wang Jinpu <xjtuwjp@xxxxxxxxx>
• Linux SCSI LUNs Question
  • From: Vipul Jain <vipulsj@xxxxxxxxx>
• Re: keyboard
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• Re: keyboard
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: keyboard
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• RE: Re: Error while compiling 2.6.10 kernel
  • From: Mark Pan - 潘卫宾 <Mark.Pan@xxxxxxxx>
• Re: keyboard
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Re: Error while compiling 2.6.10 kernel
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• keyboard
  • From: "Herlin R. Matos Lastres" <hmatos@xxxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• RE: Finding SCSI disk geomtry using General SCSI driver.
  • From: "Mark Harvey" <mark_harvey@xxxxxxxxxxxx>
• Finding SCSI disk geomtry using General SCSI driver.
  • From: Vipul Jain <vipulsj@xxxxxxxxx>
• Re: Probe method vs attach method.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Error while compiling 2.6.10 kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Error while compiling 2.6.10 kernel
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• Re: Probe method vs attach method.
  • From: LKomz Komz <lkomz101@xxxxxxxxx>
• Re: page cache query
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• page cache query
  • From: Lal <learner.kernel@xxxxxxxxx>
• Re: Queued Spin Lock.
  • From: Michel Lespinasse <walken@xxxxxxxxxx>
• Re: Probe method vs attach method.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: Luciano Rocha <luciano@xxxxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: Bian Jiang <borderj@xxxxxxxxx>
• Re: parallel port
  • From: "Matze" <mensch0815@xxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: How does "ls" command work in Linux in detail?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• How does "ls" command work in Linux in detail?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Probe method vs attach method.
  • From: LKomz Komz <lkomz101@xxxxxxxxx>
• parallel port
  • From: Martin Knappe <martin.knappe@xxxxxxxxx>
• Re: McBSP$ on OMAP
  • From: umesh krishnan <umeshdelhi@xxxxxxxxx>
• Re: McBSP$ on OMAP
  • From: Microbit_Ubuntu_9101 <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• McBSP$ on OMAP
  • From: umesh krishnan <umeshdelhi@xxxxxxxxx>
• Re: cloud computing
  • From: Bernd Petrovitsch <bernd@xxxxxxx>
• RE: Introduction to kernel threads
  • From: "Kristian Evensen" <kristian.evensen@xxxxxxxxx>
• Re: Introduction to kernel threads
  • From: luca ellero <lroluk@xxxxxxxxx>
• Decompressing Kernel image introduce data abort exception
  • From: Michael Zhu <linuxsir320@xxxxxxxxx>
• frame buffer driver
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: linux kernel modules
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: Up to date driver-model docs?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Overwriting sys_call_table entries
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: linux kernel modules
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: tracing only direct childrens
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: Memory Management Question
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Memory Management Question
  • From: Mohammed Gamal <m.gamal005@xxxxxxxxx>
• Re: Introduction to kernel threads
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Up to date driver-model docs?
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: Up to date driver-model docs?
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Up to date driver-model docs?
  • From: Philip Downer <phil@xxxxxxxxx>
• RE: Introduction to kernel threads
  • From: "Kristian Evensen" <kristian.evensen@xxxxxxxxx>
• Re: data structure initialization
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: data structure initialization
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: data structure initialization
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: data structure initialization
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: data structure initialization
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• data structure initialization
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Overwriting sys_call_table entries
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Overwriting sys_call_table entries
  • From: Fernand LONE SANG <flone_sa@xxxxxxxxxxxxxxxxxxxxx>
• Re: linux kernel modules
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Re: linux kernel modules
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• linux kernel modules
  • From: Martin Knappe <martin.knappe@xxxxxxxxx>
• Re: Overwriting sys_call_table entries
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: tracing only direct childrens
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: tracing only direct childrens
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: tracing only direct childrens
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• tracing only direct childrens
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: Problem in Configuring UMAX Scanner
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: gpio-keys sync messages
  • From: "Matze" <mensch0815@xxxxxxxx>
• Re: Console Handover
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: gpio-keys sync messages
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxxxxxxx>
• Re: Console Handover
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxxxxxxx>
• Console Handover
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• Re: Problem in Configuring UMAX Scanner
  • From: Kousik Maiti <maiti.kousik@xxxxxxxxx>
• Overwriting sys_call_table entries
  • From: Fernand LONE SANG <flone_sa@xxxxxxxxx>
• Fwd: Accessing dentry structs and lists in the VFS
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: cloud computing
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Problem in Configuring UMAX Scanner
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: cloud computing
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: rusty russell's unreliable guide to locking still ... unreliable?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: rusty russell's unreliable guide to locking still ... unreliable?
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• rusty russell's unreliable guide to locking still ... unreliable?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Problem in Configuring UMAX Scanner
  • From: Kousik Maiti <maiti.kousik@xxxxxxxxx>
• Re: gpio-keys sync messages
  • From: "Matze" <mensch0815@xxxxxxxx>
• Re: cloud computing
  • From: Bernd Petrovitsch <bernd@xxxxxxx>
• Re: cloud computing
  • From: Mauricio Mauad Menegaz Filho <mmauad@xxxxxxxxx>
• Re: cloud computing
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Problem in Configuring UMAX Scanner
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Newbie
  • From: Pei Lin <telent997@xxxxxxxxx>
• Problem in Configuring UMAX Scanner
  • From: Kousik Maiti <maiti.kousik@xxxxxxxxx>
• Re: Newbie
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Newbie
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Linux assembly query
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: DMA issue with USB devices
  • From: Greg KH <greg@xxxxxxxxx>
• Re: DMA issue with USB devices
  • From: Asim <linkasim@xxxxxxxxx>
• Re: Newbie
  • From: abhijeet tripathi <abhijeet.tripathy@xxxxxxxxxxx>
• Re: Newbie
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• finding kernel virtual addr from physical addr of a user buffer
  • From: yogeshwar sonawane <yogyas@xxxxxxxxx>
• Re: gpio-keys sync messages
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxxxxxxx>
• gpio-keys sync messages
  • From: "Matze" <mensch0815@xxxxxxxx>
• Newbie
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Brian Gerst <brgerst@xxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: DMA issue with USB devices
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Accessing dentry structs and lists in the VFS
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Accessing dentry structs and lists in the VFS
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: Sysfs over network
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Bizarr shutdown hang behavior
  • From: roland <raw@xxxxxxxxxxxxxx>
• Re: Bizarr shutdown hang behavior
  • From: Pavan Kandepet <pavankp@xxxxxxxxx>
• Bizarr shutdown hang behavior
  • From: roland <raw@xxxxxxxxxxxxxx>
• Re: read_cache_page "asynchronous" failures
  • From: Zhu Yanhai <zhu.yanhai@xxxxxxxxx>
• Re: Sysfs over network
  • From: Patrick <patger@xxxxxxxxxx>
• bletooth under embedded device
  • From: Arun Kumar <sun_888777@xxxxxxxxx>
• Re: Sysfs over network
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: [solved] usb keyboard events dont get to the console
  • From: Markus Schwarzenberg <schwarzb@xxxxxxxxxxxxxxxxxx>
• Update the ACPI _PRT table
  • From: Matteo Foppiano <matteo.foppy@xxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Jiri Slaby <jirislaby@xxxxxxxxx>
• Sysfs over network
  • From: Patrick <kpa_info@xxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Américo Wang <xiyou.wangcong@xxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: stas <stas@xxxxxxxxxxxxx>
• Re: Query on File Creation time in Linux
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Query on File Creation time in Linux
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• read_cache_page "asynchronous" failures
  • From: Darrin Thompson <darrinth@xxxxxxxxx>
• Query on File Creation time in Linux
  • From: Indraneel Mukherjee <indro.ml@xxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Viral Mehta <viral.mehta@xxxxxxxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Viral Mehta <viral.mehta@xxxxxxxxxxxxxx>
• Re: How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• How to move two valuables to x86 CPU register ebx, ecx by using AT&A inline asm.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• DMA issue with USB devices
  • From: Asim <linkasim@xxxxxxxxx>
• Strange segmentation fault in kernel module
  • From: Kristian Evensen <kristian.evensen@xxxxxxxxx>
• Re: cloud computing
  • From: Belisko Marek <marek.belisko@xxxxxxxxx>
• usb keyboard events dont get to the console
  • From: Markus Schwarzenberg <schwarzb@xxxxxxxxxxxxxxxxxx>
• Re: mmap non-kmalloc'ed or non-vmalloc'ed buffer?
  • From: Daniel Borkmann <d.borkmann@xxxxxxxxx>
• RE: mmap non-kmalloc'ed or non-vmalloc'ed buffer?
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: mmap non-kmalloc'ed or non-vmalloc'ed buffer?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• mmap non-kmalloc'ed or non-vmalloc'ed buffer?
  • From: Daniel Borkmann <d.borkmann@xxxxxxxxx>
• Re: x86 assembly - linking order query
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: cloud computing
  • From: Ryan Moore <dogen.growkin@xxxxxxxxx>
• cloud computing
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: Is it possible to execute user application from kernel space?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• RE: x86 assembly - linking order query
  • From: <sudheer.divakaran@xxxxxxxxx>
• Re: Is it possible to execute user application from kernel space?
  • From: askb <askb23@xxxxxxxxx>
• Is it possible to execute user application from kernel space?
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• Re: Linux assembly query
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: x86 assembly - linking order query
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Linux assembly query
  • From: dinesh bhaskar <pdineshb@xxxxxxxxx>
• RE: x86 assembly - linking order query
  • From: <sudheer.divakaran@xxxxxxxxx>
• Re: x86 assembly - linking order query
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• shouldn't kobj_map.h include kobject.h?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• x86 assembly - linking order query
  • From: <sudheer.divakaran@xxxxxxxxx>
• Re: configuration of NFS root file system
  • From: Abhijeet Tripathi <abhijeet.tripathy@xxxxxxxxxxx>
• Re: configuration of NFS root file system
  • From: K R I S K <kernelbowl@xxxxxxxxx>
• using Exofs
  • From: Vineet Agarwal <checkout.vineet@xxxxxxxxx>
• RE: local_irq_disable question
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• local_irq_disable question
  • From: Lal <learner.kernel@xxxxxxxxx>
• Re: configuration of NFS root file system
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• configuration of NFS root file system
  • From: "J.H.Kim" <frog1120@xxxxxxxxx>
• Re: Allocate continuous memory and physical address.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Allocate continuous memory and physical address.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Allocate continuous memory and physical address.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Allocate continuous memory and physical address.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Re: GPL Query
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• GPL Query
  • From: LKomz Komz <lkomz101@xxxxxxxxx>
• Re: Allocate continuous memory and physical address.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Allocate continuous memory and physical address.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• Allocate continuous memory and physical address.
  • From: Johnny Hung <johnny.hacking@xxxxxxxxx>
• scatter-gather io & segments
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: How to use new SCSI API?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: MTP Class driver
  • From: Greg KH <greg@xxxxxxxxx>
• Re: AT91SAM9260 async UART
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: AT91SAM9260 async UART
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Difference between major page fault and minor page fault
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: MTP Class driver
  • From: Satheesh Kumar <mesatheesh@xxxxxxxxx>
• AT91SAM9260 async UART
  • From: "J.H.Kim" <frog1120@xxxxxxxxx>
• Re: Kernel Source code/Driver coding IDE ?? Suggest
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Kernel Source code/Driver coding IDE ?? Suggest
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Communication device interrupts to user space via real time signals
  • From: Greg KH <greg@xxxxxxxxx>
• Re: MTP Class driver
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Kernel Source code/Driver coding IDE ?? Suggest
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: Kernel Source code/Driver coding IDE ?? Suggest
  • From: Zhu Yanhai <zhu.yanhai@xxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Zhu Yanhai <zhu.yanhai@xxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Zhu Yanhai <zhu.yanhai@xxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: Kernel Source code/Driver coding IDE ?? Suggest
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Kernel Source code/Driver coding IDE ?? Suggest
  • From: Sabree Blackmon <sabreeblackmon@xxxxxxxxx>
• Kernel Source code/Driver coding IDE ?? Suggest
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: why there is ktype ?
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• RE: Introduction to kernel threads
  • From: "Kristian Evensen" <kristian.evensen@xxxxxxxxx>
• Re: Introduction to kernel threads
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Introduction to kernel threads
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• RE: Introduction to kernel threads
  • From: "Kristian Evensen" <kristian.evensen@xxxxxxxxx>
• Re: Difference between major page fault and minor page fault
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: Difference between major page fault and minor page fault
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Introduction to kernel threads
  • From: "Kristian Evensen" <kristian.evensen@xxxxxxxxx>
• why there is ktype ?
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: process to processor/core identification
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• How to use new SCSI API?
  • From: Adam Jiang <jiang.adam@xxxxxxxxx>
• Re: Some kind of driver question?
  • From: Viral Mehta <viral.mehta@xxxxxxxxxxxxxx>
• RE: 32 bit processors / 64 bit processors
  • From: "Microbit_P43000" <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Where is MMU enabled?
  • From: hmthalib <h.thalib@xxxxxxxxx>
• Re: Difference between major page fault and minor page fault
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Where is MMU enabled?
  • From: Rick Brown <rick.brown.3@xxxxxxxxx>
• Re: Difference between major page fault and minor page fault
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Difference between major page fault and minor page fault
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: Some kind of driver question?
  • From: Davidlohr Bueso <dave@xxxxxxx>
• Some kind of driver question?
  • From: Ozan Türkyılmaz <ozan.turkyilmaz@xxxxxxxxx>
• Re: process to processor/core identification
  • From: George Kadianakis <desnacked@xxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Zhu Yanhai <zhu.yanhai@xxxxxxxxx>
• RE: Calling driver functions from kernel space
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• process to processor/core identification
  • From: Anand Raj Manickam <anandrm@xxxxxxxxx>
• Re: How to disable all interrupts including scheduler
  • From: er krishna <erkrishna@xxxxxxxxx>
• How to disable all interrupts including scheduler
  • From: "J.H.Kim" <frog1120@xxxxxxxxx>
• Re: Calling driver functions from kernel space
  • From: Zhu Yanhai <zhu.yanhai@xxxxxxxxx>
• Calling driver functions from kernel space
  • From: Sam Carter <sam.w.carter@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: hmthalib <hmthalib@xxxxxxxxx>
• Re: modprobe error "No such device" udc driver
  • From: Katharina Ludwig <katharina.ludwig@xxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Doubt in sizeof () operator
  • From: hmthalib <hmthalib@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: hmthalib <hmthalib@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: vkm <viral.vkm@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: hmthalib <hmthalib@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: hmthalib <hmthalib@xxxxxxxxx>
• Re: a conceptual confusion -- bio--page --block -- buffer
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: a conceptual confusion -- bio--page --block -- buffer
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: vkm <viral.vkm@xxxxxxxxx>
• Re: modprobe error "No such device" udc driver
  • From: Thomas De Schampheleire <patrickdepinguin@xxxxxxxxx>
• Re: device still in memory after removing
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• device still in memory after removing
  • From: Mena Soliko <solikoman@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: a conceptual confusion -- bio--page --block -- buffer
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Doubt in sizeof () operator
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• Re: Re: Doubt in sizeof () operator
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• Re: Doubt in sizeof () operator
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• request_region conflict
  • From: Sonal Santan <sonal.santan@xxxxxxxxx>
• Re: modprobe error "No such device" udc driver
  • From: Katharina Ludwig <katharina.ludwig@xxxxxxxx>
• Re: a conceptual confusion -- bio--page --block -- buffer
  • From: "govind raj nayak" <govind02@xxxxxxxxxxxxxx>
• How does counter value for icmp OutEchos changes in /proc/net/snmp
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: a conceptual confusion -- bio--page --block -- buffer
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• Re: modprobe error "No such device" udc driver
  • From: Thomas De Schampheleire <patrickdepinguin@xxxxxxxxx>
• Re: a conceptual confusion -- bio--page --block -- buffer
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: a conceptual confusion -- bio--page --block -- buffer
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: a conceptual confusion -- bio--page --block -- buffer
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• a conceptual confusion -- bio--page --block -- buffer
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: modprobe error "No such device" udc driver
  • From: Katharina Ludwig <katharina.ludwig@xxxxxxxx>
• Re: modprobe error "No such device" udc driver
  • From: Pei Lin <telent997@xxxxxxxxx>
• modprobe error "No such device" udc driver
  • From: Katharina Ludwig <katharina.ludwig@xxxxxxxx>
• Re: why kernel implement "udelay" by cpu instructions?
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: JTAG debugger for MIPS platform
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• MTP Class driver
  • From: Satheesh Kumar <mesatheesh@xxxxxxxxx>
• RE: doubt abt a function in ext2
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: doubt abt a function in ext2
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• RE: doubt abt a function in ext2
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• doubt abt a function in ext2
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: JTAG debugger for MIPS platform
  • From: "Daniel (Youngwhan) Song" <breadncup@xxxxxxxxx>
• JTAG debugger for MIPS platform
  • From: Shankar Ganesh <shankarganeshk@xxxxxxxxx>
• local_irq_disable() V/S disable_irq()
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• RE: why kernel implement "udelay" by cpu instructions?
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: why kernel implement "udelay" by cpu instructions?
  • From: Bryan Donlan <bdonlan@xxxxxxxxx>
• RE: why kernel implement "udelay" by cpu instructions?
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• 2 PCI addresses for the PCI-PCI bridges?
  • From: Rick Brown <rick.brown.3@xxxxxxxxx>
• Re: why kernel implement "udelay" by cpu instructions?
  • From: loody <miloody@xxxxxxxxx>
• How the first printk work after start_kernel?
  • From: "Figo.zhang" <figo1802@xxxxxxxxx>
• Re: [uClinux-dev] Shell prompt is printed twice
  • From: Jeff Bacon <jbac.uc.dev@xxxxxxxxx>
• Re: A way to let initramfs continue as THE final root filesystem?
  • From: James DeVincentis <admin@xxxxxxxxxxx>
• Re: Communication device interrupts to user space via real time signals
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: Communication device interrupts to user space via real time signals
  • From: Greg KH <greg@xxxxxxxxx>
• Reading I/O ports with kdb
  • From: luca ellero <lroluk@xxxxxxxxx>
• Re: Communication device interrupts to user space via real time signals
  • From: अनुज <anuj01@xxxxxxxxx>
• Shell prompt is printed twice
  • From: Stephane Lambert <stephane.lambert@xxxxxxxxxx>
• A way to let initramfs continue as THE final root filesystem?
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: Virtual Memory Doubt
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Virtual Memory Doubt
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• RE: Virtual Memory Doubt
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: why kernel implement "udelay" by cpu instructions?
  • From: Pulkit Goel <vipulkit.goel@xxxxxxxxx>
• Re: Virtual Memory Doubt
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Virtual Memory Doubt
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Virtual Memory Doubt
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: why kernel implement "udelay" by cpu instructions?
  • From: Rik van Riel <riel@xxxxxxxxxx>
• why kernel implement "udelay" by cpu instructions?
  • From: loody <miloody@xxxxxxxxx>
• Re: Doubt regarindg Virtual Memory
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: Doubt regarindg Virtual Memory
  • From: Zhu Yanhai <zhu.yanhai@xxxxxxxxx>
• Re: Communication device interrupts to user space via real time signals
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Communication device interrupts to user space via real time signals
  • From: Devesh Sharma <devesh28@xxxxxxxxx>
• Re: Questions about linux scheduler
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Communication device interrupts to user space via real time signals
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Questions about linux scheduler
  • From: Daniel Rodrick <daniel.rodrick@xxxxxxxxx>
• Communication device interrupts to user space via real time signals
  • From: Devesh Sharma <devesh28@xxxxxxxxx>
• Bits of SPI data
  • From: "J.H.Kim" <frog1120@xxxxxxxxx>
• Re: Doubt regarindg Virtual Memory
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Re: Questions about linux scheduler
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: Questions about linux scheduler
  • From: Jonathan Corbet <corbet@xxxxxxx>
• IRQF_TRIGGER_* flags
  • From: Rick Brown <rick.brown.3@xxxxxxxxx>
• Questions about linux scheduler
  • From: Daniel Rodrick <daniel.rodrick@xxxxxxxxx>
• 答复: About the system call named "sys_mount".
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• What stops the vanialla kernel from being called an RTOS?
  • From: Rick Brown <rick.brown.3@xxxxxxxxx>
• Re: kernel panic about kernel unaligned access
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Re: kernel panic about kernel unaligned access
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: kernel panic about kernel unaligned access
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Bizarr shutdown hang behavior
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel panic about kernel unaligned access
  • From: loody <miloody@xxxxxxxxx>
• Bizarr shutdown hang behavior
  • From: roland <raw@xxxxxxxxxxxxxx>
• RE: Whats is the operator ##
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• RE: Whats is the operator ##
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: Whats is the operator ##
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxxxxxxx>
• Whats is the operator ##
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• what is pud in MM
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Re: kernel panic about kernel unaligned access
  • From: loody <miloody@xxxxxxxxx>
• Re: kernel panic about kernel unaligned access
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Doubt regarding page traversal
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: advice on free software
  • From: Brian Smith <pagefaulthandler@xxxxxxxxx>
• Re: kernel panic about kernel unaligned access
  • From: Xiangfu Liu <xiangfu@xxxxxxxxxxxxxxx>
• Re: kernel panic about kernel unaligned access
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• kernel panic about kernel unaligned access
  • From: loody <miloody@xxxxxxxxx>
• 答复: About the system call named "sys_mount".
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• 答复: About the system call named "sys_mount".
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• RE: ext3 writing of data before metadata in ordered mode
  • From: "Mehmet Ali Ekici" <mehmet.ekici@xxxxxxxxxxxxxxxxxxxxx>
• Re: ext3 writing of data before metadata in ordered mode
  • From: Josef Bacik <josef@xxxxxxxxxx>
• Re: ext3 writing of data before metadata in ordered mode
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• SPI doubt on AP7000
  • From: "Matze" <mensch0815@xxxxxxxx>
• Re: ext3 writing of data before metadata in ordered mode
  • From: Josef Bacik <josef@xxxxxxxxxx>
• Re: ext3 writing of data before metadata in ordered mode
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: ext3 writing of data before metadata in ordered mode
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: advice on free software
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• ext3 writing of data before metadata in ordered mode
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: new member
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• new member
  • From: Vikram Dhillon <dhillonv10@xxxxxxxxx>
• advice on free software
  • From: Brian Smith <pagefaulthandler@xxxxxxxxx>
• Re: Doubt regarding page traversal
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Doubt regarding page traversal
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• Doubt regarindg Virtual Memory
  • From: Shameem Ahamed <shameem.ahamed@xxxxxxxxx>
• how to mmap 0x1f000000 to user space?
  • From: "Figo.zhang" <figo1802@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• RE: how to clean specific module instead of clean them all
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: how to clean specific module instead of clean them all
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• Re: how to clean specific module instead of clean them all
  • From: loody <miloody@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: C <a.la.kaarta@xxxxxxxxx>
• Re: how to clean specific module instead of clean them all
  • From: Vikash Kumar <vikashskumar@xxxxxxxxx>
• how to clean specific module instead of clean them all
  • From: loody <miloody@xxxxxxxxx>
• RE: 32 bit processors / 64 bit processors
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• RE: 32 bit processors / 64 bit processors
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: C <a.la.kaarta@xxxxxxxxx>
• Re: Checking status of userspace processes
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: Checking status of userspace processes
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Checking status of userspace processes
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Checking status of userspace processes
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Ontario Linux Fest this Saturday in Toronto.
  • From: 益牙 <simonyanix@xxxxxxxxx>
• Re: Checking status of userspace processes
  • From: Bob Beers <bob.beers@xxxxxxxxx>
• Re: Checking status of userspace processes
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Checking status of userspace processes
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: Ontario Linux Fest this Saturday in Toronto.
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Ontario Linux Fest this Saturday in Toronto.
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Ontario Linux Fest this Saturday in Toronto.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Are there any places to put bug report for specific kernel versions?
  • From: Matthias Kaehlcke <matthias@xxxxxxxxxxxx>
• Are there any places to put bug report for specific kernel versions?
  • From: Peter Chen <hzpeterchen@xxxxxxxxx>
• Re: How to print Superblock(ext2) data
  • From: Vineet Agarwal <checkout.vineet@xxxxxxxxx>
• Re: How to print Superblock(ext2) data
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: How to print Superblock(ext2) data
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• How to print Superblock(ext2) data
  • From: mahesh sobale <msobale007@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: askb <askb23@xxxxxxxxx>
• Re: "kernel newbie" column on brief sabbatical
  • From: Fernando Apesteguía <fernando.apesteguia@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: Ryan Moore <dogen.growkin@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: C <a.la.kaarta@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: 益牙 <simonyanix@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: 益牙 <simonyanix@xxxxxxxxx>
• Re: 32 bit processors / 64 bit processors
  • From: Siddu <siddu.sjce@xxxxxxxxx>
• 32 bit processors / 64 bit processors
  • From: Rick Brown <rick.brown.3@xxxxxxxxx>
• Re: pdflush deprecated by per-bdi writeout
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: About the system call named "sys_mount".
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• 答复: About the system call named "sys_mount".
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• Re: max size limit for mmap MAP_ANONYMOUS in different x86_64 kernels
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• max size limit for mmap MAP_ANONYMOUS in different x86_64 kernels
  • From: Mark Farnell <mark.farnell@xxxxxxxxx>
• Re: About the system call named "sys_mount".
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: "kernel newbie" column on brief sabbatical
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Kernel thread id
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: request_mem_region
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• request_mem_region
  • From: Rick Brown <rick.brown.3@xxxxxxxxx>
• IRQF_TRIGGER on AVR32
  • From: "Matze" <mensch0815@xxxxxxxx>
• Re: About the system call named "sys_mount".
  • From: Quentin Carbonneaux <qcarbonneaux@xxxxxxxxx>
• Re: IRQF_TRIGGER on AVR32
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: IRQF_TRIGGER on AVR32
  • From: "Matze" <mensch0815@xxxxxxxx>
• Re: About the system call named "sys_mount".
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• RE: About the system call named "sys_mount".
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• 答复: About the system call named "sys_mount".
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• RE: About the system call named "sys_mount".
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• "kernel newbie" column on brief sabbatical
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• About the system call named "sys_mount".
  • From: 付新荣 <FuXinRong@xxxxxxxxxxxx>
• Re: pdflush deprecated by per-bdi writeout
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• RE: Understanding VFS & Filesystem using proc fs
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: pdflush deprecated by per-bdi writeout
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Understanding VFS & Filesystem using proc fs
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• user-to-kernel shared memory with net_device
  • From: Chris Ross <chris@xxxxxxxxxxxxxxxxxxxx>
• Re: Understanding VFS & Filesystem using proc fs
  • From: shailesh jain <coolworldofshail@xxxxxxxxx>
• Understanding VFS & Filesystem using proc fs
  • From: "Leena M." <kernmonk@xxxxxxxxx>
• Re: pdflush deprecated by per-bdi writeout
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: pdflush deprecated by per-bdi writeout
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: pdflush deprecated by per-bdi writeout
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: problem with kernel logging
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: problem with kernel logging
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• USB support
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• problem with kernel logging
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: pdflush deprecated by per-bdi writeout
  • From: Rik van Riel <riel@xxxxxxxxxxxx>
• Re: Filesystem / Partition type support in kernel
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Filesystem / Partition type support in kernel
  • From: Ole Loots <ole@xxxxxxxxxxxxx>
• Filesystem / Partition type support in kernel
  • From: Ole <ole@xxxxxxxxxxxxx>
• Re: IRQF_TRIGGER on AVR32
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• IRQF_TRIGGER on AVR32
  • From: "Matze" <mensch0815@xxxxxxxx>
• Re: @listadmin: i got blacklisted
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: @listadmin: i got blacklisted
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• @listadmin: i got blacklisted
  • From: "Matze" <mensch0815@xxxxxxxx>
• Re: sse2 in kernel code
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: sse2 in kernel code
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: sse2 in kernel code
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: Changes to a page
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• pdflush deprecated by per-bdi writeout
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Changes to a page
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• A Minimalist Approach to Character Drivers in User-Space
  • From: Bob Smith <bsmith@xxxxxxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: the sendfile function call of file_operations
  • From: "Usman S. Ansari" <uansari@xxxxxxxxx>
• Re: sse2 in kernel code
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: How to check whether executing in atomic context?
  • From: Raz <raziebe@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: sse2 in kernel code
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: CONFIG_PREEMPT is not set
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Re: How to check whether executing in atomic context?
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• CONFIG_PREEMPT is not set
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• How to check whether executing in atomic context?
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: the sendfile function call of file_operations
  • From: loody <miloody@xxxxxxxxx>
• Re: Mobile OS
  • From: Shaz <shazalive@xxxxxxxxx>
• Re: Mobile OS
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Mobile OS
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• RE: how to support long file name in vfat format under linux
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: sse2 in kernel code
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Mobile OS
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: the sendfile function call of file_operations
  • From: Raz <raziebe@xxxxxxxxx>
• the sendfile function call of file_operations
  • From: loody <miloody@xxxxxxxxx>
• Re: how to support long file name in vfat format under linux
  • From: abhijeet tripathi <abhijeet.tripathy@xxxxxxxxxxx>
• Re: Hardware question
  • From: andi <andi.platschek@xxxxxxxxx>
• Re: how to support long file name in vfat format under linux
  • From: loody <miloody@xxxxxxxxx>
• Re: Hardware question
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: how to support long file name in vfat format under linux
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Re: Mobile OS
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: how to support long file name in vfat format under linux
  • From: Rahul Tank <gr8rahul@xxxxxxxxx>
• Re: how to support long file name in vfat format under linux
  • From: Srdjan Todorovic <todorovic.s@xxxxxxxxxxxxxx>
• Re: how to support long file name in vfat format under linux
  • From: loody <miloody@xxxxxxxxx>
• how to support long file name in vfat format under linux
  • From: loody <miloody@xxxxxxxxx>
• Re: how to support long file name in vfat format under linux
  • From: loody <miloody@xxxxxxxxx>
• Re: how do tasklets queue?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: how do tasklets queue?
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: [PATCH 1/1] bt8xxgpio: Check gpiochip_remove() result
  • From: Michael Buesch <mb@xxxxxxxxx>
• Re: how do tasklets queue?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: how do tasklets queue?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: how do tasklets queue?
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• [PATCH] bt8xxgpio: Check gpiochip_remove() result
  • From: Javier Martinez Canillas <martinez.javier@xxxxxxxxx>
• Re: how do tasklets queue?
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• [PATCH Resend] bt8xxgpio: Check gpiochip_remove() result
  • From: Javier Martinez Canillas <martinez.javier@xxxxxxxxx>
• Re: /dev/console (deleted)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• [PATCH Resend] bt8xxgpio: Check gpiochip_remove() result
  • From: Javier Martinez Canillas <martinez.javier@xxxxxxxxx>
• Re: how do tasklets queue?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• [PATCH 1/1] bt8xxgpio: Check gpiochip_remove() result
  • From: Javier Martinez Canillas <martinez.javier@xxxxxxxxx>
• how do tasklets queue?
  • From: Joel Fernandes <agnel.joel@xxxxxxxxx>
• Re: Hardware question
  • From: Pei Lin <telent997@xxxxxxxxx>
• Re: Hardware question
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: preempt_disable() as synchronization tool
  • From: Pei Lin <telent997@xxxxxxxxx>
• Basic about video capture
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Hardware question
  • From: Pranith <pranith.hacks@xxxxxxxxx>
• RE: /dev/console (deleted)
  • From: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@xxxxxxxxx>
• Re: Hardware question
  • From: andi <andi.platschek@xxxxxxxxx>
• Re: USB controller driver question
  • From: Henry Gebhardt <hsggebhardt@xxxxxxxxxxxxxx>
• Re: /dev/console (deleted)
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Re: Halp required
  • From: Shreyansh Jain <shrey.linux@xxxxxxxxx>
• Re: Mobile OS
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Hardware question
  • From: Ozan Türkyılmaz <ozan.turkyilmaz@xxxxxxxxx>
• Re: Mobile OS
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Mobile OS
  • From: Pranav Peshwe <pranavpeshwe@xxxxxxxxx>
• Re: Halp required
  • From: abhijeet tripathi <abhijeet.tripathy@xxxxxxxxxxx>
• Re: Mobile OS
  • From: Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: preempt_disable() as a synchronization tool
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Halp required
  • From: abhish agarwal <abhish_agr@xxxxxxxxxxx>
• Mobile OS
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: preempt_disable() as synchronization tool
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• /dev/console (deleted)
  • From: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@xxxxxxxxx>
• Re: USB controller driver question
  • From: Pranith <pranith.hacks@xxxxxxxxx>
• Re: preempt_disable() as synchronization tool
  • From: askb <askb23@xxxxxxxxx>
• Re: preempt_disable() as a synchronization tool
  • From: askb <askb23@xxxxxxxxx>
• Re: preempt_disable() as synchronization tool
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• Repository of Active Projects
  • From: Mohit Varma <mohit.varma01@xxxxxxxxx>
• Re: C question
  • From: <microbit@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Changing Kernel 3g / 1g memory split
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: invalid storage class : error in compilation of module
  • From: chaitanya <surya.namuduri@xxxxxxxxx>
• Re: invalid storage class : error in compilation of module
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• Re: invalid storage class : error in compilation of module
  • From: Bian Jiang <borderj@xxxxxxxxx>
• Re: invalid storage class : error in compilation of module
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• invalid storage class : error in compilation of module
  • From: nidhi mittal hada <nidhimittal19@xxxxxxxxx>
• SDMK2410 Ethernet Driver
  • From: "J.H.Kim" <frog1120@xxxxxxxxx>
• SMDK2410 Ethernet Driver
  • From: "J.Hwan.Kim" <j.hwan.kim99@xxxxxxxxx>
• Re: Mounting block device fails.
  • From: Prasad Joshi <prasadjoshi124@xxxxxxxxx>
• Re: Mounting block device fails.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Mounting block device fails.
  • From: Prasad Joshi <prasadjoshi124@xxxxxxxxx>
• preempt_disable() as synchronization tool
  • From: Daniel Rodrick <daniel.rodrick@xxxxxxxxx>
• preempt_disable() as a synchronization tool
  • From: Daniel Rodrick <daniel.rodrick@xxxxxxxxx>
• USB controller driver question
  • From: Vishal Thanki <vishalthanki@xxxxxxxxx>
• kernel newbie column -- more initrd and initramfs
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: waking up processes while holding spinlock
  • From: vinit dhatrak <vinit.dhatrak@xxxxxxxxx>
• waking up processes while holding spinlock
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: Mounting block device fails.
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• splice on fat filesystem
  • From: Rahul K Patel <rahulk.patel@xxxxxxxxxxxxxx>
• Re: Changing Kernel 3g / 1g memory split
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• sse2 in kernel code
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: C question
  • From: Michał Nazarewicz <m.nazarewicz@xxxxxxxxxxx>
• RE: Changing Kernel 3g / 1g memory split
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• RE: Recursive makefiles for module spanning over multiple dir
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• RE: Recursive makefiles for module spanning over multiple dir
  • From: "Rajat Jain" <Rajat.Jain@xxxxxxxxxxxx>
• Re: Changing Kernel 3g / 1g memory split
  • From: Jason Nymble <jason.nymble@xxxxxxxxx>
• Re: Recursive makefiles for module spanning over multiple dir
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: C question
  • From: Kalpesh Rathod <kalpeshrathod@xxxxxxxxx>