Linux Kernel Newbies

• Thread Index

• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: Ozgur Karatas <ozgurk@xxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: Peter Maydell <peter.maydell@xxxxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: Ozgur Karatas <ozgurk@xxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: Peter Maydell <peter.maydell@xxxxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: "'Greg KH'" <greg@xxxxxxxxx>
• RE: Can't understand /proc/interrupts output for GICv3 case
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: "'Greg KH'" <greg@xxxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: Ozgur Kara <ozgur@xxxxxxxxxx>
• RE: Can't understand /proc/interrupts output for GICv3 case
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• RE: Can't understand /proc/interrupts output for GICv3 case
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: Ozgur Kara <ozgur@xxxxxxxxxx>
• Re: Can't understand /proc/interrupts output for GICv3 case
  • From: Greg KH <greg@xxxxxxxxx>
• RE: Can't understand /proc/interrupts output for GICv3 case
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Can't understand /proc/interrupts output for GICv3 case
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Linux kernel environment setup in VSCode
  • From: Minh Dang <minhdang1990@xxxxxxxxx>
• Linux kernel environment setup in VSCode
  • From: Jasper Surmont <surmontjasper@xxxxxxxxx>
• RE: irq_desc not found for my interrupt number during request_irq (radix tree of irq_desc has only 64 entries..)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• irq_desc not found for my interrupt number during request_irq (radix tree of irq_desc has only 64 entries..)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• RE: How can I debug kernel module running on a virtual machine?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• How can I debug kernel module running on a virtual machine?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• RE: request_irq not working.. what else should I do?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• request_irq not working.. what else should I do?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Rescheduling Interrupt
  • From: H C <hc128168@xxxxxxxxx>
• Re: "tftp: sendto: Network is unreachable" during tftp on a virtual machine. What config should I add to kernel build?
  • From: Grant Taylor <gtaylor@xxxxxxxxxxxxxxxxxx>
• "tftp: sendto: Network is unreachable" during tftp on a virtual machine. What config should I add to kernel build?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: kernel space: finding cpu usage of individual process/thread
  • From: Greg KH <greg@xxxxxxxxx>
• Re: arm64 code looking for variable rodata_enabled when STRICT_KERNEL_RWX = n
  • From: Pavel Skripkin <paskripkin@xxxxxxxxx>
• kernel space: finding cpu usage of individual process/thread
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• RE: arm64 code looking for variable rodata_enabled when STRICT_KERNEL_RWX = n
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• RE: arm64 code looking for variable rodata_enabled when STRICT_KERNEL_RWX = n
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: arm64 code looking for variable rodata_enabled when STRICT_KERNEL_RWX = n
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: What to do with macros with do while (0) body
  • From: Greg KH <greg@xxxxxxxxx>
• What to do with macros with do while (0) body
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• RE: Which Page table is appled when MMU is turned on in boot process of ARM64
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Which Page table is appled when MMU is turned on in boot process of ARM64
  • From: JeongHwan Kim <frog007.kernel.kr@xxxxxxxxx>
• arm64 code looking for variable rodata_enabled when STRICT_KERNEL_RWX = n
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• RE: Which Page table is appled when MMU is turned on in boot process of ARM64
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Which Page table is appled when MMU is turned on in boot process of ARM64
  • From: JeongHwan Kim <frog007.kernel.kr@xxxxxxxxx>
• Re: ioctl number change / backwards compatibility doubt
  • From: Greg KH <greg@xxxxxxxxx>
• RE: arm64 cache policy setting
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• [PATCH] dogs -
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• arm64 cache policy setting
  • From: JeongHwan Kim <frog007.kernel.kr@xxxxxxxxx>
• S25HS512T SPI Flash support in Linux Kernel 4.9.X
  • From: Mithran B <mithranb22@xxxxxxxxx>
• How to understand sched_period in the cfs schedule class?
  • From: Song Zhi <hizhisong@xxxxxxxxxxx>
• Re: "Disappearing" file in Documentation/ABI/testing
  • From: Ozgur Kara <ozgur@xxxxxxxxxx>
• Re: "Disappearing" file in Documentation/ABI/testing
  • From: Ozgur Kara <ozgur@xxxxxxxxxx>
• Re: "Disappearing" file in Documentation/ABI/testing
  • From: Greg KH <greg@xxxxxxxxx>
• "Disappearing" file in Documentation/ABI/testing
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: ioctl number change / backwards compatibility doubt
  • From: Rogério Valentim Feitoza da Silva <rogerio.silva3920@xxxxxxxxx>
• Re: ioctl number change / backwards compatibility doubt
  • From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@xxxxxxxxx>
