Linux Kernel Newbies

• Thread Index

• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Valdis.Kletnieks@xxxxxx
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Valdis.Kletnieks@xxxxxx
• usb_driver hotplug probe callback
  • From: Jaret Flores <jarflores@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Skb Documentation?
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• RE: Skb Documentation?
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: [PATCH] usb: Fix switch statement in ohci-tmio.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Skb Documentation?
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Skb Documentation?
  • From: Jerry Snitselaar <dev@xxxxxxxxxxxxxx>
• Re: Skb Documentation?
  • From: Valdis.Kletnieks@xxxxxx
• Re: Skb Documentation?
  • From: leo kirotawa <kirotawa@xxxxxxxxx>
• Skb Documentation?
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Option CONFIG_DEBUG_SET_MODULE_RONX not working for kernel 3.10
  • From: Valdis.Kletnieks@xxxxxx
• Re: Questions about Kernel Memory that I didn't find answers in Google - Please Help
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Option CONFIG_DEBUG_SET_MODULE_RONX not working for kernel 3.10
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: Build Warnings
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Build Warnings
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Strategies for accessing driver data from file operations!?
  • From: Greg KH <greg@xxxxxxxxx>
• Understanding page statistics
  • From: Martin Ichilevici de Oliveira <iomartin@xxxxxxxxxxxx>
