Mail Index

• Thread Index

• regarding differences between 2.4 & 2.6 kernels
  • From: satya narayana
• Re: regarding differences between 2.4 & 2.6 kernels
  • From: Fernando Apesteguía
• Re: interruptible_sleep_on() vs wait_event_interruptible()
  • From: Arjan van de Ven
• Virus found in the message
  • From: Mail Admin
• Message deleted
  • From: Mail Admin
• Re: interruptible_sleep_on() vs wait_event_interruptible()
  • From: Arjan van de Ven
• Re: interruptible_sleep_on() vs wait_event_interruptible()
  • From: Christian Boon
• Secure Dereference of NULL-Pointer when using list.h
  • From: Hendrik Post
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Ricard Wanderlof
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Anupam Kapoor
• Help regarding the socket tos
  • From: Sandeep Mailk
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Hendrik Post
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Ricard Wanderlof
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Jinesh K J
• /dev during boot
  • From: Hayim Shaul
• Re: /dev during boot
  • From: Greg KH
• QUARANTINED: Kernelnewbies@nl.linux.org
  • From: WorkgroupMail Content Filter
• query regarding daemon process
  • From: chaitanya ralegaonkar
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Ricard Wanderlof
• Re: query regarding daemon process
  • From: Kedar Patil (ààààà)
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Jinesh K J
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Ricard Wanderlof
• overhead read()
  • From: Chris
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Jinesh K J
• Re: overhead read()
  • From: Bhanu Kalyan Chetlapalli
• RTP
  • From: Sam
• GNU Assembler
  • From: Ashok kumar
• Re: GNU Assembler
  • From: Shakthi Kannan
• Interrupt routine accessing i2c bus
  • From: john bogus
• Re: Interrupt routine accessing i2c bus
  • From: Shakthi Kannan
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Ricard Wanderlof
• Re: RTP
  • From: Sandeep Mailk
• list_for_each_entry() question
  • From: Bahadir Balban
• Re: Secure Dereference of NULL-Pointer when using list.h
  • From: Jinesh K J
• Re: RTP
  • From: Rodrigo Baroni
• OFFERTA
  • From: deskspa
• Re: Help regarding the socket tos
  • From: Sandeep Mailk
• slack in /proc/meminfo
  • From: nunash
• Re: slack in /proc/meminfo
  • From: nunash
• Re: RTP
  • From: Sam
• Unknown email address
  • From: Postmaster
• usb device driver queries
  • From: pradeep singh
• Re: usb device driver queries
  • From: Jinesh K J
• Re: slack in /proc/meminfo
  • From: Jinesh K J
• Re: usb device driver queries
  • From: pradeep singh
• likely, unlikely and builtin_expect()
  • From: Diego Woitasen
• Re: likely, unlikely and builtin_expect()
  • From: mohanlal jangir
• Re: likely, unlikely and builtin_expect()
  • From: JuanJo Ciarlante
• Re: usb device driver queries
  • From: Shakthi Kannan
• Re: slack in /proc/meminfo
  • From: s prashant
• Re: Interrupt routine accessing i2c bus
  • From: john bogus
• Re: usb device driver queries
  • From: Jinesh K J
• Question on platform_driver probe in backlight driver
  • From: Claudio Nieder
• Re: RTP
  • From: Sam