• Re: Does Linux (Torvald's tree) infringe GPLv2 and contain proprietary binary blobs?
  • From: Robert Joslyn <robert.joslyn@xxxxxxxxxxxxxxxx>
• Re: A blog for kernel development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Does Linux (Torvald's tree) infringe GPLv2 and contain proprietary binary blobs?
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Does Linux (Torvald's tree) infringe GPLv2 and contain proprietary binary blobs?
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Does Linux (Torvald's tree) infringe GPLv2 and contain proprietary binary blobs?
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: A blog for kernel development
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: A blog for kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: A blog for kernel development
  • From: John A <john@xxxxxxxxxxxxx>
• Re: A blog for kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: A blog for kernel development
  • From: Torin Carey <torin@xxxxxxxxx>
• Re: A blog for kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: A blog for kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: A blog for kernel development
  • From: Ozgur Kara <ozgur@xxxxxxxxxx>
• Re: A blog for kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: *** Compiler is too old
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: *** Compiler is too old
  • From: jim.cromie@xxxxxxxxx
• Re: USB CDC performance test
  • From: Mithran B <mithranb22@xxxxxxxxx>
• Re: *** Compiler is too old
  • From: Rogério Valentim Feitoza da Silva <rogerio.silva3920@xxxxxxxxx>
• Re: USB CDC performance test
  • From: Greg KH <greg@xxxxxxxxx>
• Re: USB CDC performance test
  • From: Mithran B <mithranb22@xxxxxxxxx>
• Re: *** Compiler is too old
  • From: jim.cromie@xxxxxxxxx
• Re: A blog for kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: A blog for kernel development
  • From: Thomas Piekarski <t.piekarski@xxxxxxxxxxxxxx>
• Re: Which vger list is for linux-firmware?
  • From: Ozgur Kara <ozgur@xxxxxxxxxx>
• Which vger list is for linux-firmware?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• A blog for kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: USB CDC performance test
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: USB CDC performance test
  • From: Greg KH <greg@xxxxxxxxx>
• Re: USB CDC performance test
  • From: Mithran B <mithranb22@xxxxxxxxx>
• Re: USB CDC performance test
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: Torin Carey <torin@xxxxxxxxx>
• USB CDC performance test
  • From: Mithran B <mithranb22@xxxxxxxxx>
• Does fixmap pages for fdt require 4MB memory?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Questions about data protection in the kernel
  • From: Kai Meyer <kai.meyer@xxxxxxxxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: Rogério Valentim Feitoza da Silva <rogerio.silva3920@xxxxxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Fwd: Exporting cpu instruction set to kernel .config file
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: How to compile source code of new kernel specifically for my pc hardware with uefi secure boot.
  • From: Guddla Rupesh <rupeshforu3@xxxxxxxxx>
• Re: Event Tracing in the Linux kernel
  • From: Donald Hunter <donald@xxxxxxxxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: Guddla Rupesh <rupeshforu3@xxxxxxxxx>
• RE: weird printk operation early at start_kernel..
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: How to compile source code of new kernel specifically for my pc hardware with uefi secure boot.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Exporting cpu instruction set to kernel .config file
  • From: Torin Carey <torin@xxxxxxxxx>
• Exporting cpu instruction set to kernel .config file
  • From: Guddla Rupesh <rupeshforu3@xxxxxxxxx>
• Re: How to compile source code of new kernel specifically for my pc hardware with uefi secure boot.
  • From: Guddla Rupesh <rupeshforu3@xxxxxxxxx>
• Re: Event Tracing in the Linux kernel
  • From: David Kahurani <k.kahurani@xxxxxxxxx>
• Re: Event Tracing in the Linux kernel
  • From: David Kahurani <k.kahurani@xxxxxxxxx>
• Re: Event Tracing in the Linux kernel
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• Event Tracing in the Linux kernel
  • From: David Kahurani <k.kahurani@xxxxxxxxx>
• Re: Safe registration of procfs entries in LKM
  • From: Torin Carey <torin@xxxxxxxxx>
• Re: How to compile source code of new kernel specifically for my pc hardware with uefi secure boot.
  • From: Guddla Rupesh <rupeshforu3@xxxxxxxxx>
• Re: How to compile source code of new kernel specifically for my pc hardware with uefi secure boot.
  • From: Greg KH <greg@xxxxxxxxx>
• How to compile source code of new kernel specifically for my pc hardware with uefi secure boot.
  • From: Guddla Rupesh <rupeshforu3@xxxxxxxxx>
• macro arg reuse warnings, howto fix ?
  • From: jim.cromie@xxxxxxxxx
• Re: How do I start contributing to the Linux kernel?
  • From: Ozgur Kara <ozgur@xxxxxxxxxx>
• Re: How do I start contributing to the Linux kernel?
  • From: Sebastian Fricke <sebastian.fricke@xxxxxxxxxx>
• Re: How do I start contributing to the Linux kernel?
  • From: Ozgur Kara <ozgur@xxxxxxxxxx>
• Re: How do I start contributing to the Linux kernel?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Safe registration of procfs entries in LKM
  • From: Torin Carey <torin@xxxxxxxxx>
• Re: make menuconfig and make j$(nproc) throwing errors
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• Re: make menuconfig and make j$(nproc) throwing errors
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: make menuconfig and make j$(nproc) throwing errors
  • From: Greg KH <greg@xxxxxxxxx>
• Re: make menuconfig and make j$(nproc) throwing errors
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: make menuconfig and make j$(nproc) throwing errors
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How do I start contributing to the Linux kernel?
  • From: Sebastian Fricke <sebastian.fricke.linux@xxxxxxxxx>
• make menuconfig and make j$(nproc) throwing errors
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• How do I start contributing to the Linux kernel?
  • From: Rogério Valentim Feitoza da Silva <rogerio.silva3920@xxxxxxxxx>
• Re: Are there any requirements to sign up for Kernel Newbies?
  • From: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx>
• Are there any requirements to sign up for Kernel Newbies?
  • From: Rogério Valentim Feitoza da Silva <rogerio.silva3920@xxxxxxxxx>
• Re: *** Compiler is too old
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: *** Compiler is too old
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: *** Compiler is too old
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: *** Compiler is too old
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: *** Compiler is too old
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• *** Compiler is too old
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Why doesn't the GCC give any warning to these unused variables in the Linux kernel?
  • From: Greg KH <greg@xxxxxxxxx>
• Why doesn't the GCC give any warning to these unused variables in the Linux kernel?
  • From: Song Zhi <hizhisong@xxxxxxxxxxx>
• About RISC-V syscalls and the __ARCH_WANT_TIME32_SYSCALLS macro
  • From: Yimin Gu <ustcymgu@xxxxxxxxx>
• weird printk operation early at start_kernel..
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Need good starting point
  • From: Ankit Pandey <itsankitkp@xxxxxxxxx>
• Re: Need good starting point
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Need good starting point
  • From: Ankit Pandey <itsankitkp@xxxxxxxxx>
• Re: Need good starting point
  • From: Rohan Puri <rohan.puri15@xxxxxxxxx>
• Need good starting point
  • From: Ankit Pandey <itsankitkp@xxxxxxxxx>
• Re: Fwd: Need guidance regarding fixing styleguide error in rtl871x_pwrctrl.h
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Fwd: Need guidance regarding fixing styleguide error in rtl871x_pwrctrl.h
  • From: Ankit Pandey <itsankitkp@xxxxxxxxx>
• Re: Fwd: Need guidance regarding fixing styleguide error in rtl871x_pwrctrl.h
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Need guidance regarding fixing styleguide error in rtl871x_pwrctrl.h
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Fwd: Need guidance regarding fixing styleguide error in rtl871x_pwrctrl.h
  • From: Ankit Pandey <itsankitkp@xxxxxxxxx>
• Re: Kernel freezes instead of panicking
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Can't find vprintk_safe in System.map
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• vmcore-dmesg : Missing the log_buf symbol
  • From: David Kahurani <k.kahurani@xxxxxxxxx>
• Re: Kernel freezes instead of panicking
  • From: David Kahurani <k.kahurani@xxxxxxxxx>
• Re: Kernel freezes instead of panicking
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• Re: Kernel freezes instead of panicking
  • From: David Kahurani <k.kahurani@xxxxxxxxx>
• Kernel freezes instead of panicking
  • From: David Kahurani <k.kahurani@xxxxxxxxx>
• Re: How to debug stuck read?
  • From: Dāvis Mosāns <davispuh@xxxxxxxxx>
• Re: How to debug stuck read?
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: How to debug stuck read?
  • From: Dāvis Mosāns <davispuh@xxxxxxxxx>
• Re: How to debug stuck read?
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: How to debug stuck read?
  • From: Dāvis Mosāns <davispuh@xxxxxxxxx>
• Re: How to debug stuck read?
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: How to debug stuck read?
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• RE: RFQ of FPGA PCB with assembly
  • From: "Andy. Yu" <bobojijixiao@xxxxxxx>
• Re: How to debug stuck read?
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: How to debug stuck read?
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Trying to understand oom-killer (output)
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Linux driver of vt6656 from staging area causes system to freeze.
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Trying to understand oom-killer (output)
  • From: Sasa Vilic <sasavilic@xxxxxxxxx>
• Re: Linux driver of vt6656 from staging area causes system to freeze.
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Linux driver of vt6656 from staging area causes system to freeze.
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Re: How to debug stuck read?
  • From: Dāvis Mosāns <davispuh@xxxxxxxxx>
• How to debug stuck read?
  • From: Dāvis Mosāns <davispuh@xxxxxxxxx>
• Core dump does not contain the section ".reg"
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: First Time Contributor: Looking for Good Beginner issues
  • From: "Fabio M. De Francesco" <fmdefrancesco@xxxxxxxxx>
• First Time Contributor: Looking for Good Beginner issues
  • From: Dhruva gole <goledhruva@xxxxxxxxx>
• EISA always probes
  • From: Bram Stolk <b.stolk@xxxxxxxxx>
• Re: ioctl number change / backwards compatibility doubt
  • From: Greg KH <greg@xxxxxxxxx>
• Re: ioctl number change / backwards compatibility doubt
  • From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@xxxxxxxxx>
• RE: adding GCC optimze O0 to early_fixmap_init causes compiler error (BUILD_BUG failed)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: adding GCC optimze O0 to early_fixmap_init causes compiler error (BUILD_BUG failed)
  • From: jim.cromie@xxxxxxxxx
• RE: how to fix section mismatch warning after inserting #pragma GCC optimize ?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• RE: adding GCC optimze O0 to early_fixmap_init causes compiler error (BUILD_BUG failed)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• adding GCC optimze O0 to early_fixmap_init causes compiler error (BUILD_BUG failed)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: how to fix section mismatch warning after inserting #pragma GCC optimize ?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: ioctl number change / backwards compatibility doubt
  • From: Greg KH <greg@xxxxxxxxx>
• how to fix section mismatch warning after inserting #pragma GCC optimize ?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: ioctl number change / backwards compatibility doubt
  • From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@xxxxxxxxx>
• Re: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)
  • From: jim.cromie@xxxxxxxxx
• Re: How to Convert Legacy Kernel Modules for modern Kernels
  • From: Tianrui Wei <tianrui@xxxxxxxxxxxxxx>
• Re: How to Convert Legacy Kernel Modules for modern Kernels
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to Convert Legacy Kernel Modules for modern Kernels
  • From: Tianrui Wei <tianrui@xxxxxxxxxxxxxx>
• Re: How to Convert Legacy Kernel Modules for modern Kernels
  • From: Greg KH <greg@xxxxxxxxx>
• How to Convert Legacy Kernel Modules for modern Kernels
  • From: Tianrui Wei <tianrui@xxxxxxxxxxxxxx>
• RE: error: impossible constraint in 'asm' when compiling kernel code with -O0 option
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• About the kernel configuration(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE.)
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: ioctl number change / backwards compatibility doubt
  • From: Greg KH <greg@xxxxxxxxx>
• ioctl number change / backwards compatibility doubt
  • From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@xxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Pavel Skripkin <paskripkin@xxxxxxxxx>
• RE: How to disable address randomization ?
  • From: admin LI <admin@xxxxxxxxxxxxx>
• Re: How to disable address randomization ?
  • From: admin LI <admin@xxxxxxxxxxxxx>
• Re: How to disable address randomization ?
  • From: admin LI <admin@xxxxxxxxxxxxx>
• RE: How to disable address randomization ?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: How to disable address randomization ?
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: How to disable address randomization ?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to disable address randomization ?
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• How to disable address randomization ?
  • From: admin LI <admin@xxxxxxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Greg KH <greg@xxxxxxxxx>
• Does regmap-i2c not automatically switch to I2C mux?
  • From: www <ouyangxuan10@xxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Re: Where to find the information how to write a state of the art USB driver?
  • From: Greg KH <greg@xxxxxxxxx>
• Where to find the information how to write a state of the art USB driver?
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Re: x86, nmi: IOCK error
  • From: "Maciej W. Rozycki" <macro@xxxxxxxxxxx>
• Re: Documentation confusion on ICMP Rate Mask/Rate Limiting
  • From: Daryll Swer <daryllswer15@xxxxxxxxx>
• Re: Customize path to kernel deb
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Documentation confusion on ICMP Rate Mask/Rate Limiting
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Customize path to kernel deb
  • From: Lafan Mining <lkfan@xxxxxxxxxxxxxx>
• Re: Contiguous Memory Allocator (CMA)
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• Re: Contiguous Memory Allocator (CMA)
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Contiguous Memory Allocator (CMA)
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• Re: Contiguous Memory Allocator (CMA)
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Documentation confusion on ICMP Rate Mask/Rate Limiting
  • From: Daryll Swer <daryllswer15@xxxxxxxxx>
• Device to test usblcd.c wanted
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Contiguous Memory Allocator (CMA)
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• [IMA-EVM] When "appraise" applied, kernel cannot start init process.
  • From: "Kim, Jeong-Hwan" <frog007.kernel.kr@xxxxxxxxx>
• Re: X86 : system call
  • From: Greg KH <greg@xxxxxxxxx>
• X86 : system call
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Time: new clocksource
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• A question about regmap bus
  • From: Clyde Huang31 <chuang31@xxxxxxxxxx>
• Re: Time: new clocksource
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: PCI: latency
  • From: Bjorn Helgaas <helgaas@xxxxxxxxxx>
• Re: Time: new clocksource
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Time: new clocksource
  • From: Daniel Lezcano <daniel.lezcano@xxxxxxxxxx>
• Re: Time: new clocksource
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Compilation errors: unresolved symbol tcp_dctcp_kfunc_ids/tcp_cubic_kfunc_ids/tcp_bbr_kfunc_ids
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• RE: latency
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: PCI: latency
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: pseudonymous or anonymous testing
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Time: new clocksource
  • From: Daniel Lezcano <daniel.lezcano@xxxxxxxxxx>
• pseudonymous or anonymous testing
  • From: Tarif H <tarifhazid@xxxxxxxxxx>
• PCI: latency
  • From: Subhashini Rao Beerisetty <subhashbeerisetty@xxxxxxxxx>
• Time: new clocksource
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: dm-verity: How to exactly use the dm-mod.create with verity-metadata append
  • From: Will Drewry <wad@xxxxxxxxxxxx>
• Re: dm-verity: How to exactly use the dm-mod.create with verity-metadata append
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• dm-verity: How to exactly use the dm-mod.create with verity-metadata append
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: x86, nmi: IOCK error
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: x86, nmi: IOCK error
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• x86, nmi: IOCK error
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Does sysrq work over USB?
  • From: Marc SCHAEFER <schaefer@xxxxxxxxxxx>
• Re: Does sysrq work over USB?
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Does sysrq work over USB?
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Does sysrq work over USB?
  • From: Marc SCHAEFER <schaefer@xxxxxxxxxxx>
• Re: When reviewers stop responding
  • From: Greg KH <greg@xxxxxxxxx>
• When reviewers stop responding
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: USB: invalid maxpacket 8
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• USB: invalid maxpacket 8
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Does sysrq work over USB?
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Does sysrq work over USB?
  • From: Marc SCHAEFER <schaefer@xxxxxxxxxxx>
• Re: Help needed in getting kernel dump in QEMU VM
  • From: Baoquan He <bhe@xxxxxxxxxx>
• Re: Help needed in getting kernel dump in QEMU VM
  • From: Baoquan He <bhe@xxxxxxxxxx>
• DMB vs DSB in ARM
  • From: Zhang Zeren <zhangzr23@xxxxxxxxx>
• Re: Help needed in getting kernel dump in QEMU VM
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Help needed in getting kernel dump in QEMU VM
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Ezequiel Garcia <ezequiel@xxxxxxxxxxxxxxxxxxxx>
• Question about "barrier()" in the SLUB's fast path
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• Re: loading a simple hypervisor(just prints Hello World) before the linux kernel
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• Re: loading a simple hypervisor(just prints Hello World) before the linux kernel
  • From: Mushahid Hussain <mushi.shar@xxxxxxxxx>
• Re: loading a simple hypervisor(just prints Hello World) before the linux kernel
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• loading a simple hypervisor(just prints Hello World) before the linux kernel
  • From: Mushahid Hussain <mushi.shar@xxxxxxxxx>
• Re: correct source tree to make contributions to Linux thermal framework
  • From: Greg KH <greg@xxxxxxxxx>
• correct source tree to make contributions to Linux thermal framework
  • From: "Balakrishnan, Anand" <anandbal@xxxxxxxxxx>
• Will two processes each holding a given spin lock be seen as ordered by a third process not holding that lock?
  • From: Zhang Zeren <zhangzr23@xxxxxxxxx>
• Re: Kernel module that shuts down the device
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Kernel module that shuts down the device
  • From: Drew Abbott <abbotta4@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Kernel module that shuts down the device
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Kernel module that shuts down the device
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Kernel module that shuts down the device
  • From: Drew Abbott <abbotta4@xxxxxxxxx>
• Re: Kernel module that shuts down the device
  • From: Greg KH <greg@xxxxxxxxx>
• Kernel module that shuts down the device
  • From: Drew Abbott <abbotta4@xxxxxxxxx>
• litmus test for multicopy atomic
  • From: Zhang Zeren <zhangzr23@xxxxxxxxx>
• Re: Loading a simple "kernel" at the address other than default on Raspberry Pi 4
  • From: Mushahid Hussain <mushi.shar@xxxxxxxxx>
• In the device tree, what does multiple cpu nodes mean inside 'cpus' node without the wrapping 'cpu-map' node?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Loading a simple "kernel" at the address other than default on Raspberry Pi 4
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Loading a simple "kernel" at the address other than default on Raspberry Pi 4
  • From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@xxxxxxxxx>
• Loading a simple "kernel" at the address other than default on Raspberry Pi 4
  • From: Mushahid Hussain <mushi.shar@xxxxxxxxx>
• How can I use id and schema page of a yaml file in the devicetree bindings document?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Ezequiel Garcia <ezequiel@xxxxxxxxxxxxxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• RE: DTC compile error (simple-bus unit address format error for #address-cells = <2> case)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• RE: What does LOADADDR=0x20008000 mean in linux kernel make command? and what is kernel load address?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• DTC compile error (simple-bus unit address format error for #address-cells = <2> case)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Will two READ_ONCE()s in a row execute in order
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Will two READ_ONCE()s in a row execute in order
  • From: Zhang Zeren <zhangzr23@xxxxxxxxx>
• Re: Will two READ_ONCE()s in a row execute in order
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Will two READ_ONCE()s in a row execute in order
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Will two READ_ONCE()s in a row execute in order
  • From: Zhang Zeren <zhangzr23@xxxxxxxxx>
• how is booting possible using kernel image in disk?..
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• RE: is there a method to minize kernel size using menuconfig and minial driver?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: How to mmap any address space using huge pages?
  • From: Adam Turowski <adam.s.turowski@xxxxxxxxx>
• RE: How to mmap any address space using huge pages?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• What does LOADADDR=0x20008000 mean in linux kernel make command? and what is kernel load address?
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: jim.cromie@xxxxxxxxx
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: Pavel Skripkin <paskripkin@xxxxxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Any tracing mechanism can track the executed instructions of a user process in the kernel?
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• How to mmap any address space using huge pages?
  • From: Adam Turowski <adam.s.turowski@xxxxxxxxx>
• RE: kernel doesn't start booting after chaning to minimum config (on qemu arm64 machine)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: kernel doesn't start booting after chaning to minimum config (on qemu arm64 machine)
  • From: Greg KH <greg@xxxxxxxxx>
• kernel doesn't start booting after chaning to minimum config (on qemu arm64 machine)
  • From: "Chan Kim" <ckim@xxxxxxxxxx>
• Re: is there a method to minize kernel size using menuconfig and minial driver?
  • From: Laurent Navet <laurent.navet@xxxxxxxxx>
• is there a method to minize kernel size using menuconfig and minial driver?
  • From: <ckim@xxxxxxxxxx>
• career advice - which subsystem should I focus on?
  • From: Sohaib Mhmd <xunilams@xxxxxxxxx>
• Make ksm code hugepage aware
  • From: Pedro Gomes <pedrodemargomes@xxxxxxxxx>
• Re: error: impossible constraint in 'asm' when compiling kernel code with -O0 option
  • From: jim.cromie@xxxxxxxxx
• Re: error: impossible constraint in 'asm' when compiling kernel code with -O0 option
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• error: impossible constraint in 'asm' when compiling kernel code with -O0 option
  • From: <ckim@xxxxxxxxxx>
• Re: advice on checkpatch error
  • From: jim.cromie@xxxxxxxxx
• advice on checkpatch error
  • From: jim.cromie@xxxxxxxxx
• Re: ALSA kernel projects - for academic purposes
  • From: Ricard Wanderlof <ricardw@xxxxxxxx>
• Re: Can register addresses conversion go through iommu too? probably not..
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• RE: Can register addresses conversion go through iommu too? probably not..
  • From: <ckim@xxxxxxxxxx>
• Re: Can register addresses conversion go through iommu too? probably not..
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Can register addresses conversion go through iommu too? probably not..
  • From: <ckim@xxxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: Geraldo Nascimento <geraldogabriel@xxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• RE: does dma_alloc_coherent setup iommu page table?
  • From: <ckim@xxxxxxxxxx>
• does dma_alloc_coherent setup iommu page table?
  • From: <ckim@xxxxxxxxxx>
• Re: List of all available kernel modules per version
  • From: jim.cromie@xxxxxxxxx
• Re: how to avoid CPU watchdog error during debug
  • From: jim.cromie@xxxxxxxxx
• Re: Device doesnt show up on Ble Scanner - gatt-service example in tools folder as per Documentation(doc)
  • From: jim.cromie@xxxxxxxxx
• Re: where can I find the explanations for pin-ctrl or #clock-cells in the dts file? (device tree)
  • From: jim.cromie@xxxxxxxxx
• Re: Accessing a pdev or its members
  • From: Greg KH <greg@xxxxxxxxx>
• Re: List of all available kernel modules per version
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: List of all available kernel modules per version
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Accessing a pdev or its members
  • From: Drew Abbott <abbotta4@xxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: Geraldo Nascimento <geraldogabriel@xxxxxxxxx>
• Re: List of all available kernel modules per version
  • From: jim.cromie@xxxxxxxxx
• Re: ALSA kernel projects - for academic purposes
  • From: jim.cromie@xxxxxxxxx
• Re: ALSA kernel projects - for academic purposes
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: jim.cromie@xxxxxxxxx
• Re: ALSA kernel projects - for academic purposes
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: ALSA kernel projects - for academic purposes
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• ALSA kernel projects - for academic purposes
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: List of all available kernel modules per version
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: List of all available kernel modules per version
  • From: Greg KH <greg@xxxxxxxxx>
• Re: List of all available kernel modules per version
  • From: Leon Gross <leon.gross@xxxxxx>
• Re: List of all available kernel modules per version
  • From: Greg KH <greg@xxxxxxxxx>
• Re: List of all available kernel modules per version
  • From: Leon Gross <leon.gross@xxxxxx>
• Re: List of all available kernel modules per version
  • From: Greg KH <greg@xxxxxxxxx>
• List of all available kernel modules per version
  • From: Leon Gross <leon.gross@xxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: efivars
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: efivars
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: efivars
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: efivars
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: efivars
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: efivars
  • From: Greg KH <greg@xxxxxxxxx>
• efivars
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: How to print __u128_t in kernel?
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: How to print __u128_t in kernel?
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Fwd: Commit messages in a series of patches
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• How to print __u128_t in kernel?
  • From: Dongliang Mu <mudongliangabcd@xxxxxxxxx>
• Re: [Clarification] writes to kernel addresses that came from userspace
  • From: Len Baker <len.baker@xxxxxxx>
• Re: Commit messages in a series of patches
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• where can I find the explanations for pin-ctrl or #clock-cells in the dts file? (device tree)
  • From: <ckim@xxxxxxxxxx>
• Mainlining MSM8960 Device - Initramfs Issue
  • From: logicalerzor <logicalerzor@xxxxxxxxxxxxxx>
• Commit messages in a series of patches
  • From: FMDF <fmdefrancesco@xxxxxxxxx>
• Re: [Clarification] writes to kernel addresses that came from userspace
  • From: Random Guy <random.guy.from.russia@xxxxxxxxx>
• Re: thrashing on format %u vs size_t arg
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: thrashing on format %u vs size_t arg
  • From: jim.cromie@xxxxxxxxx
• Re: Vmalloc.h implicit functions
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Vmalloc.h implicit functions
  • From: Omar Mustafa <omarmustafa1991@xxxxxxxxx>
• Re: thrashing on format %u vs size_t arg
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: thrashing on format %u vs size_t arg
  • From: jim.cromie@xxxxxxxxx
• Re: thrashing on format %u vs size_t arg
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• thrashing on format %u vs size_t arg
  • From: jim.cromie@xxxxxxxxx
• Re: [Clarification] writes to kernel addresses that came from userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [Clarification] writes to kernel addresses that came from userspace
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: [Clarification] writes to kernel addresses that came from userspace
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [Clarification] writes to kernel addresses that came from userspace
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• [Clarification] writes to kernel addresses that came from userspace
  • From: Len Baker <len.baker@xxxxxxx>
• Re: Understanding merge window and next-tree
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Understanding merge window and next-tree
  • From: Greg KH <greg@xxxxxxxxx>
• Re: ASoC/ALSA Out of Memory Issue
  • From: Alex Roberts <arob109@xxxxxxxxx>
• Understanding merge window and next-tree
  • From: Lafan Mining <lkfan@xxxxxxxxxxxxxx>
• Re: Kernel upstream compile error at drivers/staging/media
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• When to use torvalds/linux.git and next/linux-next.git
  • From: Lafan Mining <lkfan@xxxxxxxxxxxxxx>
• Re: Kernel upstream compile error at drivers/staging/media
  • From: Lafan Mining <lkfan@xxxxxxxxxxxxxx>
• Re: Vmalloc.h implicit functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Kernel upstream compile error at drivers/staging/media
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: Kernel upstream compile error at drivers/staging/media
  • From: Lafan Mining <lkfan@xxxxxxxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Kernel upstream compile error at drivers/staging/media
  • From: Lafan Mining <lkfan@xxxxxxxxxxxxxx>
• Re: Kernel upstream compile error at drivers/staging/media
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Vmalloc.h implicit functions
  • From: Omar Mustafa <omarmustafa1991@xxxxxxxxx>
• Re: Kernel upstream compile error at drivers/staging/media
  • From: Lafan Mining <lkfan@xxxxxxxxxxxxxx>
• Re: Kernel upstream compile error at drivers/staging/media
  • From: Greg KH <greg@xxxxxxxxx>
• Kernel upstream compile error at drivers/staging/media
  • From: Lafan Mining <lkfan@xxxxxxxxxxxxxx>
• Re: Vmalloc.h implicit functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Vmalloc.h implicit functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Vmalloc.h implicit functions
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Vmalloc.h implicit functions
  • From: Omar Mustafa <omarmustafa1991@xxxxxxxxx>
• Re: Vmalloc.h implicit functions
  • From: Greg KH <greg@xxxxxxxxx>
• Vmalloc.h implicit functions
  • From: Omar Mustafa <omarmustafa1991@xxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Kernel bug tracker
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re[2]: Kernel bug tracker
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Re: Patch Review Process?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Kernel bug tracker
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: Kernel bug tracker
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: Kernel bug tracker
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re[2]: Kernel bug tracker
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Re[6]: Kernel bug tracker
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Patch Review Process?
  • From: Andrew D Adamson <andrewdadamson@xxxxxxxxx>
• Re: How to debug the very first part of kernel
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• How to debug the very first part of kernel
  • From: 候 磊 <ameansone@xxxxxxxxxxx>
• Re: Kernel bug tracker
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: Kernel bug tracker
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Kernel bug tracker
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re[4]: Kernel bug tracker
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Re: The authorship of each patch in a series
  • From: "Fabio M. De Francesco" <fmdefrancesco@xxxxxxxxx>
• Re: The authorship of each patch in a series
  • From: Greg KH <greg@xxxxxxxxx>
• The authorship of each patch in a series
  • From: "Fabio M. De Francesco" <fmdefrancesco@xxxxxxxxx>
• Re: how do you find the subsystem of a file?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: MODULE_SUPPORTED_DEVICE macro existed in the Kernel 5.9.16, but got removed
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Device doesnt show up on Ble Scanner - gatt-service example in tools folder as per Documentation(doc)
  • From: Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Device doesnt show up on Ble Scanner - gatt-service example in tools folder as per Documentation(doc)
  • From: Raul Piper <raulpblooper@xxxxxxxxx>
• Re: Re[2]: Kernel bug tracker
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Device doesnt show up on Ble Scanner - gatt-service example in tools folder as per Documentation(doc)
  • From: Raul Piper <raulpblooper@xxxxxxxxx>
• Re: how to properly use BUILD_BUG_ON_MSG ?
  • From: jim.cromie@xxxxxxxxx
• how to properly use BUILD_BUG_ON_MSG ?
  • From: jim.cromie@xxxxxxxxx
• how do you find the subsystem of a file?
  • From: daniel watson <ozzloy@xxxxxxxxxxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• MODULE_SUPPORTED_DEVICE macro existed in the Kernel 5.9.16, but got removed
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Get notification when a block device is mounted.
  • From: Douglas Su <d0u9.su@xxxxxxxxxxx>
• RE: how to avoid CPU watchdog error during debug
  • From: <ckim@xxxxxxxxxx>
• Device doesnt show up on Ble Scanner - gatt-service example in tools folder as per Documentation(doc)
  • From: Raul Piper <raulpblooper@xxxxxxxxx>
• USB/HID: Device with multiple interfaces
  • From: José Expósito <jose.exposito89@xxxxxxxxx>
• Re[2]: Kernel bug tracker
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Re: Update of kernelnewbies.org/FirstKernelPatch required
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: Kernel bug tracker
  • From: Anatoly Pugachev <matorola@xxxxxxxxx>
• Kernel bug tracker
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Re: Contributing to drivers/staging area
  • From: Len Baker <len.baker@xxxxxxx>
• Re: How do the kernel boot parameters work (especially "toram")?
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• How do the kernel boot parameters work (especially "toram")?
  • From: Gueven Bay <gueven.bay@xxxxxxxxxxxxxx>
• Re: how to avoid CPU watchdog error during debug
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Re: surround complex macros in ()
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Contributing to drivers/staging area
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: surround complex macros in ()
  • From: Greg KH <greg@xxxxxxxxx>
• surround complex macros in ()
  • From: daniel watson <ozzloy@xxxxxxxxxxxxxxxxx>
• how to avoid CPU watchdog error during debug
  • From: <ckim@xxxxxxxxxx>
• Re: Update of kernelnewbies.org/FirstKernelPatch required
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Which tool to use for Mesh Testing
  • From: Raul Piper <raulpblooper@xxxxxxxxx>
• Re: Update of kernelnewbies.org/FirstKernelPatch required
  • From: Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>
• Update of kernelnewbies.org/FirstKernelPatch required
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Ezequiel Garcia <ezequiel@xxxxxxxxxxxxxxxxxxxx>
• Re: how do you find the subsystem of a file?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: how do you find the subsystem of a file?
  • From: daniel watson <ozzloy@xxxxxxxxxxxxxxxxx>
• Request for login to update https://kernelnewbies.org/FirstKernelPatch
  • From: Philipp Hortmann <philipp.g.hortmann@xxxxxxxxx>
• Contributing to drivers/staging area
  • From: Len Baker <len.baker@xxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• How to implement waiting until processing is done by a device..
  • From: <ckim@xxxxxxxxxx>
• Re: Eudyptula Challenge.
  • From: Thomas Bracht Laumann Jespersen <t@xxxxxxxxxxx>
• Eudyptula Challenge.
  • From: David K <k.kahurani@xxxxxxxxx>
• Re: kmalloc - Address is not consecutive
  • From: Lloyd <lloydkl.tech@xxxxxxxxx>
• Re: kmalloc - Address is not consecutive
  • From: ckim <ckim@xxxxxxxxxx>
• Re: kmalloc - Address is not consecutive
  • From: wuzhouhui <wuzhouhui14@xxxxxxxxxxxxxxxx>
• kmalloc - Address is not consecutive
  • From: Lloyd <lloydkl.tech@xxxxxxxxx>
• [RFC PATCH v3 16/18] ledtrig-blkdev: Add function to disassociate an LED from the trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 14/18] ledtrig-blkdev: Add mode (read/write/rw) sysfs attributue
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 18/18] ledtrig-blkdev: Add config option to enable the trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 17/18] ledtrig-blkdev: Add initialization function
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 15/18] ledtrig-blkdev: Add function to associate blkdev trigger with LED
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 13/18] ledtrig-blkdev: Add blink_time & interval sysfs attributes
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 11/18] ledtrig-blkdev: Add function to associate a device with an LED
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 12/18] ledtrig-blkdev: Add sysfs attributes to [dis]associate LEDs & devices
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 10/18] block: Call LED trigger init/cleanup functions
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 09/18] ledtrig-blkdev: Add function to disassociate a device from all LEDs
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 08/18] ledtrig-blkdev: Add function to remove LED/device association
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 07/18] ledtrig-blkdev: Add function to initialize gendisk ledtrig member
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 06/18] block: Add LED trigger pointer to struct gendisk
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 05/18] ledtrig-blkdev: Periodically check devices for activity & blink LEDs
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 03/18] ledtrig-blkdev: Add file (ledtrig-blkdev.c) for block device LED trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 04/18] ledtrig-blkdev: Add misc. helper functions to blkdev LED trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 02/18] block: Add get_disk_by_name() for use by blkdev LED trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 01/18] docs: Add block device (blkdev) LED trigger documentation
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v3 00/18] Add block device LED trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: kmalloc - Crashing
  • From: Greg KH <greg@xxxxxxxxx>