• [PATCH] staging: Check for Null return of fw_download_code
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• [PATCH] staging: Check for Null return of fw_download_code
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Forget this patch ( Error with checkpatch)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Valdis.Kletnieks@xxxxxx
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Valdis.Kletnieks@xxxxxx
• Re: [PATCH] staging: Check for Null return of fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• [PATCH] staging: Check for Null return of fw_download_code
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Jerry Snitselaar <dev@xxxxxxxxxxxxxx>
• RE: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Max Filippov <jcmvbkbc@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Philipp Muhoray <philipp.muhoray@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Valdis.Kletnieks@xxxxxx
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Max Filippov <jcmvbkbc@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Valdis.Kletnieks@xxxxxx
• Re: Strategies for accessing driver data from file operations!?
  • From: Daniel Hilst Selli <danielhilst@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Valdis.Kletnieks@xxxxxx
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Forget this Patch( not checkpatched)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCH] staging: Check for Null return of allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Jerry Snitselaar <dev@xxxxxxxxxxxxxx>
• Re: Questions about Kernel Memory that I didn't find answers in Google - Please Help
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Valdis.Kletnieks@xxxxxx
• Re: [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Valdis.Kletnieks@xxxxxx
• RE: [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Nicholas Krause <xerofoify@xxxxxxxxx>
• Re: [PATCHv3] staging: Check for Null allocated skb in fw_download_code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Assorted newb questions
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Strategies for accessing driver data from file operations!?
  • From: Greg KH <greg@xxxxxxxxx>
• Assorted newb questions
  • From: Jaret Flores <jarflores@xxxxxxxxx>
• Strategies for accessing driver data from file operations!?
  • From: Daniel Hilst Selli <danielhilst@xxxxxxxxx>
• Re: How to add x32 ABI support to PCI driver
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to add x32 ABI support to PCI driver
  • From: Omkar Houddin <ophouddin22@xxxxxxxxx>
• Re: How to add x32 ABI support to PCI driver
  • From: Greg KH <greg@xxxxxxxxx>
• How to add x32 ABI support to PCI driver
  • From: Omkar Houddin <ophouddin22@xxxxxxxxx>
• Re: Where is the source code of udev?
  • From: Saket Sinha <saket.sinha89@xxxxxxxxx>
• Re: Where is the source code of udev?
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Where is the source code of udev?
  • From: Greg Kroah-Hartman <greg@xxxxxxxxx>
• Re: Where is the source code of udev?
  • From: Saket Sinha <saket.sinha89@xxxxxxxxx>
• Questions about Tasklets and other Bottom Halves
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• CentOS 7.0 NFS dual mount
  • From: Saket Sinha <saket.sinha89@xxxxxxxxx>
• On platform device template.
  • From: mind entropy <mindentropy@xxxxxxxxx>
• Re: Formula One Scheduler (was Re: Help with git)
  • From: Philipp Muhoray <philipp.muhoray@xxxxxxxxx>
• Re: Formula One Scheduler (was Re: Help with git)
  • From: Lidza Louina <lidza.louina@xxxxxxxxx>
• Re: Formula One Scheduler (was Re: Help with git)
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Formula One Scheduler (was Re: Help with git)
  • From: Valdis.Kletnieks@xxxxxx
• Re: Formula One Scheduler (was Re: Help with git)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Formula One Scheduler (was Re: Help with git)
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Reading Code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Reading Code
  • From: Pol Eyschen <poleyschen@xxxxxxxxx>
• Re: Reading Code
  • From: Pol Eyschen <poleyschen@xxxxxxxxx>
• Reading Code
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Help with git
  • From: Valdis.Kletnieks@xxxxxx
• Re: Help with git
  • From: Valdis.Kletnieks@xxxxxx
• Re: Help with git
  • From: Valdis.Kletnieks@xxxxxx
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Help with git
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Valdis.Kletnieks@xxxxxx
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Nuno Martins <nuno.m.g.martins@xxxxxxxxx>
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Usb module loading
  • From: selva <selvabe99@xxxxxxxxx>
• Re: Usb module loading
  • From: selva <selvabe99@xxxxxxxxx>
• Re: Usb module loading
  • From: Valdis.Kletnieks@xxxxxx
• Re: Usb module loading
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• Re: Usb module loading
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Usb module loading
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Usb module loading
  • From: selva <selvabe99@xxxxxxxxx>
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Valdis.Kletnieks@xxxxxx
• Re: Help with git
  • From: Valdis.Kletnieks@xxxxxx
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Questions about fork and scheduler
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Valdis.Kletnieks@xxxxxx
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Help with git
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Help with git
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Delivery Status Notification (Failure)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Questions about struct task_struct
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Delivery Status Notification (Failure)
  • From: Valdis.Kletnieks@xxxxxx
• Re: Questions about struct task_struct
  • From: Valdis.Kletnieks@xxxxxx
• Re: Delivery Status Notification (Failure)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: how do I port from 2.6.32 kernel to 3.11. kernel
  • From: Valdis.Kletnieks@xxxxxx
• Re: how do I port from 2.6.32 kernel to 3.11. kernel
  • From: Omkar Houddin <ophouddin22@xxxxxxxxx>
• Re: how do I port from 2.6.32 kernel to 3.11. kernel
  • From: Saket Sinha <saket.sinha89@xxxxxxxxx>
• how do I port from 2.6.32 kernel to 3.11. kernel
  • From: Omkar Houddin <ophouddin22@xxxxxxxxx>
• Re: Delivery Status Notification (Failure)
  • From: Pramod Gurav <pramod.gurav.etc@xxxxxxxxx>
• Re: Delivery Status Notification (Failure)
  • From: priyaranjan <priyaranjan45678@xxxxxxxxx>
• Re: Questions about struct task_struct
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Questions about struct task_struct
  • From: Andev <debiandev@xxxxxxxxx>
• Re: Questions about struct task_struct
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Questions about struct task_struct
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Questions about struct task_struct
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• Re: Delivery Status Notification (Failure)
  • From: Valdis.Kletnieks@xxxxxx
• Re: Work (really slow directory access on ext4)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Delivery Status Notification (Failure)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Lidza Louina <lidza.louina@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Lidza Louina <lidza.louina@xxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Regarding bluez stack in linux kernel
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Valdis.Kletnieks@xxxxxx
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Josh Carlson <joshcarlson3@xxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Regarding bluez stack in linux kernel
  • From: Vivek Panwar <vivekpanwar2008@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Andev <debiandev@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Pramod Gurav <pramod.gurav.etc@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Eudyptula Challenge status
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Build Error in Linux-next, intel ethernet driver
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Build Error in Linux-next, intel ethernet driver
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Build Error in Linux-next, intel ethernet driver
  • From: Jeff Kirsher <jeffrey.t.kirsher@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Eudyptula Challenge status
  • From: Raphael Philipe <rapphil@xxxxxxxxx>
• Re: Eudyptula Challenge status
  • From: Robin Schroer <sulamiification@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Eudyptula Challenge status
  • From: Raphael Philipe <rapphil@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Valdis.Kletnieks@xxxxxx
• Re: Bad Patches and Issues with other devolopers
  • From: Rohan Puri <rohan.puri15@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Trace Help
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Trace Help
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• Re: Bad Patches and Issues with other devolopers
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Bad Patches and Issues with other devolopers
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Build Error in Linux-next, intel ethernet driver
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• CPU throttling vs. clock scaling.
  • From: StephanT <stman937-linewbie@xxxxxxxxx>
• Network driver ( dma, iomem.. )
  • From: Oscar Salvador <osalvador.vilardaga@xxxxxxxxx>
• [PATCH] drivers: net: ethernet: intel: i40e: Fix missing uapi/linux/dcbnl.h include in i40e_fcoe.c
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Configure git send mail for yahoo email
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: Questions about Kernel Memory that I didn't find answers in Google - Please Help
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Porting PCi driver from 2.6.32 to 3.x kernel version
  • From: Omkar Houddin <ophouddin22@xxxxxxxxx>
• Re: Configure git send mail for yahoo email
  • From: Valdis.Kletnieks@xxxxxx
• Re: Configure git send mail for yahoo email
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: Configure git send mail for yahoo email
  • From: Valdis.Kletnieks@xxxxxx
• Configure git send mail for yahoo email
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: Where is the source code of udev?
  • From: Greg Kroah-Hartman <greg@xxxxxxxxx>
• Re: Linux filesystem configuration infrastructure
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Questions about Kernel Memory that I didn't find answers in Google - Please Help
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Where is the source code of udev?
  • From: Valdis.Kletnieks@xxxxxx
• Re: Linux filesystem configuration infrastructure
  • From: Valdis.Kletnieks@xxxxxx
• Where is the source code of udev?
  • From: Julio Faracco <jcfaracco@xxxxxxxxx>
• Linux filesystem configuration infrastructure
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: Questions about Kernel Memory that I didn't find answers in Google - Please Help
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Questions about Kernel Memory that I didn't find answers in Google - Please Help
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: How to implement a tty serial driver for RFC2217 networked serial port access devices?
  • From: Valdis.Kletnieks@xxxxxx
• How to implement a tty serial driver for RFC2217 networked serial port access devices?
  • From: TJ <linux@xxxxxx>
• Re: Kernelnewbies Digest, Vol 45, Issue 1
  • From: Vishwas Srivastava <vishu.kernel@xxxxxxxxx>
• Re: Kernel Networking Ideas???
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: userspace stack start and end
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: userspace stack start and end
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Kernel Networking Ideas???
  • From: Aniket Shinde <universalvirus.ani@xxxxxxxxx>
• Re: apt-get is not working properly
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: apt-get is not working properly
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Process simulator
  • From: Raghavendra <arrao@xxxxxxx>
• Process simulator
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• apt-get is not working properly
  • From: Niamathullah sharief <newbiesha@xxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Makedumpfile from Raw file
  • From: enjoy mindful <enjoymindful@xxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: Henry Hallam <henry@xxxxxxxxxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Makedumpfile from Raw file
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Makedumpfile from Raw file
  • From: Real Name <enjoymindful@xxxxxxxxx>
• Makedumpfile from Raw file
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: /sys documentation
  • From: Greg KH <greg@xxxxxxxxx>
• /sys documentation
  • From: David kiarie <davidkiarie4@xxxxxxxxx>
• Re: HugePage by default
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: building kernel with -O
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: IRQ mismatch ifconfig and /proc/interrupts
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: building kernel with -O
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: building kernel with -O
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: HugePage by default
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: rootkits blocking using virtualization??
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: HugePage by default
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: rootkits blocking using virtualization??
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: HugePage by default
  • From: Valdis.Kletnieks@xxxxxx
• Re: HugePage by default
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: HugePage by default
  • From: Valdis.Kletnieks@xxxxxx
• Re: Work (really slow directory access on ext4)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: HugePage by default
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: HugePage by default
  • From: Valdis.Kletnieks@xxxxxx
• Re: blocking rootkits using virtualization
  • From: Valdis.Kletnieks@xxxxxx
• Re: Work (really slow directory access on ext4)
  • From: Valdis.Kletnieks@xxxxxx
• HugePage by default
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• blocking rootkits using virtualization
  • From: Aniket Shinde <universalvirus.ani@xxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: building kernel with -O
  • From: Valdis.Kletnieks@xxxxxx
• Re: building kernel with -O
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: building kernel with -O
  • From: Valdis.Kletnieks@xxxxxx
• building kernel with -O
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: global descriptor table in X86 Linux
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: Doubt Regarding Floating Point Arithmetic
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: How to implement a driver's read and write operations with synchronization properly
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: Doubt Regarding Floating Point Arithmetic
  • From: Prasad Ram <prasad.ram126@xxxxxxxxx>
• Re: Doubt Regarding Floating Point Arithmetic
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: How to implement a driver's read and write operations with synchronization properly
  • From: Valdis.Kletnieks@xxxxxx
• Re: How to implement a driver's read and write operations with synchronization properly
  • From: Anh Le <anhlq2110@xxxxxxxxx>
• Re: How to implement a driver's read and write operations with synchronization properly
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: How to implement a driver's read and write operations with synchronization properly
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: How to implement a driver's read and write operations with synchronization properly
  • From: Anh Le <anhlq2110@xxxxxxxxx>
• Re: How to implement a driver's read and write operations with synchronization properly
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: opening a file second time using vi on LCD console hangs the system
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: How to implement a driver's read and write operations with synchronization properly
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• How to implement a driver's read and write operations with synchronization properly
  • From: Anh Le <anhlq2110@xxxxxxxxx>
• opening a file second time using vi on LCD console hangs the system
  • From: Chan Kim <ckim@xxxxxxxxxx>
• Re: userspace stack start and end
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• global descriptor table in X86 Linux
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: Kernelnewbies Digest, Vol 44, Issue 51
  • From: Vishwas Srivastava <vishu.kernel@xxxxxxxxx>
• Re: Kernelnewbies Digest, Vol 44, Issue 51
  • From: Vishwas Srivastava <vishu.kernel@xxxxxxxxx>
• RE: Kernelnewbies Digest, Vol 44, Issue 51
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: doubt with git and linux-next
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: userspace stack start and end
  • From: anupam kapoor <anupam.kapoor@xxxxxxxxx>
• Re: userspace stack start and end
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: userspace stack start and end
  • From: anupam kapoor <anupam.kapoor@xxxxxxxxx>
• Re: Problem facing while running checkpatch.pl on linux-next tree
  • From: anish singh <anish198519851985@xxxxxxxxx>
• userspace stack start and end
  • From: Xin Tong <trent.tong@xxxxxxxxx>
• Re: Problem facing while running checkpatch.pl on linux-next tree
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• Re: Problem facing while running checkpatch.pl on linux-next tree
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Problem facing while running checkpatch.pl on linux-next tree
  • From: Rahul Garg <rahul.lnmiit@xxxxxxxxx>
• Re: Work
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Work
  • From: Yi Li <lovelylich@xxxxxxxxx>
• Re: Kernelnewbies Digest, Vol 44, Issue 51
  • From: Vishwas Srivastava <vishu.kernel@xxxxxxxxx>
• Re: New Kernel-newbies site
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Work (really slow directory access on ext4)
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Work
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Work
  • From: Valdis.Kletnieks@xxxxxx
• Re: Work
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Work
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Work
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: New Kernel-newbies site
  • From: Andrey Utkin <andrey.krieger.utkin@xxxxxxxxx>
• Re: New Kernel-newbies site
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: New Kernel-newbies site
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• New Kernel-newbies site
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: doubt with git and linux-next
  • From: Valdis.Kletnieks@xxxxxx
• Re: Work
  • From: Valdis.Kletnieks@xxxxxx
• Re: Work
  • From: Valdis.Kletnieks@xxxxxx
• Re: Work
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Work
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: doubt with git and linux-next
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: doubt with git and linux-next
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: doubt with git and linux-next
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: doubt with git and linux-next
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• doubt with git and linux-next
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• IRQ mismatch ifconfig and /proc/interrupts
  • From: Oscar Salvador <osalvador.vilardaga@xxxxxxxxx>
• Re: Work
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Work
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Work
  • From: ravi ranjan Mishra <raviranjanmishra24@xxxxxxxxx>
• Re: Help with flame wars
  • From: anish singh <anish198519851985@xxxxxxxxx>
• Re: Work
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• hacking kernel-3.x with ncc
  • From: Real Name <enjoymindful@xxxxxxxxx>
• Re: Task 1 of Eudyptula Challenge
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: How to force my usb mouse using a kernel module created by myself?
  • From: Julio Faracco <jcfaracco@xxxxxxxxx>
• Re: How to force my usb mouse using a kernel module created by myself?
  • From: Bobby Abraham <bobbyabhm@xxxxxxxxx>
• Re: Task 1 of Eudyptula Challenge
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Task 1 of Eudyptula Challenge
  • From: Jeshwanth Kumar N K <jeshkumar555@xxxxxxxxx>
• Re: Task 1 of Eudyptula Challenge
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Task 1 of Eudyptula Challenge
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• How to force my usb mouse using a kernel module created by myself?
  • From: Julio Faracco <jcfaracco@xxxxxxxxx>
• Re: printk or pr_<level>?
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Work
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Work
  • From: Andev <debiandev@xxxxxxxxx>
• Re: Work
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Work
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Work
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Work
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: [PowerPC] - Define error in arch/arch/powerpc/boot/io.h ??
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: [PowerPC] - Define error in arch/arch/powerpc/boot/io.h ??
  • From: Valdis.Kletnieks@xxxxxx
• [PATCH] powerpc: fix wrong defintion in boot/io.h
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: [PowerPC] - Define error in arch/arch/powerpc/boot/io.h ??
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: [PowerPC] - Define error in arch/arch/powerpc/boot/io.h ??
  • From: Kristof Provost <kristof@xxxxxxxxxx>
• [PowerPC] - Define error in arch/arch/powerpc/boot/io.h ??
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Help with flame wars
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Help with flame wars
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Help with flame wars
  • From: David kiarie <davidkiarie4@xxxxxxxxx>
• Help with flame wars
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: Doubt Regarding Floating Point Arithmetic
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Doubt Regarding Floating Point Arithmetic
  • From: me storage <me.storage126@xxxxxxxxx>
• Re: printk or pr_<level>?
  • From: Raphael Silva <raphaelcampos.rp@xxxxxxxxx>
• Re: printk or pr_<level>?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: printk or pr_<level>?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: question about kref API
  • From: Valdis.Kletnieks@xxxxxx
• Re: printk or pr_<level>?
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: printk or pr_<level>?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: printk or pr_<level>?
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: printk or pr_<level>?
  • From: Fernando Apesteguía <fernando.apesteguia@xxxxxxxxx>
• Re: printk or pr_<level>?
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: question about kref API
  • From: "'Greg KH'" <greg@xxxxxxxxx>
• printk or pr_<level>?
  • From: Raphael Silva <raphaelcampos.rp@xxxxxxxxx>
• RE: question about kref API
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: question about kref API
  • From: "'Greg KH'" <greg@xxxxxxxxx>
• RE: question about kref API
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• RE: question about kref API
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: wait_event_* and wake_up_*
  • From: Pranith Kumar <pranith@xxxxxxxxxx>
• Re: Doubt Regarding Floating Point Arithmetic
  • From: Greg KH <greg@xxxxxxxxx>
• Doubt Regarding Floating Point Arithmetic
  • From: me storage <me.storage126@xxxxxxxxx>
• Re: wait_event_* and wake_up_*
  • From: Mohammad Merajul Islam Molla <meraj.enigma@xxxxxxxxx>
• wait_event_* and wake_up_*
  • From: Pranith Kumar <pranith@xxxxxxxxxx>
• Re: usb serial programming
  • From: "Amadeus W.M." <amadeus84@xxxxxxxxxxx>
• Re: usb serial programming
  • From: "Amadeus W.M." <amadeus84@xxxxxxxxxxx>
• Re: question about kref API
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Path of network packet in kernel
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• RE: question about kref API
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: Confused by function names cpuidle_install_idle_handler/cpuidle_uninstall_idle_handler
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: Confused by function names cpuidle_install_idle_handler/cpuidle_uninstall_idle_handler
  • From: Mohammad Merajul Islam Molla <meraj.enigma@xxxxxxxxx>
• Re: Confused by function names cpuidle_install_idle_handler/cpuidle_uninstall_idle_handler
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: Confused by function names cpuidle_install_idle_handler/cpuidle_uninstall_idle_handler
  • From: Mohammad Merajul Islam Molla <meraj.enigma@xxxxxxxxx>
• Re: Path of network packet in kernel
  • From: Anil Joshi <aj27744@xxxxxxxxx>
• Re: Confused by function names cpuidle_install_idle_handler/cpuidle_uninstall_idle_handler
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: usb serial programming
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: question about kref API
  • From: Greg KH <greg@xxxxxxxxx>
• question about kref API
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: usb serial programming
  • From: Greg KH <greg@xxxxxxxxx>
• Re: usb serial programming
  • From: Bruce Rowen <browen@xxxxxxxxxxxx>
• Re: usb serial programming
  • From: "Amadeus W.M." <amadeus84@xxxxxxxxxxx>
• Re: usb serial programming
  • From: Greg KH <greg@xxxxxxxxx>
• Re: usb serial programming
  • From: "Amadeus W.M." <amadeus84@xxxxxxxxxxx>
• Re: usb serial programming
  • From: "Amadeus W.M." <amadeus84@xxxxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Greg KH <greg@xxxxxxxxx>
• Re: usb serial programming
  • From: Bruce Rowen <browen@xxxxxxxxxxxx>
• Re: usb serial programming
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Hillf Danton <dhillf@xxxxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• usb serial programming
  • From: "Amadeus W.M." <amadeus84@xxxxxxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: How to decode a kernel symbol
  • From: Masami Ichikawa <masami256@xxxxxxxxx>
• How to decode a kernel symbol
  • From: Santhosh Kumar <forwardinglnx@xxxxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Greg KH <greg@xxxxxxxxx>
• module_param does not work in Ubuntu 13.10 - Kernel 3.10.0-4
  • From: dora babu <dora.nitw@xxxxxxxxx>
• Confused by function names cpuidle_install_idle_handler/cpuidle_uninstall_idle_handler
  • From: Mohammad Merajul Islam Molla <meraj.enigma@xxxxxxxxx>
• Re: How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Andrey Utkin <andrey.krieger.utkin@xxxxxxxxx>
• Where find Linux Kernel Development Jobs
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• How to automate checkpatch && get_maintainers && git send-email of commits range?
  • From: Andrey Utkin <andrey.krieger.utkin@xxxxxxxxx>
• Re: hi , question function of net_rx(struct net_device *dev)
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• hi , question function of net_rx(struct net_device *dev)
  • From: lx <lxlenovostar@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: Exporting ioctls from out-of-tree module to userspace
  • From: Daniel Hilst Selli <danielhilst@xxxxxxxxx>
• Re: downstream pci walk
  • From: Amerei Acuna <amerei@xxxxxxxxx>
• Re: Exporting ioctls from out-of-tree module to userspace
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Re: downstream pci walk
  • From: Amerei Acuna <amerei@xxxxxxxxx>
• Re: downstream pci walk
  • From: Valdis.Kletnieks@xxxxxx
• downstream pci walk
  • From: Amerei Acuna <amerei@xxxxxxxxx>
• Exporting ioctls from out-of-tree module to userspace
  • From: Daniel Hilst Selli <danielhilst@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Abhishek Sharma <asharma.es@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: Add Data to packet header
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: John de la Garza <john@xxxxxxxxx>
• Re: Add Data to packet header
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Add Data to packet header
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: How to prevent a module from unloading when in used
  • From: Chetan Nanda <chetannanda@xxxxxxxxx>
• Re: Path of network packet in kernel
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Re: Path of network packet in kernel
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• RE: Path of network packet in kernel
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Kinka Huang <kinkabrain@xxxxxxxxx>
• Re: Path of network packet in kernel
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: Path of network packet in kernel
  • From: Mohammad Merajul Islam Molla <meraj.enigma@xxxxxxxxx>
• Path of network packet in kernel
  • From: Anil Joshi <aj27744@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• Problems with Linux next tree
  • From: Lucas Tanure <ltanure@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Prabhakar Lad <prabhakar.csengg@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Prabhakar Lad <prabhakar.csengg@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Alexey Tulia <alexey.tulia@xxxxxxxxx>
• Re:Re: what does nr_iowait_cpu() do?
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Problems with Linux next tree
  • From: Stone Kang <stonekyx@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: 黄钦佳 <kinkabrain@xxxxxxxxx>
• Re: what does nr_iowait_cpu() do?
  • From: Mohammad Merajul Islam Molla <meraj.enigma@xxxxxxxxx>
• Re: what does nr_iowait_cpu() do?
  • From: Mohammad Merajul Islam Molla <meraj.enigma@xxxxxxxxx>
• Re: what does nr_iowait_cpu() do?
  • From: Andev <debiandev@xxxxxxxxx>
• Re: what does nr_iowait_cpu() do?
  • From: Andev <debiandev@xxxxxxxxx>
• Re: Using /tmp for temprory storage
  • From: Valdis.Kletnieks@xxxxxx
• Re: Problems with Linux next tree
  • From: Valdis.Kletnieks@xxxxxx
• Re: Problems with Linux next tree
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Peter Senna Tschudin <peter.senna@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Benedict Börger <benedict.boerger@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Problems with Linux next tree
  • From: Prabhakar Lad <prabhakar.csengg@xxxxxxxxx>
• Problems with Linux next tree
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: [PATCH] title: no lookup_page for if statement
  • From: Andev <debiandev@xxxxxxxxx>
• Using /tmp for temprory storage
  • From: sagar hu <hugarsagar@xxxxxxxxxxx>
• what does nr_iowait_cpu() do?
  • From: Mohammad Merajul Islam Molla <meraj.enigma@xxxxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Re: some project
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: some project
  • From: Safarin Samsudin <safarin87@xxxxxxxxx>
• Re: some project
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• some project
  • From: Oscar Salvador <osalvador.vilardaga@xxxxxxxxx>
• Re:Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Re:Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Question on path mtu and IP fragmentation in Linux kernel 3.0
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: linux-header files.
  • From: Greg KH <greg@xxxxxxxxx>
• linux-header files.
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH] checkpatch: Remove unnecessary + after {8,8}
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: Do per cpu variables need to be atomic?
  • From: Christoph Lameter <cl@xxxxxxxxxx>
• Re: Do per cpu variables need to be atomic?
  • From: Christoph Lameter <cl@xxxxxxxxxx>
• Re: Do per cpu variables need to be atomic?
  • From: Christoph Lameter <cl@xxxxxxxxxx>
• Do per cpu variables need to be atomic?
  • From: Pranith Kumar <pranith@xxxxxxxxxx>
• Question on path mtu and IP fragmentation in Linux kernel 3.0
  • From: Sudharsan Vijayaraghavan <sudvijayr@xxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Eudyptula Challenge
  • From: karthik nayak <karthik.188@xxxxxxxxx>
• question about mmc_rescan function
  • From: Chan Kim <ckim@xxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] checkpatch: Remove unnecessary + after {8,8}
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] reformat_with_checkpatch: Add automation to checkpatch
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Eudyptula Challenge
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Eudyptula Challenge
  • From: Jake Mitchell <jake@xxxxxxxxxxxxxxxxxxxx>
