kernelnewbies  

Messages by Thread

• • Re: kmalloc - Address is not consecutive wuzhouhui
  • Re: kmalloc - Address is not consecutive ckim
  • Re: kmalloc - Address is not consecutive Lloyd
• [RFC PATCH v3 00/18] Add block device LED trigger Ian Pilcher
  • [RFC PATCH v3 01/18] docs: Add block device (blkdev) LED trigger documentation Ian Pilcher
  • [RFC PATCH v3 02/18] block: Add get_disk_by_name() for use by blkdev LED trigger Ian Pilcher
  • [RFC PATCH v3 04/18] ledtrig-blkdev: Add misc. helper functions to blkdev LED trigger Ian Pilcher
  • [RFC PATCH v3 03/18] ledtrig-blkdev: Add file (ledtrig-blkdev.c) for block device LED trigger Ian Pilcher
  • [RFC PATCH v3 06/18] block: Add LED trigger pointer to struct gendisk Ian Pilcher
  • [RFC PATCH v3 05/18] ledtrig-blkdev: Periodically check devices for activity & blink LEDs Ian Pilcher
  • [RFC PATCH v3 07/18] ledtrig-blkdev: Add function to initialize gendisk ledtrig member Ian Pilcher
  • [RFC PATCH v3 08/18] ledtrig-blkdev: Add function to remove LED/device association Ian Pilcher
  • [RFC PATCH v3 09/18] ledtrig-blkdev: Add function to disassociate a device from all LEDs Ian Pilcher
  • [RFC PATCH v3 10/18] block: Call LED trigger init/cleanup functions Ian Pilcher
  • [RFC PATCH v3 12/18] ledtrig-blkdev: Add sysfs attributes to [dis]associate LEDs & devices Ian Pilcher
  • [RFC PATCH v3 11/18] ledtrig-blkdev: Add function to associate a device with an LED Ian Pilcher
  • [RFC PATCH v3 13/18] ledtrig-blkdev: Add blink_time & interval sysfs attributes Ian Pilcher
  • [RFC PATCH v3 15/18] ledtrig-blkdev: Add function to associate blkdev trigger with LED Ian Pilcher
  • [RFC PATCH v3 17/18] ledtrig-blkdev: Add initialization function Ian Pilcher
  • [RFC PATCH v3 18/18] ledtrig-blkdev: Add config option to enable the trigger Ian Pilcher
  • [RFC PATCH v3 14/18] ledtrig-blkdev: Add mode (read/write/rw) sysfs attributue Ian Pilcher
  • [RFC PATCH v3 16/18] ledtrig-blkdev: Add function to disassociate an LED from the trigger Ian Pilcher
• kmalloc - Crashing Lloyd
  • Re: kmalloc - Crashing Greg KH
  • Re: kmalloc - Crashing Lloyd
  • Re: kmalloc - Crashing Greg KH
• Process after patch has been reviewed and reviewed-by: tag added nishad kamdar
  • Re: Process after patch has been reviewed and reviewed-by: tag added Greg KH
  • Re: Process after patch has been reviewed and reviewed-by: tag added nishad kamdar
• "Forcibly" disabling a config option (CONFIG_BLOCK)? Ian Pilcher
• kernel / system configuration question regarding "unstable filesystems" Colin Williams
• Problem for testing linux-next Sidong Yang
  • Re: Problem for testing linux-next Greg KH
  • Re: Problem for testing linux-next Sidong Yang
• Linux Kernel build dpkg-buildpackage error Adverg Ebashinskii
  • Re: Linux Kernel build dpkg-buildpackage error Ewan Marshall
  • Re: Linux Kernel build dpkg-buildpackage error Adverg Ebashinskii
• [no subject] Adverg Ebashinskii
• VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -2 jim . cromie
  • Re: VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -2 Valdis Klētnieks
  • Re: VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -2 jim . cromie
• Re: USB-Audio: Device or resource busy (strace log) Jaroslav Kysela
  • Re: USB-Audio: Device or resource busy (strace log) vishnu
  • Re: USB-Audio: Device or resource busy (strace log) Muni Sekhar
  • Re: USB-Audio: Device or resource busy (strace log) Muni Sekhar
  • Re: USB-Audio: Device or resource busy (strace log) vishnu
  • Re: USB-Audio: Device or resource busy (strace log) vishnu