• Re: kmalloc - Crashing
  • From: Lloyd <lloydkl.tech@xxxxxxxxx>
• Re: kmalloc - Crashing
  • From: Greg KH <greg@xxxxxxxxx>
• kmalloc - Crashing
  • From: Lloyd <lloydkl.tech@xxxxxxxxx>
• Re: Process after patch has been reviewed and reviewed-by: tag added
  • From: nishad kamdar <nishadkamdar@xxxxxxxxx>
• Re: Process after patch has been reviewed and reviewed-by: tag added
  • From: Greg KH <greg@xxxxxxxxx>
• Process after patch has been reviewed and reviewed-by: tag added
  • From: nishad kamdar <nishadkamdar@xxxxxxxxx>
• "Forcibly" disabling a config option (CONFIG_BLOCK)?
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• kernel / system configuration question regarding "unstable filesystems"
  • From: Colin Williams <colin.williams.orcas@xxxxxxxxx>
• Re: Problem for testing linux-next
  • From: Sidong Yang <realwakka@xxxxxxxxx>
• Re: Problem for testing linux-next
  • From: Greg KH <greg@xxxxxxxxx>
• Problem for testing linux-next
  • From: Sidong Yang <realwakka@xxxxxxxxx>
• Re: VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -2
  • From: jim.cromie@xxxxxxxxx
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: Linux Kernel build dpkg-buildpackage error
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Re: Linux Kernel build dpkg-buildpackage error
  • From: Ewan Marshall <ewanm89@xxxxxxxxx>