• Re: Re:Practical way to rename kernel-release on custom kernel
  • From: Safarin <safarin87@xxxxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Eudyptula Challenge
  • From: Narendra Joshi <quote.narendra@xxxxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Re:Re:Practical way to rename kernel-release on custom kernel
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Dave Tian <dave.jing.tian@xxxxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Re:Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Re: More than 9 days on task 06 Eudyptula Challenge
  • From: karthik nayak <karthik.188@xxxxxxxxx>
• Re: More than 9 days on task 06 Eudyptula Challenge
  • From: Greg Peter <greg.petr@xxxxxxxxx>
• Re: Practical way to rename kernel-release on custom kernel
  • From: Anil Shashikumar Belur <askb23@xxxxxxxxx>
• Re:Practical way to rename kernel-release on custom kernel
  • From: shhuiw <shhuiw@xxxxxxx>
• Re:Re: memory dump problem
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Do per cpu variables need to be atomic?
  • From: Pranith Kumar <pranith@xxxxxxxxxx>
• Re: Do per cpu variables need to be atomic?
  • From: Pranith Kumar <pranith@xxxxxxxxxx>
• Re: Practical way to rename kernel-release on custom kernel
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Practical way to rename kernel-release on custom kernel
  • From: Safarin <safarin87@xxxxxxxxx>