• USB-Audio: Device or resource busy Muni Sekhar
• A question about staging driver like pi433 Sidong Yang
  • Re: A question about staging driver like pi433 Greg KH
  • Re: A question about staging driver like pi433 Sidong Yang
  • Re: A question about staging driver like pi433 Greg KH
  • Re: A question about staging driver like pi433 Sidong Yang
• read() via USB bus Muni Sekhar
  • Re: read() via USB bus Oliver Neukum
  • Re: read() via USB bus Greg KH
  • Re: LDD 3rd ed. - It was: Re: read() via USB bus Valdis Klētnieks
  • Re: LDD 3rd ed. - It was: Re: read() via USB bus Greg KH
  • Re: LDD 3rd ed. - It was: Re: read() via USB bus Robert P. J. Day
  • Re: read() via USB bus Muni Sekhar
  • Re: read() via USB bus Muni Sekhar
  • Re: read() via USB bus Oliver Neukum
  • Re: read() via USB bus Muni Sekhar
  • Re: read() via USB bus Oliver Neukum
• [RFC PATCH v2 00/10] Add configurable block device LED triggers Ian Pilcher
  • [RFC PATCH v2 02/10] block: Add file (blk-ledtrig.c) for block device LED trigger implementation Ian Pilcher
  • [RFC PATCH v2 01/10] docs: Add block device LED trigger documentation Ian Pilcher
  • Re: [RFC PATCH v2 01/10] docs: Add block device LED trigger documentation Pavel Machek
  • [RFC PATCH v2 03/10] block: Add block device LED trigger fields to gendisk structure Ian Pilcher
  • [RFC PATCH v2 04/10] block: Add functions to set & clear block device LEDs Ian Pilcher
  • [RFC PATCH v2 05/10] block: Add block device sysfs attribute to set/clear/show LED Ian Pilcher
  • Re: [RFC PATCH v2 05/10] block: Add block device sysfs attribute to set/clear/show LED Jackie Liu
  • Re: [RFC PATCH v2 05/10] block: Add block device sysfs attribute to set/clear/show LED Ian Pilcher
  • [RFC PATCH v2 06/10] block: Add activate and deactivate functions for block device LED trigger Ian Pilcher
  • [RFC PATCH v2 08/10] block: Add init function for block device LED trigger Ian Pilcher
  • [RFC PATCH v2 07/10] block: Add sysfs attributes to LEDs associated with blkdev trigger Ian Pilcher
  • [RFC PATCH v2 09/10] block: Blink device LED (if any) when request is sent to its driver Ian Pilcher
  • [RFC PATCH v2 10/10] block: Add config option to enable block device LED triggers Ian Pilcher
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Marek Behún
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Ian Pilcher
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Marek Behún
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Ian Pilcher
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Greg KH
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Marek Behún
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Greg KH
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Ian Pilcher
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Greg KH
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Marek Behún
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Ian Pilcher
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Christoph Hellwig
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Marek Behún
  • Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers Pali Rohár
• patch idea, kick it around here ? jim . cromie
• macro version of __func__ ? jim . cromie
  • Re: macro version of __func__ ? Constantine Shulyupin
  • Re: macro version of __func__ ? Bernd Petrovitsch
  • Re: macro version of __func__ ? jim . cromie
• device tree and config file Anuz Pratap Singh Tomar
  • Re: device tree and config file Greg KH
• nand flash disable ecc Ivan Riabtsov
  • Re: nand flash disable ecc Ivan Riabtsov
• about get_user_pages function ckim
• Communicating with a FTDI device Jeffrey Walton
  • Re: Communicating with a FTDI device Jeffrey Walton
• Embedded USB Debug(EUD) driver Subhashini Rao Beerisetty
  • Re: Embedded USB Debug(EUD) driver Greg KH
  • Re: Embedded USB Debug(EUD) driver Subhashini Rao Beerisetty
  • Re: Embedded USB Debug(EUD) driver Randy Dunlap
• Multi-touch USB weird response Jorge Fernandez Monteagudo
  • Re: Multi-touch USB weird response Valdis Klētnieks
  • RE: Multi-touch USB weird response Jorge Fernandez Monteagudo