• Linux Kernel build dpkg-buildpackage error
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• [no subject]
  • From: Adverg Ebashinskii <ebashinskii@xxxxxxx>
• Re: VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -2
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• VFS: Cannot open root device "(null)" or unknown-block(0, 0): error -2
  • From: jim.cromie@xxxxxxxxx
• Re: USB-Audio: Device or resource busy (strace log)
  • From: vishnu <vardhanraj4143@xxxxxxxxx>
• Re: USB-Audio: Device or resource busy (strace log)
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: USB-Audio: Device or resource busy (strace log)
  • From: vishnu <vardhanraj4143@xxxxxxxxx>
• Re: USB-Audio: Device or resource busy (strace log)
  • From: vishnu <vardhanraj4143@xxxxxxxxx>
• Re: [RFC PATCH v2 05/10] block: Add block device sysfs attribute to set/clear/show LED
  • From: Jackie Liu <liuyun01@xxxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Pali Rohár <pali@xxxxxxxxxx>
• Re: LDD 3rd ed. - It was: Re: read() via USB bus
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: LDD 3rd ed. - It was: Re: read() via USB bus
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: LDD 3rd ed. - It was: Re: read() via USB bus
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: A question about staging driver like pi433
  • From: Sidong Yang <realwakka@xxxxxxxxx>