• Re: memory dump problem
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re:Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re:Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Greg KH <greg@xxxxxxxxx>
• Memory allocation problems on RHEL 6.3 kernel version 2.6.32-279.el6.x86_64
  • From: Amit Agarwal <amit@xxxxxxxxxxxxxxxxxx>
• Working on NoMoreModuleVmalloc Project
  • From: shashank karkare <karkareshashank@xxxxxxxxx>
• Re:Re: Re: Make queues in kernel space
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: USB forceful removal
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Re: View device <=> IOMMU mapping table
  • From: Real Name <enjoymindful@xxxxxxxxx>
• Re: View device <=> IOMMU mapping table
  • From: Ahmed A <ahmedcali@xxxxxxxxx>
• Re: Re: Make queues in kernel space
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: View device <=> IOMMU mapping table
  • From: Real Name <enjoymindful@xxxxxxxxx>
• View device <=> IOMMU mapping table
  • From: Ahmed A <ahmedcali@xxxxxxxxx>
• Re:memory dump problem
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: USB forceful removal
  • From: Greg KH <greg@xxxxxxxxx>
• Re: USB forceful removal
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: USB forceful removal
  • From: Greg KH <greg@xxxxxxxxx>
• USB forceful removal
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• RE: Linux Kernel Module program to obtain domain name from IP
  • From: Hettiarachchige Hasitha Shan <hh_shan@xxxxxxxx>