• Please confirm (conf#a2610f687a51780a4f790c08ff1f74c8)
  • From: Juniper certification
• Re: Question on platform_driver probe in backlight driver
  • From: Dmitry Torokhov
• Getting error scheduling while atomic.
  • From: Ranjan Sinha
• Re: usb device driver queries
  • From: pradeep singh
• Re: usb device driver queries
  • From: pradeep singh
• libusb and usbdevfs
  • From: pradeep singh
• Re: libusb and usbdevfs
  • From: pradeep singh
• kernel 2.2 + running bdflush when there are no free buffers in getblk.
  • From: Pawel
• Re: graphic cards drivers on linux
  • From: Jan Hudec
• /proc/pid/status & slack
  • From: nunash
• User-Mode-Linux & kernel debugging : new tutorial [in portuguese only for while]
  • From: Rodrigo Baroni
• Re: libusb and usbdevfs
  • From: Jinesh K J
• Why do we need /dev
  • From: Jinesh K J
• Re: Why do we need /dev
  • From: Greg KH
• Re: Why do we need /dev
  • From: Anupam Kapoor
• Re: Why do we need /dev
  • From: Jinesh K J
• Re: Why do we need /dev
  • From: borasahin
• Re: Why do we need /dev
  • From: Vikram Auradkar
• Re: Why do we need /dev
  • From: Jinesh K J
• Re: Why do we need /dev
  • From: pradeep singh
• Re: libusb and usbdevfs
  • From: pradeep singh
• Re: Why do we need /dev
  • From: Arjan van de Ven
• Re: Why do we need /dev
  • From: Raseel Bhagat
• Re: Why do we need /dev
  • From: Raseel Bhagat
• Tab Completion
  • From: Jakko Pastuchio
• Re: Why do we need /dev
  • From: Greg KH
• Re: Tab Completion
  • From: rohit hooda
• Re: Tab Completion
  • From: Girish Venkatachalam
• Re: Tab Completion
  • From: Jakko Pastuchio
• inode numbers
  • From: Jakko Pastuchio
• Re: inode numbers
  • From: Avishay Traeger
• Re: Question on platform_driver probe in backlight driver
  • From: Claudio Nieder
• Re: Why do we need /dev
  • From: Jinesh K J
• Re: libusb and usbdevfs
  • From: Jinesh K J
• Re: inode numbers
  • From: Jakko Pastuchio
• Re: Re: inode numbers
  • From: rohit hooda
• Re: inode numbers
  • From: Vincent Thomasset
• Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Amol Lad
• Re: Userspace <-> communication
  • From: Jesper Juhl
• Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Jesper Juhl
• Returned mail: see transcript for details
  • From: investor_relations
• Re: Userspace <-> communication
  • From: s prashant
• Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: s prashant
• R: Userspace <-> communication
  • From: Perego Paolo Franco
• Re: Userspace <-> communication
  • From: Bhanu Kalyan Chetlapalli
• Re: Userspace <-> communication
  • From: Prasenjit Manna
• Re: R: Userspace <-> communication
  • From: Prasenjit Manna
• Re: Userspace <-> communication
  • From: Girish Venkatachalam
• Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Girish Venkatachalam
• Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Girish Venkatachalam
• Re: Re: inode numbers
  • From: Jakko Pastuchio
• Re: Re: inode numbers
  • From: Avishay Traeger
• Re: libusb and usbdevfs
  • From: Greg KH
• Re: Why do we need /dev
  • From: Greg KH
• Re: Re: Re: inode numbers
  • From: rohit hooda
• how to view??
  • From: Cheatah 0#@!^
• Re: Re: Userspace <-> communication
  • From: rohit hooda
• touchscreen driver: what to do to connect them to a device?
  • From: Claudio Nieder
• Re: Userspace <-> communication
  • From: Seongsu Lee
• Re: inode numbers
  • From: Rik van Riel
• Re: Why do we need /dev
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Jinesh K J
• E-mail recusado - Refused e-mail
  • From: mm
• Re: inode numbers
  • From: Jakko Pastuchio
• Re: Userspace <-> communication
  • From: Girish Venkatachalam
• Need to allocate memory always in interrupt handler which MUST succeed.
  • From: Parav Pandit
• Re :Re: Re: Userspace <-> communication
  • From: rohit hooda
• Re: libusb and usbdevfs
  • From: pradeep singh
• Re: Need to allocate memory always in interrupt handler which MUST succeed.
  • From: pradeep singh
• Re: Need to allocate memory always in interrupt handler which MUST succeed.
  • From: Amol Lad
• Re: Need to allocate memory always in interrupt handler which MUST succeed.
  • From: Parav Pandit
• Re: how to view??
  • From: Thomas Petazzoni
• Re: Need to allocate memory always in interrupt handler which MUST succeed.
  • From: Amol Lad
• RDMA buffer registration
  • From: Jos De Graeve
• Re: Re :Re: Re: Userspace <-> communication
  • From: Jinesh K J
• Re: Userspace <-> communication
  • From: Jinesh K J
• Re: libusb and usbdevfs
  • From: Jinesh K J
• Re: Need to allocate memory always in interrupt handler which MUST succeed.
  • From: Jiri Kosina
• Re: Need to allocate memory always in interrupt handler which MUST succeed.
  • From: Jiri Kosina
• Re: Userspace <-> communication
  • From: Girish Venkatachalam
• Re: libusb and usbdevfs
  • From: pradeep singh
• Re: Need to allocate memory always in interrupt handler which MUST succeed.
  • From: Arjan van de Ven
• Re: libusb and usbdevfs
  • From: Greg KH
• Re: Why do we need /dev
  • From: Greg KH
• Re: Userspace <-> communication
  • From: Greg KH
• Re: libusb and usbdevfs
  • From: pradeep singh
• SATA Controller driver on 2.6
  • From: Rizvan
• Re: SATA Controller driver on 2.6
  • From: Jiri Kosina
• init stuck when console is redirected to the serial port
  • From: Siddharth Taneja
• How to read execute_command?
  • From: Tetsuo Handa
• Re: libusb and usbdevfs
  • From: Greg KH
• Re: libusb and usbdevfs
  • From: pradeep singh
• disable config_4kstacks
  • From: Huub
• Re: libusb and usbdevfs
  • From: Greg KH
• Hugetlbfs support error.
  • From: atoka wotsa
• Hugetlbfs support error.
  • From: atoka wotsa
• PAE enabling
  • From: atoka wotsa
• Re: Hugetlbfs support error.
  • From: Nish Aravamudan
• Re: disable config_4kstacks
  • From: Adrian Bunk
• GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jakko Pastuchio
• Re: PAE enabling
  • From: Fawad Lateef
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jinesh K J
• Re: libusb and usbdevfs
  • From: pradeep singh
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jakko Pastuchio
• memory management project
  • From: Onkar N Mahajan
• Re: memory management project
  • From: Amol Lad
• usb-skeleton.c query
  • From: pradeep singh
• Re: usb-skeleton.c query
  • From: Greg KH
• Re: usb-skeleton.c query
  • From: Jim Bauer
• Virtual Memory doubt
  • From: Madhukar
• usb serial driver query
  • From: pradeep singh
• Re: usb serial driver query
  • From: Greg KH
• Re: usb serial driver query
  • From: pradeep singh
• Re: usb-skeleton.c query
  • From: pradeep singh
• Re: memory management project
  • From: Ashok Sharma
• Re: usb serial driver query
  • From: Greg KH
• "Bad page state in process" after unmapping DMA buffer
  • From: Mike DeKoker
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Florin Malita
• Re: Virtual Memory doubt
  • From: Hayim Shaul
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Greg KH
• udev problems
  • From: Dinesh Bhat
• Re: udev problems
  • From: Maxim Wexler
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jinesh K J
• Re: Virtual Memory doubt
  • From: Rodrigo Baroni
• Re: usb serial driver query
  • From: pradeep singh
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Greg KH
• Re: udev problems
  • From: Greg KH
• Re: Increase of HZ
  • From: suman adak
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jinesh K J
• Re: Increase of HZ
  • From: Jinesh K J
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jakko Pastuchio
• probe not called for usb serial driver
  • From: pradeep singh
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Momchil Velikov
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Momchil Velikov
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jinesh K J
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Ricard Wanderlof
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jakko Pastuchio
• net_device fields
  • From: Hayim Shaul
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jakko Pastuchio
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Momchil Velikov
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jakko Pastuchio
• /proc/pids
  • From: Jakko Pastuchio
• Re: /proc/pids
  • From: suman adak
• Help locating linux/init/main.c
  • From: amit mehta
• Re: Help locating linux/init/main.c
  • From: Shakthi Kannan
• Re: Help locating linux/init/main.c
  • From: Jinesh K J
• Re: Help locating linux/init/main.c
  • From: amit mehta
• Re: Help locating linux/init/main.c
  • From: Jinesh K J
• many minor page fault
  • From: Bizhan Gholikhamseh \(bgholikh\)
• FC6: #define for _syscall? not found in /usr/include/asm/unistd.h
  • From: penguin-newbie
• Re: FC6: #define for _syscall? not found in /usr/include/asm/unistd.h
  • From: penguin-newbie
• Re: FC6: #define for _syscall? not found in /usr/include/asm/unistd.h
  • From: Jinesh K J
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jinesh K J
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Mark Hounschell
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Mark Hounschell
• probe not returning
  • From: pradeep singh
• Re: /proc/pids
  • From: Jakko Pastuchio
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Momchil Velikov
• Re: FC6: #define for _syscall? not found in /usr/include/asm/unistd.h
  • From: Tetsuo Handa
• Re: probe not returning
  • From: pradeep singh
• Re: FC6: #define for _syscall? not found in /usr/include/asm/unistd.h
  • From: Nish Aravamudan
• splint giving error message
  • From: amit mehta
• Re: splint giving error message
  • From: Avishay Traeger
• Re: splint giving error message
  • From: Nish Aravamudan
• Re: many minor page fault
  • From: Mulyadi Santosa
• Re: /proc/pids
  • From: Mulyadi Santosa
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Greg KH
• Re: many minor page fault
  • From: Mulyadi Santosa
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Momchil Velikov
• platform_driver_register() questions
  • From: Curran, Dominic
• Re: many minor page fault
  • From: Rik van Riel
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jinesh K J
• Re: splint giving error message
  • From: amit mehta
• Re: splint giving error message
  • From: Ricard Wanderlof
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Mark Hounschell
• help in block drivers
  • From: Rahul Theraja
• Re: GPLv3 / FSF vs. OSS/ TivO ?
  • From: Jinesh K J
• Re: help in block drivers
  • From: Shakthi Kannan
• Re: help in block drivers
  • From: Rahul Theraja
• RE: many minor page fault
  • From: Bizhan Gholikhamseh \(bgholikh\)
• Returned mail: see transcript for details
  • From: forbesford
• Re: help in block drivers
  • From: Fawad Lateef
• Re: help in block drivers
  • From: Fawad Lateef
• Problem with kernel 2.6.19-rc2, include/linux/config.h and drivers
  • From: Jose Luis Alarcon Sanchez
• kernelnewbies-bounce@nl.linux.org
  • From: Ananda Krishnan
• Re: Problem with kernel 2.6.19-rc2, include/linux/config.h and drivers
  • From: JuanJo Ciarlante
• Question regarding Kernel Messages
  • From: Jesús Velazquez
• Re: Question regarding Kernel Messages
  • From: Dinesh
• Re: FC6: #define for _syscall? not found in /usr/include/asm/unistd.h
  • From: Tetsuo Handa
• Re: How to read execute_command?
  • From: Tetsuo Handa
• Re: Question regarding Kernel Messages
  • From: Shakthi Kannan
• Re: Question regarding Kernel Messages
  • From: Jesús Velazquez
• Returned mail: Data format error
  • From: audio . lyric
• MDaemon Notification -- Attachment Removed
  • From: Postmaster
• Re: help in block drivers
  • From: Rahul
• Preemptible Linux (Ingo Molnar's preemption patch)
  • From: Seongsu Lee
• hugetlb pages!
  • From: sudhnesh adapawar
• Changing the base page size !
  • From: sudhnesh adapawar
• Re: Preemptible Linux (Ingo Molnar's preemption patch)
  • From: Ohad Ben-Cohen
• You sent potentially unsafe content: Returned mail: see transcript for details
  • From: Virus canner
• Re: Preemptible Linux (Ingo Molnar's preemption patch)
  • From: Mark Hounschell
• Re: Changing the base page size !
  • From: Rik van Riel
• Re: Preemptible Linux (Ingo Molnar's preemption patch)
  • From: Mouhammad Tayseer Alquoatli
• Documentation
  • From: Alan Menegotto
• wait_event_interruptible_timeout related query
  • From: Dinesh
• correct way to initialize pointer...
  • From: Mandeep Sandhu
• Alert from eSafe: document.zip\document.scr Infected with Win32.Mydoom.m
  • From: esafe
• Re: correct way to initialize pointer...
  • From: Om Narasimhan
• Re: correct way to initialize pointer...
  • From: Momchil Velikov
• Re: correct way to initialize pointer...
  • From: Mandeep Sandhu
• Re: correct way to initialize pointer...
  • From: Momchil Velikov
• Re: correct way to initialize pointer...
  • From: Ricard Wanderlof
• Re: correct way to initialize pointer...
  • From: Mandeep Sandhu
• Re: help in block drivers
  • From: Rahul
• Re: help in block drivers
  • From: Fawad Lateef
• Sysfs question
  • From: Ivan Korzakow
• VIrtual filesystem Doubt
  • From: atoka wotsa
• Re: VIrtual filesystem Doubt
  • From: Shakthi Kannan
• IRQ_HANDLED related query
  • From: Dinesh
• Re: IRQ_HANDLED related query
  • From: Shakthi Kannan
• access_ok
  • From: Talib Alim
• Re: access_ok
  • From: Om Narasimhan
• Re: IRQ_HANDLED related query
  • From: Dinesh Bhat
• Kernel Threading
  • From: endeavor john
• Re: IRQ_HANDLED related query
  • From: Thomas Petazzoni
• LIST_HEAD macros and family
  • From: pradeep singh
• Need help
  • From: Prasenjit Manna
• Re: IRQ_HANDLED related query
  • From: Dinesh
• Re: Need help
  • From: Kris van Rens
• > Viren-Warnung <
  • From: mailadmin
• Re: Kernel Threading
  • From: Mulyadi Santosa
• Re: LIST_HEAD macros and family
  • From: Mulyadi Santosa
• Re: Need help
  • From: Prasenjit Manna
• Re: LIST_HEAD macros and family
  • From: pradeep singh
• Re: Need help
  • From: suman adak
• what enhancements are needed in hugetlbfs???
  • From: adheer chandravanshi
• Test Message
  • From: Bithika Khargharia
• Re: what enhancements are needed in hugetlbfs???
  • From: Rik van Riel
• Reading the LRU Active and Incative List
  • From: Bithika Khargharia
• Re: Reading the LRU Active and Incative List
  • From: Mulyadi Santosa
• Re: Reading the LRU Active and Incative List
  • From: Bithika Khargharia
• Re: Re: Reading the LRU Active and Incative List
  • From: Mulyadi Santosa
• Re: Re: Reading the LRU Active and Incative List
  • From: Bithika Khargharia
• page->map_count & zone active list
  • From: Bithika Khargharia
• huge pages access..
  • From: toka
• Re: huge pages access..
  • From: Sandeep Kumar
• which is begin of kernel subsystem
  • From: liang yuanen
• Re: which is begin of kernel subsystem
  • From: Sandeep Kumar
• mmap of a file that is partially in cache already
  • From: Prashant Anand
• Fork applications with huge pages !
  • From: sudhnesh adapawar
• How raw read/write operations on block device works.
  • From: Manish Regmi
• Re: Real Time Behaviour of Linux
  • From: liang yuanen
• remap_pfn_range : Cant access mapped memory!
  • From: Sudharsan Rangarajan
• Re: how 2 debug a core file in linux
  • From: botron
• Re: Cross Compiler for ARM
  • From: botron
• remap_pfn_range : Cant access mapped memory!
  • From: Sudharsan Rangarajan
• Proc File System
  • From: Bithika Khargharia
• Re: Proc File System
  • From: Greg KH
• Re: Documentation
  • From: botron
• Re: Documentation
  • From: Jesper Juhl
• Re: Documentation
  • From: Jesper Juhl
• Message could not be delivered
  • From: username
• Reading OOPS Message
  • From: Vaibhav Nipunage
• RE: Reading OOPS Message
  • From: Perego Paolo Franco
• Re: remap_pfn_range : Cant access mapped memory!
  • From: Anumolu Sudheer
• Re: Reading OOPS Message
  • From: Kris van Rens
• Re: which is begin of kernel subsystem
  • From: liang yuanen
• Does generic ide driver use libata
  • From: Manish Regmi
• Re: Reading OOPS Message
  • From: Anumolu Sudheer
• Re: remap_pfn_range : Cant access mapped memory!
  • From: Sudharsan Rangarajan
• irq nobody cared error
  • From: Dinesh
• Physical Address for pfn
  • From: Bithika Khargharia
• Memory snapshot
  • From: Arun Babu