• Re: USB-Audio: Device or resource busy (strace log)
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: USB-Audio: Device or resource busy (strace log)
  • From: Jaroslav Kysela <perex@xxxxxxxx>
• USB-Audio: Device or resource busy
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Marek Behún <kabel@xxxxxxxxxx>
• Re: read() via USB bus
  • From: Oliver Neukum <oneukum@xxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: sri vathsa <srivathsa729.8@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: read() via USB bus
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Marek Behún <kabel@xxxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: read() via USB bus
  • From: Oliver Neukum <oneukum@xxxxxxxx>
• Re: read() via USB bus
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: [RFC PATCH v2 01/10] docs: Add block device LED trigger documentation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Marek Behún <kabel@xxxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: A question about staging driver like pi433
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: A question about staging driver like pi433
  • From: Sidong Yang <realwakka@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Marek Behún <kabel@xxxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Marek Behún <kabel@xxxxxxxxxx>
• Re: A question about staging driver like pi433
  • From: Greg KH <greg@xxxxxxxxx>
• Re: read() via USB bus
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• A question about staging driver like pi433
  • From: Sidong Yang <realwakka@xxxxxxxxx>
• Re: [RFC PATCH v2 05/10] block: Add block device sysfs attribute to set/clear/show LED
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: read() via USB bus
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: read() via USB bus
  • From: Oliver Neukum <oneukum@xxxxxxxx>