• memory dump problem
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: ptrace and signal handlers.
  • From: manty kuma <mantykuma@xxxxxxxxx>
• Re: Xserver on framebuffer (/dev/fbX)
  • From: Praveen Kumar Pendyala <praveendath92@xxxxxxxxxx>
• Re: Re: Linux Kernel Module program to obtain domain name from IP
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Re: Linux Kernel Module program to obtain domain name from IP
  • From: Kristof Provost <kristof@xxxxxxxxxx>
• Re: Xserver on framebuffer (/dev/fbX)
  • From: Laurent Navet <laurent.navet@xxxxxxxxx>
• Xserver on framebuffer (/dev/fbX)
  • From: Praveen Kumar Pendyala <praveendath92@xxxxxxxxxx>
• Re:Re: Linux Kernel Module program to obtain domain name from IP
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Linux Kernel Module program to obtain domain name from IP
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re:Linux Kernel Module program to obtain domain name from IP
  • From: shhuiw <shhuiw@xxxxxxx>
• current->exit_code Where does this get initialised?
  • From: manty kuma <mantykuma@xxxxxxxxx>
• Linux Kernel Module program to obtain domain name from IP
  • From: Hettiarachchige Hasitha Shan <hh_shan@xxxxxxxx>
• DMAR:[fault reason 02] Present bit in context entry is clear error
  • From: Ahmed A <ahmedcali@xxxxxxxxx>
• Re: USB file mmap
  • From: Jeshwanth Kumar N K <jeshkumar555@xxxxxxxxx>
• Re: USB file mmap
  • From: Greg Kroah-Hartman <greg@xxxxxxxxx>
• Re: USB file mmap
  • From: Greg Kroah-Hartman <greg@xxxxxxxxx>
• Re: USB file mmap
  • From: Greg KH <greg@xxxxxxxxx>
• USB file mmap
  • From: Jeshwanth Kumar N K <jeshkumar555@xxxxxxxxx>
• Re:differences between async_schedule and async_schedule_domain
  • From: shhuiw <shhuiw@xxxxxxx>
• differences between async_schedule and async_schedule_domain
  • From: vichy <vichy.kuo@xxxxxxxxx>
• Re:Re: Make queues in kernel space
  • From: shhuiw <shhuiw@xxxxxxx>