• [RFC PATCH 0/8] Add configurable block device LED triggers Ian Pilcher
  • [RFC PATCH 1/8] docs: Add block device LED trigger documentation Ian Pilcher
  • Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation Valdis Klētnieks
  • Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation Ian Pilcher
  • Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation Greg KH
  • Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation Greg KH
  • Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation Marek Behún
  • Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation Ian Pilcher
  • [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers Ian Pilcher
  • Re: [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers Valdis Klētnieks
  • Re: [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers Ian Pilcher
  • Re: [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers Greg KH
  • [RFC PATCH 2/8] block: Add block device LED trigger list Ian Pilcher
  • Re: [RFC PATCH 2/8] block: Add block device LED trigger list Valdis Klētnieks
  • Re: [RFC PATCH 2/8] block: Add block device LED trigger list Ian Pilcher
  • [RFC PATCH 4/8] block: Add block class attributes to manage LED trigger list Ian Pilcher
  • Re: [RFC PATCH 4/8] block: Add block class attributes to manage LED trigger list Greg KH
  • [RFC PATCH 5/8] block: Add block device LED trigger info to struct genhd Ian Pilcher
  • [RFC PATCH 6/8] block: Add kernel APIs to set & clear per-block device LED triggers Ian Pilcher
  • [RFC PATCH 7/8] block: Add block device attributes to set & clear LED triggers Ian Pilcher
  • [RFC PATCH 8/8] block: Blink device LED when request is sent to low-level driver Ian Pilcher
  • Re: [RFC PATCH 0/8] Add configurable block device LED triggers Pavel Machek
  • Re: [RFC PATCH 0/8] Add configurable block device LED triggers Ian Pilcher
  • Re: [RFC PATCH 0/8] Add configurable block device LED triggers Pavel Machek
  • Re: [RFC PATCH 0/8] Add configurable block device LED triggers Ian Pilcher
• PCM prepare callback Muni Sekhar
• ASoC/ALSA Out of Memory Issue Alex Roberts
  • Re: ASoC/ALSA Out of Memory Issue Takashi Iwai
  • Re: ASoC/ALSA Out of Memory Issue Alex Roberts
  • Re: ASoC/ALSA Out of Memory Issue Alex Roberts
• How can I convert user virtual address to kernel virtual address and then to physical address? ckim
  • Re: How can I convert user virtual address to kernel virtual address and then to physical address? Raghuram Jallipalli
• Return value for "impossible" situations Ian Pilcher
  • Re: Return value for "impossible" situations Bernd Petrovitsch
  • Re: Return value for "impossible" situations Ian Pilcher
  • Re: Return value for "impossible" situations Valdis Klētnieks
  • Re: Return value for "impossible" situations Ian Pilcher
  • Re: Return value for "impossible" situations Bernd Petrovitsch
  • Re: Return value for "impossible" situations Bernd Petrovitsch
• seeking guidance on adding MOD_PARAM_BITMAP jim . cromie
• a question about dma_set_mask function ckim
  • RE: a question about dma_set_mask function ckim
• Re: Interested in kernel development Amit Kumar
  • Re: Interested in kernel development Constantine Shulyupin
• My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development s.v.krishna reddy
  • Re: My effort to learn Linux kernel development Jules Irenge
  • Re: My effort to learn Linux kernel development Robert P. J. Day
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development Greg KH
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development Greg KH
  • Re: My effort to learn Linux kernel development Robert P. J. Day
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development Raghuram Jallipalli
  • Re: My effort to learn Linux kernel development Connor Kuehl
  • Re: My effort to learn Linux kernel development sri vathsa
  • Re: My effort to learn Linux kernel development Robert P. J. Day
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development Aruna Hewapathirane
  • Re: My effort to learn Linux kernel development Cindy Sue Causey
  • Re: My effort to learn Linux kernel development Gabriel Moreira
  • Re: My effort to learn Linux kernel development Aruna Hewapathirane
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development sri vathsa
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development Amit Kumar
  • Re: My effort to learn Linux kernel development Constantine Shulyupin
  • Re: My effort to learn Linux kernel development Robert P. J. Day
• Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Mikulas Patocka
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Mikulas Patocka
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Thomas Petazzoni
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Thomas Petazzoni
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Greg KH
  • Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue Pintu Agarwal
• MTD: How to get actual image size from MTD partition Pintu Agarwal
  • Re: MTD: How to get actual image size from MTD partition Richard Weinberger
  • Re: MTD: How to get actual image size from MTD partition Greg KH
  • Re: MTD: How to get actual image size from MTD partition Richard Weinberger

• Earlier messages
• Later messages