• read() via USB bus
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• [RFC PATCH v2 10/10] block: Add config option to enable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 09/10] block: Blink device LED (if any) when request is sent to its driver
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 08/10] block: Add init function for block device LED trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 07/10] block: Add sysfs attributes to LEDs associated with blkdev trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 06/10] block: Add activate and deactivate functions for block device LED trigger
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 05/10] block: Add block device sysfs attribute to set/clear/show LED
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 04/10] block: Add functions to set & clear block device LEDs
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 03/10] block: Add block device LED trigger fields to gendisk structure
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 00/10] Add configurable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 01/10] docs: Add block device LED trigger documentation
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH v2 02/10] block: Add file (blk-ledtrig.c) for block device LED trigger implementation
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Embedded USB Debug(EUD) driver
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: Embedded USB Debug(EUD) driver
  • From: Subhashini Rao Beerisetty <subhashbeerisetty@xxxxxxxxx>
• patch idea, kick it around here ?
  • From: jim.cromie@xxxxxxxxx
• Re: macro version of __func__ ?
  • From: jim.cromie@xxxxxxxxx
• Re: macro version of __func__ ?
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: macro version of __func__ ?
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• macro version of __func__ ?
  • From: jim.cromie@xxxxxxxxx
• Re: nand flash disable ecc
  • From: Ayan Halder <ayankumarh@xxxxxxxxx>