• Re: Getting an obscure driver into mainline
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Make queues in kernel space
  • From: Freeman Zhang <freeman.zhang1992@xxxxxxxxx>
• Make queues in kernel space
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Getting an obscure driver into mainline
  • From: Kieran Kunhya <kieran618@xxxxxxxxxxxxxx>
• Re: How to use keyring in the kernel?
  • From: Freeman Zhang <freeman.zhang1992@xxxxxxxxx>
• Re: How to use keyring in the kernel?
  • From: Valdis.Kletnieks@xxxxxx
• How to use keyring in the kernel?
  • From: Freeman Zhang <freeman.zhang1992@xxxxxxxxx>
• Re: Eudyptula Challenge
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Eudyptula Challenge
  • From: me storage <me.storage126@xxxxxxxxx>
• Re: DMA over USB
  • From: Raghavendra <arrao@xxxxxxx>
• Re: DMA over USB
  • From: Greg KH <greg@xxxxxxxxx>
• Re: DMA over USB
  • From: Raghavendra <arrao@xxxxxxx>
• Re: DMA over USB
  • From: Raghavendra <arrao@xxxxxxx>
• Re: DMA over USB
  • From: Greg KH <greg@xxxxxxxxx>
• Re: DMA over USB
  • From: Raghavendra <arrao@xxxxxxx>
• RE: DMA over USB
  • From: Chan Kim <ckim@xxxxxxxxxx>
• Re: DMA over USB
  • From: Greg KH <greg@xxxxxxxxx>
• Re: DMA over USB
  • From: Greg KH <greg@xxxxxxxxx>
• Re: DMA over USB
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• DMA over USB
  • From: Raghavendra <arrao@xxxxxxx>
• Re: sysfs bind/unbind attributes usage
  • From: Bjørn Mork <bjorn@xxxxxxx>
• sysfs bind/unbind attributes usage
  • From: Raghavendra <arrao@xxxxxxx>
• Query regarding suspend/resume support in MMC
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Re: Eudyptula Challenge Query
  • From: Morgan Stuar <morgansstuartdev@xxxxxxxxx>
• Re: Eudyptula Challenge Query
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Eudyptula Challenge Query
  • From: Narendra Joshi <quote.narendra@xxxxxxxxx>
• usb mass storage ADSC cmd
  • From: Dave Tian <dave.jing.tian@xxxxxxxxx>
• Re: Delay in Printk Messages.
  • From: mhornung.linux@xxxxxxxxx
• Re: Delay in Printk Messages.
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Delay in Printk Messages.
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Delay in Printk Messages.
  • From: Arun Kumar <arunkr.linux@xxxxxxxxx>
• Re: Eudyptula Challenge How To Prepare
  • From: karthik nayak <karthik.188@xxxxxxxxx>
• Re: Kernel memory leak
  • From: Anil Shashikumar Belur <askb23@xxxxxxxxx>
• Kernel memory leak
  • From: Santhosh Kumar <forwardinglnx@xxxxxxxxx>
• Eudyptula Challenge How To Prepare
  • From: me storage <me.storage126@xxxxxxxxx>
• Re:Eudyptula Challenge
  • From: wei zhang <asuka.com@xxxxxxx>
• Re: More than 9 days on task 06 Eudyptula Challenge
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Eudyptula Challenge
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Query regarding ARP request on a multi-homed system
  • From: Chaitra Ramaiah <linux.delve@xxxxxxxxx>
• Re: Eudyptula Challenge
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Eudyptula Challenge
  • From: Narendra Joshi <quote.narendra@xxxxxxxxx>
• Re: More than 9 days on task 06 Eudyptula Challenge
  • From: Dave Tian <dave.jing.tian@xxxxxxxxx>
• Re: More than 9 days on task 06 Eudyptula Challenge
  • From: Fernando Apesteguía <fernando.apesteguia@xxxxxxxxx>
• Re: More than 9 days on task 06 Eudyptula Challenge
  • From: Dave Tian <dave.jing.tian@xxxxxxxxx>
• More than 9 days on task 06 Eudyptula Challenge
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: Query regarding ARP request on a multi-homed system
  • From: Dave Tian <dave.jing.tian@xxxxxxxxx>
• Diff between various CPU masks
  • From: Vignesh Radhakrishnan <vignesh1192@xxxxxxxxx>
• Re:Query regarding ARP request on a multi-homed system
  • From: "wei zhang" <asuka.com@xxxxxxx>
• Re: Query regarding ARP request on a multi-homed system
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Query regarding ARP request on a multi-homed system
  • From: ankur dwivedi <ankurengg2003@xxxxxxxxx>
• Query regarding ARP request on a multi-homed system
  • From: Chaitra Ramaiah <linux.delve@xxxxxxxxx>
• Re: Usb block driver to store file
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Eudyptula Challenge
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Eudyptula Challenge
  • From: Javier <quaere1verum@xxxxxxxxx>
• Re: Eudyptula Challenge
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Eudyptula Challenge
  • From: Javier <quaere1verum@xxxxxxxxx>
• Suspend/Resume support for PCI
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Re: About bio_endio
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: about pr_debug
  • From: lx <lxlenovostar@xxxxxxxxx>
• Re: about pr_debug
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• Re: about pr_debug
  • From: lx <lxlenovostar@xxxxxxxxx>
• Re: code location where memory for page structures is allocated.
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: about pr_debug
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: Eudyptula Challenge Task 02 Doubt
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: about pr_debug
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: Eudyptula Challenge Task 02 Doubt
  • From: Nada Saif <nada.saif7@xxxxxxxxx>
• Re: about pr_debug
  • From: anish singh <anish198519851985@xxxxxxxxx>
• Re: Eudyptula Challenge Task 02 Doubt
  • From: Nada Saif <nada.saif7@xxxxxxxxx>
• Re: about pr_debug
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• Usb block driver to store file
  • From: ravi ranjan Mishra <raviranjanmishra24@xxxxxxxxx>
• Re: about pr_debug
  • From: Real Name <enjoymindful@xxxxxxxxx>
• about pr_debug
  • From: lx <lxlenovostar@xxxxxxxxx>
• Re: Building a software serial driver
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: About bio_endio
  • From: Alvin Abitria <abitria.alvin@xxxxxxxxx>
• Re: Building a software serial driver
  • From: Torrie Fischer <tdfischer@xxxxxxxxxxxxxx>
• Re: About bio_endio
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: About bio_endio
  • From: Alvin Abitria <abitria.alvin@xxxxxxxxx>
• Re: Building a software serial driver
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: code location where memory for page structures is allocated.
  • From: Karaoui mohamed lamine <moharaka@xxxxxxxxx>
• Re: Building a software serial driver
  • From: Torrie Fischer <tdfischer@xxxxxxxxxxxxxx>
• Re: code location where memory for page structures is allocated.
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: code location where memory for page structures is allocated.
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• code location where memory for page structures is allocated.
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: Building a software serial driver
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: About bio_endio
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: Getting started with kernel programming..
  • From: Javier <quaere1verum@xxxxxxxxx>
• Getting started with kernel programming..
  • From: Murtaza Amravatiwala <murtazaamravatiwala@xxxxxxxxx>
• Building a software serial driver
  • From: Torrie Fischer <tdfischer@xxxxxxxxxxxxxx>
• bio_endio error codes
  • From: Alvin Abitria <abitria.alvin@xxxxxxxxx>
• About bio_endio
  • From: Alvin Abitria <abitria.alvin@xxxxxxxxx>
• Re: TASK05
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: how to test the vanilla kernel
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: how to test the vanilla kernel
  • From: Kai Bojens <kb@xxxxxxxxxx>
• Re: how to test the vanilla kernel
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: how to test the vanilla kernel
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Re: how to test the vanilla kernel
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• how to test the vanilla kernel
  • From: shubham k <skaushal.lk@xxxxxxxxx>
• Re: Are Small Changes in kernel accepted as patches
  • From: karthik <karthik.188@xxxxxxxxx>
• Re: Are Small Changes in kernel accepted as patches
  • From: Valdis.Kletnieks@xxxxxx
• Re: Are Small Changes in kernel accepted as patches
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Are Small Changes in kernel accepted as patches
  • From: Jeff Kirsher <jeffrey.t.kirsher@xxxxxxxxx>
• Are Small Changes in kernel accepted as patches
  • From: karthik <karthik.188@xxxxxxxxx>
• Re: How to get the average/max process scheduling latency
  • From: Valdis.Kletnieks@xxxxxx
• Re: issues dealing with kobjects
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Understanding #ifdef in .h files
  • From: Harold André <harold.andre@xxxxxx>
• Re: How to get the average/max process scheduling latency
  • From: Teto <mattator@xxxxxxxxx>
• Re: Understanding #ifdef in .h files
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: Understanding #ifdef in .h files
  • From: Harold André <harold.andre@xxxxxx>
• Re: TASK05
  • From: parinay <parinay@xxxxxxxxx>
• Re: TASK05
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: TASK05
  • From: karthik nayak <karthik.188@xxxxxxxxx>
• Re: TASK05
  • From: Fernando Apesteguía <fernando.apesteguia@xxxxxxxxx>
• Re: TASK05
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• TASK05
  • From: Akam <azurelustre@xxxxxxxxx>
• Re: Understanding #ifdef in .h files
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Understanding #ifdef in .h files
  • From: Harold André <harold.andre@xxxxxx>
• Re: issues dealing with kobjects
  • From: Raghavendra <arrao@xxxxxxx>
• Re: issues dealing with kobjects
  • From: enjoy mindful <enjoymindful@xxxxxxxxx>
• issues dealing with kobjects
  • From: Raghavendra <arrao@xxxxxxx>
• Re: pow calculation in kernel
  • From: John de la Garza <john@xxxxxxxxx>
• pow calculation in kernel
  • From: "=?gb18030?b?1cXqzw==?=" <zganghanhan@xxxxxxxxxxx>
• Re: How to get the average/max process scheduling latency
  • From: Valdis.Kletnieks@xxxxxx
• Unsuccessful transactions during usb enumeration
  • From: "Ranjith T. C." <ranjith.tc@xxxxxxxxxxxxx>
• Re: Why the page tables are needed for lowmem?
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• RE: Unsuccessful transactions during usb enumeration
  • From: "Ranjith T. C." <ranjith.tc@xxxxxxxxxxxxx>
• How is memory allocated between the different TCP queues ?
  • From: Teto <mattator@xxxxxxxxx>
• How to get the average/max process scheduling latency
  • From: Teto <mattator@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: Why the page tables are needed for lowmem?
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Why the page tables are needed for lowmem?
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Valdis.Kletnieks@xxxxxx
• Re: Eudyptula Challenge Task 01
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: out-of-tree configuration
  • From: john bougs <bogusemail98230@xxxxxxxxx>
• Re: out-of-tree configuration
  • From: Anders Darander <anders.darander@xxxxxxxxx>
• Re: out-of-tree configuration
  • From: Valdis.Kletnieks@xxxxxx
• Re: out-of-tree configuration
  • From: john bougs <bogusemail98230@xxxxxxxxx>
• Re: out-of-tree configuration
  • From: Anders Darander <anders.darander@xxxxxxxxx>
• out-of-tree configuration
  • From: John Bougs <bogusemail98230@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: Unsuccessful transactions during usb enumeration
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: Unsuccessful transactions during usb enumeration
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Unsuccessful transactions during usb enumeration
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: Unsuccessful transactions during usb enumeration
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Adding new board support
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: SOC: Zedboard: Driver question
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: Unsuccessful transactions during usb enumeration
  • From: Greg KH <greg@xxxxxxxxx>
• Unsuccessful transactions during usb enumeration
  • From: "Ranjith T. C." <ranjith.tc@xxxxxxxxxxxxx>
• Re: Kernel Kconfig doubt..
  • From: Abhishek Sharma <asharma.es@xxxxxxxxx>
• Re: Kernel Kconfig doubt..
  • From: karthik nayak <karthik.188@xxxxxxxxx>
• Re: Kernel Kconfig doubt..
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Anurudh Tiwari <anurudhtripathi@xxxxxxxxx>
• Re: Kernel Kconfig doubt..
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Kernel Kconfig doubt..
  • From: siva sangeetha <coolgeetha.ece@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Vlad Ungureanu <vvu@xxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Re: How to capture channel 2 's frames when wireless interface was set to channel 1
  • From: "jiangtao.jit" <jiangtao.jit@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: How to capture channel 2 's frames when wireless interface was set to channel 1
  • From: Henry Hallam <henry@xxxxxxxxxxxxxxxx>
• Re: Lxc vs openvz
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Linked lists for userspace programs in Linux
  • From: Valdis.Kletnieks@xxxxxx
• Re: Eudyptula Challenge Task 01
  • From: Oussama Jabbari <oussama.jabbari@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Chen Weixiang <weixiangchen@xxxxxxxxx>
• Lxc vs openvz
  • From: Grzegorz Dwornicki <gd1100@xxxxxxxxx>
• Re: Linked lists for userspace programs in Linux
  • From: Chandrasekaran Sivakumar <chandru.a6@xxxxxxxxx>