• Re: device tree and config file
  • From: Greg KH <greg@xxxxxxxxx>
• Re: nand flash disable ecc
  • From: Ivan Riabtsov <ivriabtsov@xxxxxxxxx>
• device tree and config file
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• nand flash disable ecc
  • From: Ivan Riabtsov <ivriabtsov@xxxxxxxxx>
• about get_user_pages function
  • From: <ckim@xxxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Gabriel Moreira <gabriel.moreira@xxxxxxxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Cindy Sue Causey <butterflybytes@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Ezequiel Garcia <ezequiel@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation
  • From: Marek Behún <kabel@xxxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Ezequiel Garcia <ezequiel@xxxxxxxxxxxxxxxxxxxx>
• Re: Embedded USB Debug(EUD) driver
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Communicating with a FTDI device
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Communicating with a FTDI device
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Embedded USB Debug(EUD) driver
  • From: Subhashini Rao Beerisetty <subhashbeerisetty@xxxxxxxxx>
• RE: Multi-touch USB weird response
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [RFC PATCH 0/8] Add configurable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC PATCH 0/8] Add configurable block device LED triggers
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: [RFC PATCH 0/8] Add configurable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC PATCH 2/8] block: Add block device LED trigger list
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Multi-touch USB weird response
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Multi-touch USB weird response
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [RFC PATCH 0/8] Add configurable block device LED triggers
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [RFC PATCH 4/8] block: Add block class attributes to manage LED trigger list
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: [RFC PATCH 2/8] block: Add block device LED trigger list
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: [RFC PATCH 1/8] docs: Add block device LED trigger documentation
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• [RFC PATCH 8/8] block: Blink device LED when request is sent to low-level driver
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH 7/8] block: Add block device attributes to set & clear LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH 6/8] block: Add kernel APIs to set & clear per-block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH 5/8] block: Add block device LED trigger info to struct genhd
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH 4/8] block: Add block class attributes to manage LED trigger list
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH 2/8] block: Add block device LED trigger list
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH 3/8] block: Add kernel APIs to create & delete block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH 1/8] docs: Add block device LED trigger documentation
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [RFC PATCH 0/8] Add configurable block device LED triggers
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• PCM prepare callback
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: ASoC/ALSA Out of Memory Issue
  • From: Alex Roberts <arob109@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: ASoC/ALSA Out of Memory Issue
  • From: Takashi Iwai <tiwai@xxxxxxx>
• ASoC/ALSA Out of Memory Issue
  • From: Alex Roberts <arob109@xxxxxxxxx>
• Re: Return value for "impossible" situations
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Return value for "impossible" situations
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Return value for "impossible" situations
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: How can I convert user virtual address to kernel virtual address and then to physical address?
  • From: Raghuram Jallipalli <raghuram.jallipalli99@xxxxxxxxx>
• How can I convert user virtual address to kernel virtual address and then to physical address?
  • From: <ckim@xxxxxxxxxx>
• Re: Return value for "impossible" situations
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Return value for "impossible" situations
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Return value for "impossible" situations
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Return value for "impossible" situations
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: sri vathsa <srivathsa729.8@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Connor Kuehl <cipkuehl@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Raghuram Jallipalli <raghuram.jallipalli99@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• seeking guidance on adding MOD_PARAM_BITMAP
  • From: jim.cromie@xxxxxxxxx
• Re: My effort to learn Linux kernel development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Greg KH <greg@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Greg KH <greg@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Jules Irenge <jbi.octave@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• RE: a question about dma_set_mask function
  • From: <ckim@xxxxxxxxxx>
• a question about dma_set_mask function
  • From: <ckim@xxxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: "s.v.krishna reddy" <svkr521@xxxxxxxxx>
• Re: Interested in kernel development
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• Re: My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: Interested in kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Richard Weinberger <richard@xxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• My effort to learn Linux kernel development
  • From: Amit Kumar <free.amit.kumar@xxxxxxxxx>
• Kernel 4.14: Using dm-verity with squashfs rootfs - mounting issue
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Richard Weinberger <richard@xxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: How to comment or reply to others?
  • From: jim.cromie@xxxxxxxxx
• Re: MTD: How to get actual image size from MTD partition
  • From: Richard Weinberger <richard@xxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Richard Weinberger <richard@xxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Greg KH <greg@xxxxxxxxx>
• Re: MTD: How to get actual image size from MTD partition
  • From: Richard Weinberger <richard@xxxxxx>
• MTD: How to get actual image size from MTD partition
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Not getting serial console prints
  • From: Ramanagouda Patil <patilraman@xxxxxxxxx>
• Re: Not getting serial console prints
  • From: hemanth nandish <hemanthluvsfifa@xxxxxxxxx>
• Not getting serial console prints
  • From: Ramanagouda Patil <patilraman@xxxxxxxxx>
• Re: Intel i40e driver call centos 4.14.44 kernel crash!
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• Re: Intel i40e driver call centos 4.14.44 kernel crash!
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Intel i40e driver call centos 4.14.44 kernel crash!
  • From: "Oracle" <oraclelinux@xxxxxxxxxxx>
• Re: Kernel first task
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How to comment or reply to others?
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Hi All, I noticed soft lockup in fb_flashcursor(). What could be the problem? and how to resolve this?
  • From: "Oracle" <oraclelinux@xxxxxxxxxxx>
• RE: ioremap and page table
  • From: <ckim@xxxxxxxxxx>