• Re: Fwd: Question about USB hotplug
  • From: Simon Guo <wei.guo.simon@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Kristofer Hallin <kristofer.hallin@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: non-static init in a basic kernel module
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• How to capture channel 2 's frames when wireless interface was set to channel 1
  • From: "jiangtao.jit" <jiangtao.jit@xxxxxxxxx>
• Re: Linked lists for userspace programs in Linux
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Linked lists for userspace programs in Linux
  • From: Valdis.Kletnieks@xxxxxx
• Linked lists for userspace programs in Linux
  • From: Chandrasekaran Sivakumar <chandru.a6@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: How to use kernel crypto
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: How to use kernel crypto
  • From: Freeman Zhang <freeman.zhang1992@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Abhishek Sharma <asharma.es@xxxxxxxxx>
• Re: How to use kernel crypto
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: Adding new board support
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: Fwd: Question about USB hotplug
  • From: Greg KH <greg@xxxxxxxxx>
• How to use kernel crypto
  • From: Freeman Zhang <freeman.zhang1992@xxxxxxxxx>
• Re: Putting a thread to sleep using schedule() is foolproof?
  • From: Joshi <joshiiitr@xxxxxxxxx>
• Fwd: Question about USB hotplug
  • From: Simon Guo <wei.guo.simon@xxxxxxxxx>
• Re: why a static function is in kernel symbol table
  • From: Ji Li <lijimlee@xxxxxxxxx>
• Question about USB hotplug
  • From: Simon Guo <wei.guo.simon@xxxxxxxxx>
• Re: Unable to access mounted sd card partition on resume from hibernate
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Re: USB Device Driver
  • From: Vlad Ungureanu <vvu@xxxxxxx>
• Re: USB Device Driver
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Unable to access mounted sd card partition on resume from hibernate
  • From: Valdis.Kletnieks@xxxxxx
• Re: SOC: Zedboard: Driver question
  • From: Josh Cartwright <joshc@xxxxxxxxxxxx>
• Re: USB Device Driver
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Re: Disabling a BH : spin_lock_bh or local_bh_disable.
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Bjørn Mork <bjorn@xxxxxxx>
• USB Device Driver
  • From: Vlad Ungureanu <vvu@xxxxxxx>
• RE: why a static function is in kernel symbol table
  • From: Ji <lijimlee@xxxxxxxxx>
• Unable to access mounted sd card partition on resume from hibernate
  • From: AYAN KUMAR HALDER <ayankumarh@xxxxxxxxx>
• Disabling a BH : spin_lock_bh or local_bh_disable.
  • From: priyaranjan <priyaranjan45678@xxxxxxxxx>
• Re: why a static function is in kernel symbol table
  • From: Valdis.Kletnieks@xxxxxx
• why a static function is in kernel symbol table
  • From: Ji Li <lijimlee@xxxxxxxxx>
• Re: SOC: Zedboard: Driver question
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: me storage <me.storage126@xxxxxxxxx>
• RE: Eudyptula Challenge Task 01
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Valdis.Kletnieks@xxxxxx
• Re: Eudyptula Challenge Task 01
  • From: Kai Bojens <kb@xxxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Eudyptula Challenge Task 01
  • From: Nada Saif <nada.saif7@xxxxxxxxx>
• Re: ?ظ?: git download
  • From: Valdis.Kletnieks@xxxxxx
• Re: SOC: Zedboard: Driver question
  • From: priyaranjan <priyaranjan45678@xxxxxxxxx>
• Re: SOC: Zedboard: Driver question
  • From: priyaranjan <priyaranjan45678@xxxxxxxxx>
• SOC: Zedboard: Driver question
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• Re: git download
  • From: Valdis.Kletnieks@xxxxxx
• 回复: git download
  • From: "jinzhao@xxxxxxxxxxxx" <jinzhao@xxxxxxxxxxxx>
• git download
  • From: "jinzhao@xxxxxxxxxxxx" <jinzhao@xxxxxxxxxxxx>
• Re: Problem using git
  • From: Andev <debiandev@xxxxxxxxx>
• Re: git merge issues
  • From: Andreas Platschek <andi.platschek@xxxxxxxxx>
• Re: git merge issues
  • From: Vignesh Radhakrishnan <vignesh1192@xxxxxxxxx>
• Re: git merge issues
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• git merge issues
  • From: Raghavendra <arrao@xxxxxxx>
• Re: Problem using git
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Problem using git
  • From: Ali Aminian <aminian.opensource@xxxxxxxxx>
• Re: EudyptulaChallenge in github??
  • From: karthik <karthik.188@xxxxxxxxx>
• RE: Putting a thread to sleep using schedule() is foolproof?
  • From: Jeff Haran <Jeff.Haran@xxxxxxxxxx>
• Re: Putting a thread to sleep using schedule() is foolproof?
  • From: Joshi <joshiiitr@xxxxxxxxx>
• Re: Beginner guide
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Beginner guide
  • From: Valdis.Kletnieks@xxxxxx
• Re: Putting a thread to sleep using schedule() is foolproof?
  • From: Valdis.Kletnieks@xxxxxx
• Putting a thread to sleep using schedule() is foolproof?
  • From: Joshi <joshiiitr@xxxxxxxxx>
• Re: Beginner guide
  • From: Saurabh Jain <saurabh4768jain@xxxxxxxxx>
• Re: Beginner guide
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: Beginner guide
  • From: Ben <ben@xxxxxxx>
• Re: non-static init in a basic kernel module
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Patch submission issue
  • From: Scott Lovenberg <scott.lovenberg@xxxxxxxxx>
• non-static init in a basic kernel module
  • From: Warren Turkal <wt@xxxxxxxxxxxxxxxx>
• Re: Beginner guide
  • From: sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx>
• Re: EudyptulaChallenge in github??
  • From: Laurent Navet <laurent.navet@xxxxxxxxx>
• Re: Beginner guide
  • From: Rohan Puri <rohan.puri15@xxxxxxxxx>
• Re: Beginner guide
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: Beginner guide
  • From: Asutosh Das <das.asutosh@xxxxxxxxx>
• Beginner guide
  • From: Prudhvee Narasimha Sadha <prudhvi.sada@xxxxxxxxx>
• Memory mapping issue in OMAP Linux kernel stack
  • From: Saket Sinha <saket.sinha89@xxxxxxxxx>
• EudyptulaChallenge in github??
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Re: spi_board_info and module automatic load
  • From: Varka Bhadram <varkab@xxxxxxx>
• Re: Patch submission issue
  • From: Greg KH <greg@xxxxxxxxx>