• Re: KVM syscalls
  • From: Simon Connah <simon.n.connah@xxxxxxxxxxxxxx>
• Re: KVM syscalls
  • From: Greg KH <greg@xxxxxxxxx>
• KVM syscalls
  • From: Simon Connah <simon.n.connah@xxxxxxxxxxxxxx>
• Re: ioremap and page table
  • From: Deepanshu Kartikey <kartikey406@xxxxxxxxx>
• ioremap and page table
  • From: <ckim@xxxxxxxxxx>
• Re: Kernel first task
  • From: Cláudio Maia <clrrm@xxxxxxxxxxx>
• Re: Kernel first task
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Kernel first task
  • From: Anton Baltser <antonbaltser@xxxxxxxxx>
• Kernel first task
  • From: Anton Baltser <antonbaltser@xxxxxxxxx>
• Re: How to comment or reply to others?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How to comment or reply to others?
  • From: jim.cromie@xxxxxxxxx
• Re: laptop iwlwifi suddenly not working
  • From: jim.cromie@xxxxxxxxx
• Re: trigger timestamp
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: trigger timestamp
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: trigger timestamp
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: trigger timestamp
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: trigger timestamp
  • From: Takashi Iwai <tiwai@xxxxxxx>
• Re: How to comment or reply to others?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Re: How to comment or reply to others?
  • From: Abd-Alrhman Masalkhi <abd.masalkhi@xxxxxxxxx>
• Re: How to comment or reply to others?
  • From: Abd-Alrhman Masalkhi <abd.masalkhi@xxxxxxxxx>
• Re: How to comment or reply to others?
  • From: Abd-Alrhman Masalkhi <abd.masalkhi@xxxxxxxxx>
• Re: How to comment or reply to others?
  • From: jim.cromie@xxxxxxxxx
• How to better control IMA module?
  • From: Xiaolong Wang <xiaolongw@xxxxxxxxxxxx>
• How to comment or reply to others?
  • From: abdalrhman masalkhi <abd.masalkhi@xxxxxxxxx>
• Re: Seeking advice on "monkey patching" a driver
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: laptop iwlwifi suddenly not working
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Re: laptop iwlwifi suddenly not working
  • From: jim.cromie@xxxxxxxxx
• Re: Seeking advice on "monkey patching" a driver
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Seeking advice on "monkey patching" a driver
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Seeking advice on "monkey patching" a driver
  • From: Greg KH <greg@xxxxxxxxx>
• Re: laptop iwlwifi suddenly not working
  • From: Connor Kuehl <cipkuehl@xxxxxxxxx>
• Re: laptop iwlwifi suddenly not working
  • From: jim.cromie@xxxxxxxxx
• laptop iwlwifi suddenly not working
  • From: jim.cromie@xxxxxxxxx
• Re: Seeking advice on "monkey patching" a driver
  • From: jim.cromie@xxxxxxxxx
• Re: Seeking advice on "monkey patching" a driver
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Seeking advice on "monkey patching" a driver
  • From: Greg KH <greg@xxxxxxxxx>
• Seeking advice on "monkey patching" a driver
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: kernel build error during ubuntu linux kernel build
  • From: Alexander Kapshuk <alexander.kapshuk@xxxxxxxxx>
• RE: kernel build error during ubuntu linux kernel build
  • From: <ckim@xxxxxxxxxx>
• trigger timestamp
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• ssh connection problem
  • From: Er Krishna <erkrishna@xxxxxxxxx>
• Re: advice on a bisect
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• advice on a bisect
  • From: jim.cromie@xxxxxxxxx
• Re: Query: UBIFS: How to detect empty volumes
  • From: Steve deRosier <derosier@xxxxxxxxx>
• Re: Kernel Compile Issue
  • From: Thomas Bracht Laumann Jespersen <t@xxxxxxxxxxx>
• Re: kernel build error during ubuntu linux kernel build
  • From: Alexander Kapshuk <alexander.kapshuk@xxxxxxxxx>
• RE: kernel build error during ubuntu linux kernel build
  • From: <ckim@xxxxxxxxxx>
• kernel build error during ubuntu linux kernel build
  • From: <ckim@xxxxxxxxxx>
• Re: Kernel Compile Issue
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Query: UBIFS: How to detect empty volumes
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Query: UBIFS: How to detect empty volumes
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: Kernel Compile Issue
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Kernel Compile Issue
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Wikibook Linux kernel
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• Adding a custom layer 3 protocol driver
  • From: Cedric Velandres <cedric.velandres@xxxxxxxxxxxxxx>
• Re: Kernel Compile Issue
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Kernel Compile Issue
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Kernel Compile Issue
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Kernel Compile Issue
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Kernel Compile Issue
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Kernel Compile Issue
  • From: Thomas Bracht Laumann Jespersen <t@xxxxxxxxxxx>
• Re: Kernel Compile Issue
  • From: Cindy Sue Causey <butterflybytes@xxxxxxxxx>
• Re: Query: UBIFS: How to detect empty volumes
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Query: UBIFS: How to detect empty volumes
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Kernel Compile Issue
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: Kernel Compile Issue
  • From: Thomas Bracht Laumann Jespersen <t@xxxxxxxxxxx>
• Kernel Compile Issue
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: why does an in-tree loadable module taint the kernel
  • From: jim.cromie@xxxxxxxxx
• Re: why does an in-tree loadable module taint the kernel
  • From: jim.cromie@xxxxxxxxx
• Re: why does an in-tree loadable module taint the kernel
  • From: Greg KH <greg@xxxxxxxxx>
• Re: why does an in-tree loadable module taint the kernel
  • From: jim.cromie@xxxxxxxxx
• Re: why does an in-tree loadable module taint the kernel
  • From: Greg KH <greg@xxxxxxxxx>
• Re: why does an in-tree loadable module taint the kernel
  • From: jim.cromie@xxxxxxxxx
• Re: USB sound card issues
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: USB sound card issues
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Getting backtrace of a process
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Getting backtrace of a process
  • From: hemanth nandish <hemanthluvsfifa@xxxxxxxxx>
• Re: why does an in-tree loadable module taint the kernel
  • From: Greg KH <greg@xxxxxxxxx>
• why does an in-tree loadable module taint the kernel
  • From: jim.cromie@xxxxxxxxx
• Re: USB sound card issues
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: USB sound card issues
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• CMA: why DMA_ATTR_FORCE_CONTIGUOUS is not used in v4l2 or DRM cma helper
  • From: ayaka <ayaka@xxxxxxxxxxx>
• SNDRV_PCM_IOCTL_READI_FRAMES returns EIO
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: USB sound card issues
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: USB sound card issues
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: USB sound card issues
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: USB sound card issues
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: USB sound card issues
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• USB sound card issues
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Data present in vm_area_struct
  • From: Deepanshu Kartikey <kartikey406@xxxxxxxxx>
• Re: Missing panic logs in /var/log/kern.log
  • From: manty kuma <mantykuma@xxxxxxxxx>
• how to return unneeded init-data to kernel ?
  • From: jim.cromie@xxxxxxxxx
• Re: Missing panic logs in /var/log/kern.log
  • From: Fox Chen <foxhlchen@xxxxxxxxx>
• Re: Missing panic logs in /var/log/kern.log
  • From: manty kuma <mantykuma@xxxxxxxxx>