Linux Kernel Newbies

• Thread Index

• Re: How to choose format specifier for boolean variables in Linux kernel?
  • From: 慕冬亮 <mudongliangabcd@xxxxxxxxx>
• Re: How to choose format specifier for boolean variables in Linux kernel?
  • From: Fox Chen <foxhlchen@xxxxxxxxx>
• How to choose format specifier for boolean variables in Linux kernel?
  • From: 慕冬亮 <mudongliangabcd@xxxxxxxxx>
• Re: What Device Deriver Developers Do?
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• What Device Deriver Developers Do?
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: Adding a sched_class after the removal of ".next" regarding priority
  • From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@xxxxxxxxx>
• Adding a sched_class after the removal of ".next" regarding priority
  • From: J Mårtensson <martensson.jacob@xxxxxxxxx>
• Re: How to test device driver?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to test device driver?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How to test device driver?
  • From: jim.cromie@xxxxxxxxx
• Re: How to test device driver?
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: How to test device driver?
  • From: jim.cromie@xxxxxxxxx
• How to test device driver?
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• How to make BPF program which is attached to kprobe keep working after process exits?
  • From: Junyeong Jeong <esrse.jeong@xxxxxxxxx>
• Adding a new scheduler to the kernel
  • From: J Mårtensson <martensson.jacob@xxxxxxxxx>
• Re: Does FreeRTOS works on Linux?
  • From: Primoz Beltram <primoz.beltram@xxxxxxxxx>
• Re: Does FreeRTOS works on Linux?
  • From: loïc tourlonias <loic.tourlonias@xxxxxxxxx>
• kernel module parameter API ala drm.debug
  • From: jim.cromie@xxxxxxxxx
• Re: Does FreeRTOS works on Linux?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Does FreeRTOS works on Linux?
  • From: jim.cromie@xxxxxxxxx
• Re: Does FreeRTOS works on Linux?
  • From: loïc tourlonias <loic.tourlonias@xxxxxxxxx>
• GPIO Driver Design
  • From: Robert Joslyn <robert.joslyn@xxxxxxxxxxxxxxxx>
• Re: Does FreeRTOS works on Linux?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Does FreeRTOS works on Linux?
  • From: Raul Piper <raulpblooper@xxxxxxxxx>
• Re: Wikibook Linux kernel
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: Wikibook Linux kernel
  • From: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx>
• Re: Wikibook Linux kernel
  • From: Mike Rapoport <rppt@xxxxxxxxxxxxx>
• Re: Wikibook Linux kernel
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Wikibook Linux kernel
  • From: Constantine Shulyupin <constantine.shulyupin@xxxxxxxxx>
• Re: Does FreeRTOS works on Linux?
  • From: Raul Piper <raulpblooper@xxxxxxxxx>
• Re: Does FreeRTOS works on Linux?
  • From: loïc tourlonias <loic.tourlonias@xxxxxxxxx>
• Does FreeRTOS works on Linux?
  • From: Raul Piper <raulpblooper@xxxxxxxxx>
• Re: deleting timer that re-registers itself
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: Test if a socket accept is from external network
  • From: jim.cromie@xxxxxxxxx
• Re: deleting timer that re-registers itself
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: deleting timer that re-registers itself
  • From: Greg KH <greg@xxxxxxxxx>
• Re: deleting timer that re-registers itself
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: deleting timer that re-registers itself
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: deleting timer that re-registers itself
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: deleting timer that re-registers itself
  • From: Greg KH <greg@xxxxxxxxx>
• Re: deleting timer that re-registers itself
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• deleting timer that re-registers itself
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: high precision timers
  • From: loïc tourlonias <loic.tourlonias@xxxxxxxxx>
• Re: high precision timers
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: high precision timers
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: high precision timers
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: high precision timers
  • From: Greg KH <greg@xxxxxxxxx>
• high precision timers
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: B K Karthik <bkkarthik@xxxxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: bkkarthik <bkkarthik@xxxxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: B K Karthik <bkkarthik@xxxxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: Jaroslav Kysela <perex@xxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: bkkarthik <bkkarthik@xxxxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: Jaroslav Kysela <perex@xxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Jaroslav Kysela <perex@xxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: Jaroslav Kysela <perex@xxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: Jaroslav Kysela <perex@xxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: bkkarthik <bkkarthik@xxxxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: "Rafael J. Wysocki" <rafael@xxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: bkkarthik <bkkarthik@xxxxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: can't find device_create funtion in a driver containing cdev (habanalabs)
  • From: "'Greg KH'" <greg@xxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• RE: can't find device_create funtion in a driver containing cdev (habanalabs)
  • From: <ckim@xxxxxxxxxx>
• Problem building an out of tree modules for kernel version 5.8.0
  • From: Michael McCann <kb2ghz@xxxxxxxxx>
• Re: can't find device_create funtion in a driver containing cdev (habanalabs)
  • From: Greg KH <greg@xxxxxxxxx>
• can't find device_create funtion in a driver containing cdev (habanalabs)
  • From: <ckim@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Anupama K Patil <anupamakpatil123@xxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Anupama K Patil <anupamakpatil123@xxxxxxxxx>
• Re: [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] MAINTAINERS: mark isapnp as obsolete
  • From: Anupama K Patil <anupamakpatil123@xxxxxxxxx>
• Re: Re:Re: [kernel]:overlayfs: invalid origin (root/bmcweb_persistent_data.json, ftype=8000, origin ftype=4000)
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re:Re:Re: [kernel]:overlayfs: invalid origin (root/bmcweb_persistent_data.json, ftype=8000, origin ftype=4000)
  • From: www <ouyangxuan10@xxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: Device driver .shutdown() VS .remove()
  • From: Luca Ceresoli <luca@xxxxxxxxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: Barnabás Pőcze <pobrn@xxxxxxxxxxxxxx>
• [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: Anupama K Patil <anupamakpatil123@xxxxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• [PATCH] drivers: pnp: proc.c: Removed unnecessary varibles
  • From: Anupama K Patil <anupamakpatil123@xxxxxxxxx>
• Re: [QUERY]drivers: pnp: isapnp:proc.c: assignment inside if statement
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Willy Tarreau <w@xxxxxx>
• [QUERY]drivers: pnp: isapnp:proc.c: assignment inside if statement
  • From: anupamakpatil123 <anupamakpatil123@xxxxxxxxx>
• Re: Test if a socket accept is from external network
  • From: John Wood <john.wood@xxxxxxx>
• Re: Test if a socket accept is from external network
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Test if a socket accept is from external network
  • From: John Wood <john.wood@xxxxxxx>
• Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Unable to initialize SMTP properly. Check config and use --smtp-debug. VALUES:
  • From: Jules Irenge <jbi.octave@xxxxxxxxx>
• Re: Importing the Japanese Shift-JIS encoding to the kernel's locale
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Importing the Japanese Shift-JIS encoding to the kernel's locale
  • From: HerbalNekoTea <herbalnekotea@xxxxxxxxx>
• Re: preemptible spinlock?
  • From: Hyeonggon Yoo <42.hyeyoo@xxxxxxxxx>
• Re: Importing the Japanese Shift-JIS encoding to the kernel's locale
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Importing the Japanese Shift-JIS encoding to the kernel's locale
  • From: HerbalNekoTea <herbalnekotea@xxxxxxxxx>
• Re: TCP syn flooding protection
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• TCP syn flooding protection
  • From: JeongHwan Kim <frog007.kernel.kr@xxxxxxxxx>
• Re: preemptible spinlock?
  • From: Max Filippov <jcmvbkbc@xxxxxxxxx>
• RE: preemptible spinlock?
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• Re: Device driver .shutdown() VS .remove()
  • From: jim.cromie@xxxxxxxxx
• preemptible spinlock?
  • From: 유형곤 <42.hyeyoo@xxxxxxxxx>
• Re: USB resets
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Device driver .shutdown() VS .remove()
  • From: Luca Ceresoli <luca@xxxxxxxxxxxxxxxx>
• RE: USB resets
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Question about the linux switch_to macro parameters
  • From: 武广阔 <wuguangkuo@xxxxxxx>
• Re: Is there documentation for what each script in linux/scripts does?
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Is there documentation for what each script in linux/scripts does?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Is there documentation for what each script in linux/scripts does?
  • From: Esme Xuan Lim <esmethedev@xxxxxxxxx>
• Re: USB resets
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• RE: USB resets
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: USB resets
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• USB resets
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: HID Monitor Driver Advice
  • From: Mark Bolhuis <mark@xxxxxxxxxxx>
• Re: HID Monitor Driver Advice
  • From: Greg KH <greg@xxxxxxxxx>
• Re:Re: [kernel]:overlayfs: invalid origin (root/bmcweb_persistent_data.json, ftype=8000, origin ftype=4000)
  • From: www <ouyangxuan10@xxxxxxx>
• Re: [kernel]:overlayfs: invalid origin (root/bmcweb_persistent_data.json, ftype=8000, origin ftype=4000)
  • From: Amir Goldstein <amir73il@xxxxxxxxx>
• Re: HID Monitor Driver Advice
  • From: Mark Bolhuis <mark@xxxxxxxxxxx>
• Re: HID Monitor Driver Advice
  • From: Greg KH <greg@xxxxxxxxx>
• HID Monitor Driver Advice
  • From: mark@xxxxxxxxxxx
• Why does dump_stack need asmlinkage?
  • From: Lv Ying <lvying.system.thoughts@xxxxxxxxx>
• Re: Linux kernel BSP
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Linux kernel BSP
  • From: "Pankaj Vinodrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: Linux kernel BSP
  • From: Saket Sinha <saket.sinha89@xxxxxxxxx>
• Re: Linux kernel BSP
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Linux kernel BSP
  • From: "Pankaj Vinodrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: Linux kernel BSP
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Linux kernel BSP
  • From: "Pankaj Vinodrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: Linux kernel BSP
  • From: Greg KH <greg@xxxxxxxxx>
• Linux kernel BSP
  • From: "Pankaj Vinodrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: Andi Kleen <ak@xxxxxxxxxxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: Andi Kleen <ak@xxxxxxxxxxxxxxx>
• Controlling IOVA addresses generated by IOMMU
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How to free a page table page
  • From: Wonkyo Choe <heysid3@xxxxxxxxx>
• Re: How to free a page table page
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: How to free a page table page
  • From: linux lover <caprianking2002@xxxxxxxxx>
• How to free a page table page
  • From: Wonkyo Choe <heysid3@xxxxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: pid start time and new display field in proc pid stat [ race in task->start_boottime ,start_time]
  • From: Navin P <navinp0304@xxxxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: pid start time and new display field in proc pid stat [ race in task->start_boottime , start_time]
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Unable to boot to kernel built from stable 5.11.y
  • From: Andrew D Adamson <andrewdadamson@xxxxxxxxx>
• Re: memory order seq cst for atomics
  • From: Greg KH <greg@xxxxxxxxx>
• memory order seq cst for atomics
  • From: Navin P <navinp0304@xxxxxxxxx>
• Re: Unable to boot to kernel built from stable 5.11.y
  • From: jim.cromie@xxxxxxxxx
• Re: Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: Status of a kernel.org hosted project, mmsd?
  • From: linux lover <caprianking2002@xxxxxxxxx>
• Status of a kernel.org hosted project, mmsd?
  • From: Chris Talbot <chris@xxxxxxxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Arnd Bergmann <arnd@xxxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Arnd Bergmann <arnd@xxxxxxxxxx>
• Re: pid start time and new display field in proc pid stat [ race in task->start_boottime ,start_time]
  • From: Navin P <navinp0304@xxxxxxxxx>
• Re: Missing RUST_EXAMPLE option in linux-next
  • From: Manas <manas18244@xxxxxxxxxxx>
• Re: Missing RUST_EXAMPLE option in linux-next
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Missing RUST_EXAMPLE option in linux-next
  • From: Manas <manas18244@xxxxxxxxxxx>
• Re: platform device as parent of a miscdevice
  • From: Greg KH <greg@xxxxxxxxx>
• Re: platform device as parent of a miscdevice
  • From: Martin Kaiser <lists@xxxxxxxxx>
• Re: Notify special task kill using wait* functions
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Notify special task kill using wait* functions
  • From: John Wood <john.wood@xxxxxxx>
• Re: platform device as parent of a miscdevice
  • From: Greg KH <greg@xxxxxxxxx>
• platform device as parent of a miscdevice
  • From: Martin Kaiser <lists@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Unable to boot to kernel built from stable 5.11.y
  • From: Andrew Adamson <andrewdadamson@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Compiling kernel-3.4.xxx with gcc-9.x. Need some help.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Understanding the locking behavior of msync
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Understanding the locking behavior of msync
  • From: Maximilian Böther <maximilian.boether@xxxxxxxxxxxxxx>
• Re: pid start time and new display field in proc pid stat
  • From: Navin P <navinp0304@xxxxxxxxx>
• patchset grooming question.
  • From: jim.cromie@xxxxxxxxx
• Re: make menuconfig
  • From: jim.cromie@xxxxxxxxx
• Re: How to switch between installed kernel and developed kernel
  • From: jim.cromie@xxxxxxxxx
• Re: pid start time and new display field in proc pid stat
  • From: jim.cromie@xxxxxxxxx
• "module:find_symbol: Failed to find symbol ....." not so bad.
  • From: jim.cromie@xxxxxxxxx
• pid start time and new display field in proc pid stat
  • From: Navin P <navinp0304@xxxxxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: Gidi Gal <gidi.gal.linux@xxxxxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: Gidi Gal <gidi.gal.linux@xxxxxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: "Invalid signature" issue on dev kernel launch
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• "Invalid signature" issue on dev kernel launch
  • From: Gidi Gal <gidi.gal.linux@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Gidi Gal <gidi.gal.linux@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Mismatch between tcp_output.c and tcp_fastopen.c in net/ipv4
  • From: Navin P <navinp0304@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Gidi Gal <gidi.gal.linux@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Aruna Hewapathirane <aruna.hewapathirane@xxxxxxxxx>
• Re: kernel projects for students
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Gidi Gal <gidi.gal.linux@xxxxxxxxx>
• Re: kernel projects for students
  • From: Okash Khawaja <okash.khawaja@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• kernel projects for students
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: How to switch between installed kernel and developed kernel
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• How to switch between installed kernel and developed kernel
  • From: Gidi Gal <gidi.gal.linux@xxxxxxxxx>
• Re: picking the first patch
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• RE: question about ioport_map function
  • From: <ckim@xxxxxxxxxx>
• question about ioport_map function
  • From: <ckim@xxxxxxxxxx>
• Re: Help filing bugs from crash reports and repro files.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Help filing bugs from crash reports and repro files.
  • From: Greg KH <greg@xxxxxxxxx>
• Help filing bugs from crash reports and repro files.
  • From: Machiry Aravind Kumar <makrvcs@xxxxxxxxx>
• Device file not appearing
  • From: Gregory Anders <greg@xxxxxxxxxxxx>
• Re: picking the first patch
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: picking the first patch
  • From: Harsha Vardhan <harshavardhan3294@xxxxxxxxx>
• Re: picking the first patch
  • From: Greg KH <greg@xxxxxxxxx>
• picking the first patch
  • From: Harsha Vardhan <harshavardhan3294@xxxxxxxxx>
• make menuconfig
  • From: Martin Herdeis <martinherdeis@xxxxxx>
• Re: are 1-wire devices "discoverable"?
  • From: jim.cromie@xxxxxxxxx
• Re: /sys/devices/system/cpu/possible is immutable?
  • From: Junyeong Jeong <esrse.jeong@xxxxxxxxx>
• Re: /sys/devices/system/cpu/possible is immutable?
  • From: Greg KH <greg@xxxxxxxxx>
• /sys/devices/system/cpu/possible is immutable?
  • From: Junyeong Jeong <esrse.jeong@xxxxxxxxx>
• Re: Device file not appearing
  • From: Gregory Anders <greg@xxxxxxxxxxxx>
• Re: Device file not appearing
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Device file not appearing
  • From: Gregory Anders <greg@xxxxxxxxxxxx>
• Re: Device file not appearing
  • From: Gregory Anders <greg@xxxxxxxxxxxx>
• Re: Device file not appearing
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Device file not appearing
  • From: Gregory Anders <greg@xxxxxxxxxxxx>
• Re: Device file not appearing
  • From: Greg KH <greg@xxxxxxxxx>
• Device file not appearing
  • From: Gregory Anders <greg@xxxxxxxxxxxx>
• Re: is there an efficient module_is_builtin() test ?
  • From: jim.cromie@xxxxxxxxx
• help with linker script mods
  • From: jim.cromie@xxxxxxxxx
• Re: [PATCH 05/15] staging: rtl8723bs: remove unused code blocks conditioned by never set CONFIG_PM
  • From: Fabio Aiuto <fabioaiuto83@xxxxxxxxx>
• Re: Kernelnewbies Digest, Vol 124, Issue 4
  • From: linux lover <caprianking2002@xxxxxxxxx>
• Re: Kernelnewbies Digest, Vol 124, Issue 4
  • From: linux lover <caprianking2002@xxxxxxxxx>
• Re: Kernelnewbies Digest, Vol 124, Issue 4
  • From: linux lover <caprianking2002@xxxxxxxxx>
• Re: is there an efficient module_is_builtin() test ?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• is there an efficient module_is_builtin() test ?
  • From: jim.cromie@xxxxxxxxx
• Re: linux-kernel janitorial RFP: Mark static arrays as const
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: linux-kernel janitorial RFP: Mark static arrays as const
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: linux-kernel janitorial RFP: Mark static arrays as const
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: linux-kernel janitorial RFP: Mark static arrays as const
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: How to reverse engineer a PCI-Express driver under Linux ?
  • From: Greg KH <greg@xxxxxxxxx>
• How to reverse engineer a PCI-Express driver under Linux ?
  • From: Tomek LECOCQ <tomek.lecocq@xxxxxxxxxx>
• Re: [Cocci] linux-kernel janitorial RFP: Mark static arrays as const
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: [Cocci] linux-kernel janitorial RFP: Mark static arrays as const
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [Cocci] linux-kernel janitorial RFP: Mark static arrays as const
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• linux-kernel janitorial RFP: Mark static arrays as const
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: Fwd: Re: [GIT PULL] PCI changes for v5.12
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Fwd: Re: [GIT PULL] PCI changes for v5.12
  • From: wuzhouhui <wuzhouhui14@xxxxxxxxxxxxxxxx>
• Re: Fwd: Re: [GIT PULL] PCI changes for v5.12
  • From: Greg KH <greg@xxxxxxxxx>
• Fwd: Re: [GIT PULL] PCI changes for v5.12
  • From: wuzhouhui <wuzhouhui14@xxxxxxxxxxxxxxxx>
• Re: Aw: How to make .dtb from .dts file (how to set include path for #include .. ?)
  • From: linux lover <caprianking2002@xxxxxxxxx>
• Re: Eudyptula task 6
  • From: Sebastian Fricke <sebastian.fricke.linux@xxxxxxxxx>
• Re: Eudyptula task 6
  • From: Jules Irenge <jbi.octave@xxxxxxxxx>
• Eudyptula task 6
  • From: Jules Irenge <jbi.octave@xxxxxxxxx>
• RE: How to make .dtb from .dts file (how to set include path for #include .. ?)
  • From: <ckim@xxxxxxxxxx>
• Aw: How to make .dtb from .dts file (how to set include path for #include .. ?)
  • From: Martin Herdeis <martinherdeis@xxxxxx>
• Re: How to make .dtb from .dts file (how to set include path for #include .. ?)
  • From: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx>
• How to make .dtb from .dts file (how to set include path for #include .. ?)
  • From: <ckim@xxxxxxxxxx>
• Enable 9bit-mode in a serial device
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: Does 'make oldconfig' work across different architectures?
  • From: jim.cromie@xxxxxxxxx
• Does 'make oldconfig' work across different architectures?
  • From: <ckim@xxxxxxxxxx>
• are 1-wire devices "discoverable"?
  • From: Trevor Woerner <twoerner@xxxxxxxxx>
• Is it possible to disable NEON to cause a trap with NEON code?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Enquiry
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Enquiry
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Enquiry
  • From: Abhijit Paul <coder.abhijit90@xxxxxxxxx>
• Re: Changelog of features / drivers removed from kernel?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Changelog of features / drivers removed from kernel?
  • From: Evan T Mesterhazy <etm2131@xxxxxxxxxxxx>
• Re: Changelog of features / drivers removed from kernel?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Changelog of features / drivers removed from kernel?
  • From: Evan T Mesterhazy <etm2131@xxxxxxxxxxxx>
• Re: Changelog of features / drivers removed from kernel?
  • From: Greg KH <greg@xxxxxxxxx>
• Changelog of features / drivers removed from kernel?
  • From: Evan T Mesterhazy <etm2131@xxxxxxxxxxxx>
• Re: grab raw data from microphone and send it to the output
  • From: Ivan Riabtsov <ivriabtsov@xxxxxxxxx>
• Re: grab raw data from microphone and send it to the output
  • From: Greg KH <greg@xxxxxxxxx>
• Re: grab raw data from microphone and send it to the output
  • From: Ivan Riabtsov <ivriabtsov@xxxxxxxxx>
• Re: grab raw data from microphone and send it to the output
  • From: Pouya Abbassi <abbassi.pouya@xxxxxxxxx>
• Re: grab raw data from microphone and send it to the output
  • From: Greg KH <greg@xxxxxxxxx>
• grab raw data from microphone and send it to the output
  • From: Ivan Riabtsov <ivriabtsov@xxxxxxxxx>
• Re: Enquiry for contribute in Linux Kernel
  • From: Krishna Deshpande <krishna.desh2@xxxxxxxxx>
• Re: Enquiry for contribute in Linux Kernel
  • From: Ezra Buehler <ezra@xxxxxxxx>
• Re: Enquiry for contribute in Linux Kernel
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Enquiry for contribute in Linux Kernel
  • From: Abhijit Paul <coder.abhijit90@xxxxxxxxx>
• Re: UDP implementation and the MSG_MORE flag
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: '-D' 'KBUILD_MODSYM=main - like KBUILD_MODNAME, without the quotes ?
  • From: jim.cromie@xxxxxxxxx
• Re: '-D' 'KBUILD_MODSYM=main - like KBUILD_MODNAME, without the quotes ?
  • From: jim.cromie@xxxxxxxxx
• Re: '-D' 'KBUILD_MODSYM=main - like KBUILD_MODNAME, without the quotes ?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: '-D' 'KBUILD_MODSYM=main - like KBUILD_MODNAME, without the quotes ?
  • From: jim.cromie@xxxxxxxxx
• Re: '-D' 'KBUILD_MODSYM=main - like KBUILD_MODNAME, without the quotes ?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• '-D' 'KBUILD_MODSYM=main - like KBUILD_MODNAME, without the quotes ?
  • From: jim.cromie@xxxxxxxxx
• Re: Doubt on show() function of sysfs attribute
  • From: Mohana Datta Yelugoti <ymdatta.work@xxxxxxxxx>
• Re: Doubt on show() function of sysfs attribute
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: Doubt on show() function of sysfs attribute
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Doubt on show() function of sysfs attribute
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Doubt on show() function of sysfs attribute
  • From: Mohana Datta Yelugoti <ymdatta.work@xxxxxxxxx>
• Re: new module is not compiled
  • From: Dario Pagani <dario.pagani.146@xxxxxxxxx>
• UDP implementation and the MSG_MORE flag
  • From: Oliver Graute <oliver.graute@xxxxxxxxx>
• Re: new module is not compiled
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• new module is not compiled
  • From: Dario Pagani <dario.pagani.146@xxxxxxxxx>
• Re: /proc/cpuinfo not showing all info
  • From: Greg KH <greg@xxxxxxxxx>
• Re: /proc/cpuinfo not showing all info
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: /proc/cpuinfo not showing all info
  • From: "Pankaj Vinodrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: /proc/cpuinfo not showing all info
  • From: Greg KH <greg@xxxxxxxxx>
• Re: /proc/cpuinfo not showing all info
  • From: "Pankaj Vinodrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• device tree or ACPI table? and x0 register in arm64 kernel start
  • From: <ckim@xxxxxxxxxx>
• Re: 回复：How to join other mailing lists
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• 回复：How to join other mailing lists
  • From: ‪bigbird2444@xxxxxxx‬ <bigbird2444@xxxxxxx>
• linker script hack - can it be made to work ?
  • From: jim.cromie@xxxxxxxxx
• Re: How to join other mailing lists
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How to join other mailing lists
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: How to join other mailing lists
  • From: Alexander Kapshuk <alexander.kapshuk@xxxxxxxxx>
• How to join other mailing lists
  • From: "bigbird2444@xxxxxxx" <bigbird2444@xxxxxxx>
• Restrict DMA Buffer to 32 bit Address
  • From: Tal Lubko <tallubko@xxxxxxxxx>
• Re: /proc/cpuinfo not showing all info
  • From: Greg KH <greg@xxxxxxxxx>
• /proc/cpuinfo not showing all info
  • From: "Pankaj Vinodrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Greg KH <greg@xxxxxxxxx>
• RE: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Greg KH <greg@xxxxxxxxx>
• RE: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Greg KH <greg@xxxxxxxxx>
• RE: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Greg KH <greg@xxxxxxxxx>
• RE: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Greg KH <greg@xxxxxxxxx>
• How to replace set_fs(KERNEL_DS) for a kernel 5.10.x module driver version
  • From: Jorge Fernandez Monteagudo <jorgefm@xxxxxxxxx>
• Re: Tutorial for "drivers/mmc/*"?
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: Setting group/other write flags not honoured in open
  • From: Nicky Chorley <ndchorley@xxxxxxxxx>
• Tutorial for "drivers/mmc/*"?
  • From: "Gabriel L. Somlo" <gsomlo@xxxxxxxxx>
• Re: Linux has timerfd, signalfd and eventfd. Is it time for a "unionfd"?
  • From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
• How should I understand the 'less-compatible' names in the compatible list in device tree?
  • From: <ckim@xxxxxxxxxx>
• Re: Linux has timerfd, signalfd and eventfd. Is it time for a "unionfd"?
  • From: Joe Doe <joe.doe.de.silva@xxxxxxxxx>
• Linux has timerfd, signalfd and eventfd. Is it time for a "unionfd"?
  • From: Joe Doe <joe.doe.de.silva@xxxxxxxxx>
• How is RSDP passed to kernel?
  • From: <ckim@xxxxxxxxxx>
• Failure debug messages
  • From: jim.cromie@xxxxxxxxx
• Re: get_user_pages and pinning
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• Re: get_user_pages and pinning
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: get_user_pages and pinning
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• Re: get_user_pages and pinning
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• Re: get_user_pages and pinning
  • From: daniela daniela <daniela.daniela.daniela.daniela@xxxxxxxxx>
• Re: get_user_pages and pinning
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• Re: get_user_pages and pinning
  • From: Greg KH <greg@xxxxxxxxx>
• Re: get_user_pages and pinning
  • From: Cengiz Can <cengiz@xxxxxxxxxx>
• get_user_pages and pinning
  • From: Sadanand Warrier <sadanandwarrier@xxxxxxxxx>
• Re: Looking for a good gmail alternative for kernel lists
  • From: Sebastian Fricke <sebastian.fricke.linux@xxxxxxxxx>
• Re: Looking for a good gmail alternative for kernel lists
  • From: Greg KH <greg@xxxxxxxxx>
• Looking for a good gmail alternative for kernel lists
  • From: Sebastian Fricke <sebastian.fricke.linux@xxxxxxxxx>
• Re: [PATCH 0/4] Help to debug spinlocks
  • From: John Wood <john.wood@xxxxxxx>
• Correcting errors on wiki page FAQ/Hashtables
  • From: Stefan Laufmann <slaufmann@xxxxxxxxx>
• Re: [PATCH 0/4] Help to debug spinlocks
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: [PATCH 0/4] Help to debug spinlocks
  • From: John Wood <john.wood@xxxxxxx>
• [PATCH 2/4] security/brute: Define a LSM and manage statistical data
  • From: John Wood <john.wood@xxxxxxx>
• [PATCH 3/4] securtiy/brute: Detect a brute force attack
  • From: John Wood <john.wood@xxxxxxx>
• [PATCH 1/4] security: Add LSM hook at the point where a task gets a fatal signal
  • From: John Wood <john.wood@xxxxxxx>
• [PATCH 0/4] Help to debug spinlocks
  • From: John Wood <john.wood@xxxxxxx>
• how does objcopy work? and how does the linux kernel process relocation with that stripped off image?
  • From: <ckim@xxxxxxxxxx>
• Re: How to install kernel modules after a successful compiling
  • From: FuLong Wang <fulwang@xxxxxxxxxxxxxxxxxx>
• Re: How to install kernel modules after a successful compiling
  • From: Alexander Kapshuk <alexander.kapshuk@xxxxxxxxx>
• Re: How to install kernel modules after a successful compiling
  • From: FuLong Wang <fulwang@xxxxxxxxxxxxxxxxxx>
• Re: How to install kernel modules after a successful compiling
  • From: Alexander Kapshuk <alexander.kapshuk@xxxxxxxxx>
• Re: How to install kernel modules after a successful compiling
  • From: FuLong Wang <fulwang@xxxxxxxxxxxxxxxxxx>
• Re: How to install kernel modules after a successful compiling
  • From: FuLong Wang <fulwang@xxxxxxxxxxxxxxxxxx>
• Re: How to install kernel modules after a successful compiling
  • From: Alexander Kapshuk <alexander.kapshuk@xxxxxxxxx>
• Re: [RFC PATCH 2/2] security/brute.c: Protect the stats pointer
  • From: John Wood <john.wood@xxxxxxx>
• How to install kernel modules after a successful compiling
  • From: FuLong Wang <fulwang@xxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] security/brute.c: Protect the stats pointer
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• [RFC PATCH 0/2] Locking protection for the stats pointer
  • From: John Wood <john.wood@xxxxxxx>
• [RFC PATCH 1/2] security/brute: Brute LSM
  • From: John Wood <john.wood@xxxxxxx>
• [RFC PATCH 2/2] security/brute.c: Protect the stats pointer
  • From: John Wood <john.wood@xxxxxxx>
• Re: Why new kernel version cannot be installed on old Ubuntu?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Why new kernel version cannot be installed on old Ubuntu?
  • From: Ezra Buehler <ezra@xxxxxxxx>
• Why new kernel version cannot be installed on old Ubuntu?
  • From: Joontaek Oh <na94jun@xxxxxxxxx>
• hot take question for the day
  • From: jim.cromie@xxxxxxxxx
• Re: Configuring kdump for ARM64
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Configuring kdump for ARM64
  • From: "Pankaj Vinadrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: question about arm64 __primary_switched code
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• RE: question about arm64 __primary_switched code
  • From: <ckim@xxxxxxxxxx>
• Re: question about arm64 __primary_switched code
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• question about arm64 __primary_switched code
  • From: <ckim@xxxxxxxxxx>
• es8316 i2c-ESSX8316:00: ASoC: error at soc_component_write_no_lock
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• RE: toolchain name for building linux kernel?
  • From: <ckim@xxxxxxxxxx>
• power management
  • From: Pankaj Joshi <pankaj.joshi347@xxxxxxxxx>
• RE: toolchain name for building linux kernel?
  • From: <ckim@xxxxxxxxxx>
• Re: arm64: Question about barriers with the mmu off
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• Re: toolchain name for building linux kernel?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: arm64: Question about barriers with the mmu off
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• toolchain name for building linux kernel?
  • From: <ckim@xxxxxxxxxx>
• Re: arm64: Question about barriers with the mmu off
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• Re: arm64: Question about barriers with the mmu off
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• arm64: Question about barriers with the mmu off
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• Re: arm64: Question about barriers with the mmu off
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• arm64: Question about barriers with the mmu off
  • From: Wonhyuk Yang <vvghjk1234@xxxxxxxxx>
• STATE: TASK_UNINTERRUPTIBLE (PANIC)
  • From: Marc Smith <msmith626@xxxxxxxxx>
• Re: PCI / PCIe Device Memory - Rationale for Choosing MMIO Over PMIO (and Visa-Versa)
  • From: Jack Winch <sunt.un.morcov@xxxxxxxxx>
• Re: PCI / PCIe Device Memory - Rationale for Choosing MMIO Over PMIO (and Visa-Versa)
  • From: Greg KH <greg@xxxxxxxxx>
• PCI / PCIe Device Memory - Rationale for Choosing MMIO Over PMIO (and Visa-Versa)
  • From: Jack Winch <sunt.un.morcov@xxxxxxxxx>
• initialization of global variables in u-boot
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: power management
  • From: "Pankaj Vinadrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: power management
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• power management
  • From: "Pankaj Vinadrao Joshi" <Pankaj.VJ@xxxxxxxxxxxxxxx>
• Re: sound: PCM/I2S Digital Mic & SPDIF
  • From: linux lover <caprianking2002@xxxxxxxxx>
• sound: PCM/I2S Digital Mic & SPDIF
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Setting group/other write flags not honoured in open
  • From: Marcelo Diop-Gonzalez <marcelo827@xxxxxxxxx>
• Setting group/other write flags not honoured in open
  • From: Nicky Chorley <ndchorley@xxxxxxxxx>
• Re: passing FDT(flattened device tree) to kernel during booting
  • From: Martin Kaiser <lists@xxxxxxxxx>
• Re: passing FDT(flattened device tree) to kernel during booting
  • From: linux lover <caprianking2002@xxxxxxxxx>
• passing FDT(flattened device tree) to kernel during booting
  • From: 김찬 <ckim@xxxxxxxxxx>
• Re: Invoke Firefox from kernel space
  • From: Greg KH <greg@xxxxxxxxx>
• Invoke Firefox from kernel space
  • From: Sohaib Mhmd <xunilams@xxxxxxxxx>
• Re: Recover previous kernel
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Recover previous kernel
  • From: Palash Nigam <b116031@xxxxxxxxxxxxx>
• Re: some u-boot mailing list
  • From: Ezra Buehler <ezra@xxxxxxxx>
• Re: how to pass log level to 7 from u-boot
  • From: Ezra Buehler <ezra@xxxxxxxx>
• how to pass log level to 7 from u-boot
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: Oops stack trace missing function addresses
  • From: Alexander Kapshuk <alexander.kapshuk@xxxxxxxxx>
• Re: Oops stack trace missing function addresses
  • From: Adrian Larumbe <fromago@xxxxxxxxx>
• Re: Oops stack trace missing function addresses
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Oops stack trace missing function addresses
  • From: Adrian Larumbe <fromago@xxxxxxxxx>
• Re: USB Question about devices being reconnected to the host
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• Re: some u-boot mailing list
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: USB Question about devices being reconnected to the host
  • From: Greg KH <greg@xxxxxxxxx>
• USB Question about devices being reconnected to the host
  • From: Lucas Tanure <tanure@xxxxxxxxx>
• some u-boot mailing list
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: opaque "pointer" API, model, best practice ?
  • From: jim.cromie@xxxxxxxxx
• Re: opaque "pointer" API, model, best practice ?
  • From: Greg KH <greg@xxxxxxxxx>
• opaque "pointer" API, model, best practice ?
  • From: jim.cromie@xxxxxxxxx
• Re: What's the relationship between linux-next and mainline
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• What's the relationship between linux-next and mainline
  • From: wuzhouhui <wuzhouhui14@xxxxxxxxxxxxxxxx>
• Re: How to make /dev/ttyACM0 (and friends) exclusive?
  • From: linux lover <caprianking2002@xxxxxxxxx>
• Re: How to make /dev/ttyACM0 (and friends) exclusive?
  • From: Daniel Santos <daniel.santos@xxxxxxxxx>
• Re: How are the standard file descriptors implemented?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Read the "real_parent" field of task_struct
  • From: John Wood <john.wood@xxxxxxx>
• Re: How are the standard file descriptors implemented?
  • From: linux lover <caprianking2002@xxxxxxxxx>
• How are the standard file descriptors implemented?
  • From: Sebastian Fricke <sebastian.fricke.linux@xxxxxxxxx>
• Re: make vmlinux .bss PROGBITS
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: make vmlinux .bss PROGBITS
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: make vmlinux .bss PROGBITS
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• make vmlinux .bss PROGBITS
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Fixing keyboard chatter in Linux
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Fixing keyboard chatter in Linux
  • From: Ave Milia <avemilia@xxxxxxxxxxxxxx>
• Re: Cannot boot kernel 2.6.35 or 2.6.24 with qemu 5.1
  • From: jim.cromie@xxxxxxxxx
• Re: Read the "real_parent" field of task_struct
  • From: John Wood <john.wood@xxxxxxx>
• Re: external tool to remove embedded filenames
  • From: Bhaskar Chowdhury <unixbhaskar@xxxxxxxxx>
• Re: external tool to remove embedded filenames
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: Accessing allocated space in a debugfs file
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Accessing allocated space in a debugfs file
  • From: ymdatta <ymdatta.work@xxxxxxxxx>
• Re: Read the "real_parent" field of task_struct
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• external tool to remove embedded filenames
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: Read the "real_parent" field of task_struct
  • From: John Wood <john.wood@xxxxxxx>
• Re: timer API change from kernel 4.9 to 5.0
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: timer API change from kernel 4.9 to 5.0
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Accessing allocated space in a debugfs file
  • From: Greg KH <greg@xxxxxxxxx>
• Accessing allocated space in a debugfs file
  • From: ymdatta <ymdatta.work@xxxxxxxxx>
• timer API change from kernel 4.9 to 5.0
  • From: Fabien R <theedge456@xxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Read the "real_parent" field of task_struct
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Ard Biesheuvel <ardb@xxxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Read the "real_parent" field of task_struct
  • From: John Wood <john.wood@xxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: What to do when a patch set gets no reply for 3 weeks ?
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: What to do when a patch set gets no reply for 3 weeks ?
  • From: Greg KH <greg@xxxxxxxxx>
• What to do when a patch set gets no reply for 3 weeks ?
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: Confused about which branch to patch against
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• KASLR support on ARM with Kernel 4.9 and 4.14
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Using FPGA subsystem to upload bit-stream using altera-ps-spi.
  • From: Grzegorz Heldt <grzegorz.heldt@xxxxxxxxx>
• Re: Confused about which branch to patch against
  • From: James Browning <jamesbrowning137@xxxxxxxxx>
• Re: Confused about which branch to patch against
  • From: "Gustavo A. R. Silva" <garsilva@xxxxxxxxxxxxxx>
• Re: Confused about which branch to patch against
  • From: James Browning <jamesbrowning137@xxxxxxxxx>
• Confused about which branch to patch against
  • From: James Browning <jamesbrowning137@xxxxxxxxx>
• Re: Compiled Kernel stuck in booting
  • From: jim.cromie@xxxxxxxxx
• Re: memory mapping from user space to kernel space
  • From: Greg KH <greg@xxxxxxxxx>
• memory mapping from user space to kernel space
  • From: JeongHwan Kim <frog007.kernel.kr@xxxxxxxxx>
• Re: Not able to find reference text for the latest linux kernel process scheduler
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Not able to find reference text for the latest linux kernel process scheduler
  • From: Rohit Chourasia <chourasiarohit27@xxxxxxxxx>
• Can't understand VM_PFNMAP and VM_MIXEDMAP flag
  • From: Hao Lee <haolee.swjtu@xxxxxxxxx>
• Re: Can I reboot a USB device within a driver's probe function?
  • From: Thierry Seegers <thierry.seegers@xxxxxxxxx>
• Re: Can I reboot a USB device within a driver's probe function?
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Can I reboot a USB device within a driver's probe function?
  • From: Thierry Seegers <thierry.seegers@xxxxxxxxx>
• Re: Can I reboot a USB device within a driver's probe function?
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Can I reboot a USB device within a driver's probe function?
  • From: Thierry Seegers <thierry.seegers@xxxxxxxxx>
• Re: Disable EISA and probes
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Disable EISA and probes
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Disable EISA and probes
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to acquire the occupancy time of CPUs within a certain duration, i.e. 10ms, 1ms, and etc?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Disable EISA and probes
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Disable EISA and probes
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Disable EISA and probes
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Disable EISA and probes
  • From: Greg KH <greg@xxxxxxxxx>
• Disable EISA and probes
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: cpu-freq: running the perf increases the data rate?
  • From: Artem Bityutskiy <dedekind1@xxxxxxxxx>
• How and where are a processes's PTEs set when mmaping a file in a tmpfs?
  • From: Bijan Tabatabai <bijan311@xxxxxxxxx>
• Re: Please assess this patch: [PATCH] Docs: FIxed spelling errors in Documentation/devicetree/bindings/
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Please assess this patch: [PATCH] Docs: FIxed spelling errors in Documentation/devicetree/bindings/
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Please assess this patch: [PATCH] Docs: FIxed spelling errors in Documentation/devicetree/bindings/
  • From: linux lover <caprianking2002@xxxxxxxxx>
• Please assess this patch: [PATCH] Docs: FIxed spelling errors in Documentation/devicetree/bindings/
  • From: Marlon Rac Cambasis <marlonrc08@xxxxxxxxx>
• Re: Relationship between Rx/Tx ring and Skbuff.
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: HOW DO I KNOW SOMEONE RECEIVED MY PATCH
  • From: Ron Guilmet <ronpguilmet@xxxxxxxxx>
• Re: HOW DO I KNOW SOMEONE RECEIVED MY PATCH
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• HOW DO I KNOW SOMEONE RECEIVED MY PATCH
  • From: Ronald P Guilmet <ronpguilmet@xxxxxxxxx>
• Re: How to acquire the occupancy time of CPUs within a certain duration, i.e. 10ms, 1ms, and etc?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: Userspace app crash causes system crash on do_exit probe
  • From: Greg KH <greg@xxxxxxxxx>
• Userspace app crash causes system crash on do_exit probe
  • From: César Augusto Marcelino dos Santos <dev.cmsantos@xxxxxxxxx>
• Re: cpu-freq: running the perf increases the data rate?
  • From: Subhashini Rao Beerisetty <subhashbeerisetty@xxxxxxxxx>
• Re: Relationship between Rx/Tx ring and Skbuff.
  • From: Richard Sailer <richard_siegfried@xxxxxxxxxxxx>
• Re: What mailer to use with Gmail?
  • From: Richard Sailer <richard_siegfried@xxxxxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• How to acquire the occupancy time of CPUs within a certain duration, i.e. 10ms, 1ms, and etc?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: Pawan Gupta <writetopawan@xxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• cpu-freq: running the perf increases the data rate?
  • From: Subhashini Rao Beerisetty <subhashbeerisetty@xxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: Leam Hall <leamhall@xxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: Greg KH <greg@xxxxxxxxx>
• Cannot boot kernel 2.6.35 or 2.6.24 with qemu 5.1
  • From: Cao Nitro <nitrocao51@xxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: Garrit Franke <garritfranke@xxxxxxxxx>
• Re: Please give advise about my first patch attempt
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Please give advise about my first patch attempt
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: What mailer to use with Gmail?
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• What mailer to use with Gmail?
  • From: Leam Hall <leamhall@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Opening /proc/<pid>/net/dev prevents network namespace from expiring
  • From: Grant Taylor <gtaylor@xxxxxxxxxxxxxxxxxx>
• Re: Opening /proc/<pid>/net/dev prevents network namespace from expiring
  • From: Greg KH <greg@xxxxxxxxx>
• Opening /proc/<pid>/net/dev prevents network namespace from expiring
  • From: Arne Welzel <arne.welzel@xxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Julia Lawall <julia.lawall@xxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: [Cocci] coccinelle: Convert comma to semicolons (was Re: [PATCH] checkpatch: Add test for comma use that should be semicolon)
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: How to pass flag from makefile to preprocesor when building external kernel module
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• How to pass flag from makefile to preprocesor when building external kernel module
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• RE: Scheduler benchmarks
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Confusion about icsk_accept_queue
  • From: tianyu chen <ch.tianyu89@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: peter enderborg <peter.enderborg@xxxxxxxx>
• Re: Scheduler benchmarks
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Validity of ioremap pointer within the kernel module
  • From: Eduard Fuchs <lists.kel@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Re: Scheduler benchmarks
  • From: Greg KH <greg@xxxxxxxxx>
• Scheduler benchmarks
  • From: Muni Sekhar <munisekharrms@xxxxxxxxx>
• Does "i_mutex" in comments mean inode_lock() in code ?
  • From: "Thomas Schmitt" <scdbackup@xxxxxxx>
• Re: Help to test the powerpc architecture
  • From: jim.cromie@xxxxxxxxx
• Re: Help to test the powerpc architecture
  • From: Santosh S <santosh@xxxxxxxxxx>
• Re: functions with empty body in file /kernel/events/core
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• delayed_put_task_struct() used by put_task_struct_rcu_user() never gets called
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• functions with empty body in file /kernel/events/core
  • From: cristian andres vargas gonzalez <vargascristian@xxxxxxxxxxxxxxxx>
• what are all the .cold symbols in system.map?
  • From: jim.cromie@xxxxxxxxx
• Re: How is the value of KernelStack in /proc/meminfo computed ?
  • From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@xxxxxxxxx>
• How is the value of KernelStack in /proc/meminfo computed ?
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: [PATCH 0/8] dyndbg: WIP diet plan
  • From: jim.cromie@xxxxxxxxx
• Re: [PATCH 0/8] dyndbg: WIP diet plan
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Relationship between Rx/Tx ring and Skbuff.
  • From: Vasu M <vasu.kernel@xxxxxxxxx>
• Re: Relationship between Rx/Tx ring and Skbuff.
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: [PATCH 0/8] dyndbg: WIP diet plan
  • From: jim.cromie@xxxxxxxxx
• Relationship between Rx/Tx ring and Skbuff.
  • From: Vasu M <vasu.kernel@xxxxxxxxx>
• [PATCH 7/8] dyndbg: enable 'cache' of active pr_debug callsites
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 4/8] dyndbg: split struct _ddebug in 2, creating _ddebug_callsite
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 3/8] dyndbg: select ZPOOL in Kconfig.debug
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 2/8] dyndbg: motivate a diet plan
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 1/8] dyndbg: give %3u width in pr-format, cosmetic only
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 8/8] dyndbg: add locking around zpool-add loop in zpool-init
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 6/8] dyndbg: ddebug_zpool_remove
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 5/8] dyndbg: WIP replace __dyndbg_callsite section with a zs-pool copy.
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 0/8] dyndbg: WIP diet plan
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: CONFIG_KDB_KEYBOARD
  • From: jim.cromie@xxxxxxxxx
• Re: CONFIG_KDB_KEYBOARD
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• CONFIG_KDB_KEYBOARD
  • From: jim.cromie@xxxxxxxxx
• Help to test the powerpc architecture
  • From: Oscar Carter <oscar.carter@xxxxxxx>
• Re: Compiled Kernel stuck in booting
  • From: Bryan Brattlof <hello@xxxxxxxxxxxxxxxxx>
• Compiled Kernel stuck in booting
  • From: Yashodhan Joshi <yjdoc2@xxxxxxxxx>
• How to check my wifi driver iwlwifi supports "wifi 5G band 4"
  • From: Malatesh Ankasapur <malatesh10@xxxxxxxxx>
• Re: test tools to measure performance of the Linux kernel
  • From: Greg KH <greg@xxxxxxxxx>
• test tools to measure performance of the Linux kernel
  • From: Subhashini Rao Beerisetty <subhashbeerisetty@xxxxxxxxx>
• [PATCH 3/3] dyndbg: fixup/correct assumptions re ptr-vals
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 2/3] dyndbg: zhandle+1 plus info tweaks, BUG_ONs
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 1/3] dyndbg: WIP replace __dyndbg section with a zs-pool copy.
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• [PATCH 0/3] dyndbg: WIP semi-viable diet plan ?
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Unable to manually bind driver
  • From: Isaac <ckl.isaac@xxxxxxxxx>
• i2c possible patch
  • From: Nuno Sá <noname.nuno@xxxxxxxxx>
• Re: Dubios pointer casting with put_user()
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Dubios pointer casting with put_user()
  • From: Richard Sailer <richard_siegfried@xxxxxxxxxxxx>
• Why disabling CONFIG_APIC may cause the kernel failing to boot up?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• How to comfirm whether __GI___clock_gettime() implemented as fast system call or not on x86_64 platform with Linux 4.19.84?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Old Driver Code Using Streams
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Old Driver Code Using Streams
  • From: Steve Boley <steve@xxxxxxxx>
• Re: Dubios pointer casting with put_user()
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Help troubleshooting memory leak when highres=on
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Dubios pointer casting with put_user()
  • From: Richard Sailer <richard_siegfried@xxxxxxxxxxxx>
• Dubios pointer casting with put_user()
  • From: Richard Sailer <richard_siegfried@xxxxxxxxxxxx>
• Re: How to comprehend this code snippet: __asm__ __volatile__("rdtsc" : "=A"(t))?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to comprehend this code snippet: __asm__ __volatile__("rdtsc" : "=A"(t))?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: How to comprehend this code snippet: __asm__ __volatile__("rdtsc" : "=A"(t))?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• How to comprehend this code snippet: __asm__ __volatile__("rdtsc" : "=A"(t))?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Why the trigered counts of NMIs is equivalent to PMI's?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: When returning from schedule_tail() ...
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: When returning from schedule_tail() ...
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• When returning from schedule_tail() ...
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: [PATCH] mmc: cqhci: Fix a print format for the task descriptor
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: What's tha KOBJ_MAX action used for?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: What's tha KOBJ_MAX action used for?
  • From: Garrit Franke <garritfranke@xxxxxxxxx>
• Re: Turn private hugetlb mapping into VM_SHARED
  • From: heep <0x60@xxxxx>
• Re: How to understand the comment of macro *compute_indices*?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: What's tha KOBJ_MAX action used for?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• How to understand the comment of macro *compute_indices*?
  • From: carver <carver.lio@xxxxxxxxxxx>
• Re: What's tha KOBJ_MAX action used for?
  • From: Greg KH <greg@xxxxxxxxx>
• What's tha KOBJ_MAX action used for?
  • From: Garrit Franke <garritfranke@xxxxxxxxx>
• Re: Regarding Linux kernel SMP and task switching CPU
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• RE: Are kernel trees the same as a branch in terms of git?
  • From: cristian andres vargas gonzalez <vargascristian@xxxxxxxxxxxxxxxx>
• Re: Are kernel trees the same as a branch in terms of git?
  • From: Richard Sailer <richard_siegfried@xxxxxxxxxxxx>
• Turn private hugetlb mapping into VM_SHARED
  • From: heep <0x60@xxxxx>
• Re: Regarding Linux kernel SMP and task switching CPU
  • From: CVS <cvs268@xxxxxxxxx>
• Re: Regarding Linux kernel SMP and task switching CPU
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Regarding Linux kernel SMP and task switching CPU
  • From: CVS <cvs268@xxxxxxxxx>
• Re: Why are there "<IRQ>" and "</IRQ>" in the call trace section? What does them imply?
  • From: CVS <cvs268@xxxxxxxxx>
• What are the major differences between soft lockup and hard lockup which are both detected by watchdog?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• What methods or tools could be used to investigate the causes of hard or soft lockup?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Why are there "<IRQ>" and "</IRQ>" in the call trace section? What does them imply?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: new TODO list item
  • From: Suraj Upadhyay <usuraj35@xxxxxxxxx>
• Why are there "<IRQ>" and "</IRQ>" in the call trace section? What does them imply?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Are kernel trees the same as a branch in terms of git?
  • From: CRISTIAN ANDRES VARGAS GONZALEZ <vargascristian@xxxxxxxxxxxxxxxx>
• Re: how to debug problem with "failing unmounting"
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: how to debug problem with "failing unmounting"
  • From: Abu Rasheda <rcpilot2010@xxxxxxxxx>
• how to debug problem with "failing unmounting"
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Regarding Linux kernel SMP and task switching CPU
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: What are the most frequently used methods for system level-tracing?
  • From: Augusto Mecking Caringi <augustocaringi@xxxxxxxxx>
• What are the most frequently used methods for system level-tracing?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• TPM error 256 (TPM_RC_INITIALIZE)
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: Kbuild support for rebuilding a single driver gone?
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: How can I investigate the cause of "watchdog: BUG: soft lockup"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Kbuild support for rebuilding a single driver gone?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: printk() format %pS wrong symbol
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Re: printk() format %pS wrong symbol
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Kbuild support for rebuilding a single driver gone?
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: Kbuild support for rebuilding a single driver gone?
  • From: Greg KH <greg@xxxxxxxxx>
• Kbuild support for rebuilding a single driver gone?
  • From: Bjørn Mork <bjorn@xxxxxxx>
• What are the relations between queued_spin_lock_slowpath function and __raw_spin_lock function?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: printk() format %pS wrong symbol
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: For a bug in lib/vsprintf.c where should a patch be sent to ?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: There is "softlockup_tick()" function in the source code of linux-2.6.32, but what's the corresponding function name in the linux-4.9 or later?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: For a bug in lib/vsprintf.c where should a patch be sent to ?
  • From: Santosh Sivaraj <santosh@xxxxxxxxxx>
• Re: For a bug in lib/vsprintf.c where should a patch be sent to ?
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• For a bug in lib/vsprintf.c where should a patch be sent to ?
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: There is "softlockup_tick()" function in the source code of linux-2.6.32, but what's the corresponding function name in the linux-4.9 or later?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Git pull and untracked files
  • From: Gautam Bhat <mindentropy@xxxxxxxxx>
• There is "softlockup_tick()" function in the source code of linux-2.6.32, but what's the corresponding function name in the linux-4.9 or later?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: Pavel Machek <pavel@xxxxxx>
• Re: printk() format %pS wrong symbol
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• Re: printk() format %pS wrong symbol
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: Pavel Machek <pavel@xxxxxx>
• Re: printk() format %pS wrong symbol
  • From: Valentin Vidić <vvidic@xxxxxxxxxxxxxxxxxxxxxx>
• printk() format %pS wrong symbol
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: How can I investigate the cause of "watchdog: BUG: soft lockup"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: How can I investigate the cause of "watchdog: BUG: soft lockup"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: How can I investigate the cause of "watchdog: BUG: soft lockup"?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How can I investigate the cause of "watchdog: BUG: soft lockup"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: How can I investigate the cause of "watchdog: BUG: soft lockup"?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• How can I investigate the cause of "watchdog: BUG: soft lockup"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• modprobe rbtree-test nnodes=1000 gets soft lockup
  • From: jim.cromie@xxxxxxxxx
• Re: How do you investigate the cause of total hang? Is there some information that I should pay attention to in order to get some hint?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Could interruptions be handled while current process context is switching?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Is there some method or software that could purposely generate a lot of physical memory fragmentations on linux?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Is there some method or software that could purposely generate a lot of physical memory fragmentations on linux?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Is there some method or software that could purposely generate a lot of physical memory fragmentations on linux?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Where to place my driver
  • From: jaap aarts <jaap.aarts1@xxxxxxxxx>
• Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: How do you investigate the cause of total hang? Is there some information that I should pay attention to in order to get some hint?
  • From: Cong Wang <xiyou.wangcong@xxxxxxxxx>
• How do you investigate the cause of total hang? Is there some information that I should pay attention to in order to get some hint?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Is there some method or software that could purposely generate a lot of physical memory fragmentations on linux?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Where to place my driver
  • From: Greg KH <greg@xxxxxxxxx>
• Where to place my driver
  • From: jaap aarts <jaap.aarts1@xxxxxxxxx>
• Re: Git pull and untracked files
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Git pull and untracked files
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Git pull and untracked files
  • From: Gautam Bhat <mindentropy@xxxxxxxxx>
• Re: Advice about the linux kernel development process
  • From: Oscar Carter <oscar.carter@xxxxxxx>
• Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: Greg KH <greg@xxxxxxxxx>
• Are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA, PCI, serial port and etc) by vmalloc() instead of kmalloc()?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Besides kmalloc() is more efficient, are there some potential problems that I should be aware of if I allocate the memory which doesn't have any relation to peripheral hardwares(i.e. DMA,PCI,serial port and etc) by vmalloc() instead of kmalloc() to avoid the page allocation failure?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Are there still some methods that could be used by the Linux kernel to reduce memory fragmentation while both CONFIG-MIGRATION and CONFIG-COMPACTION are disabled?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• What are the potential problems if the option CONFIG_MIGRATION is disabled?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Advice about the linux kernel development process
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Crash recovery kernel error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Advice about the linux kernel development process
  • From: Oscar Carter <oscar.carter@xxxxxxx>
• Re: Crash recovery kernel error
  • From: Harsh chopra <serviceprovider.tester@xxxxxxxxx>
• Re: Why does “page allocation failure” occur whereas there are still “58*4096kB (C)” could be used?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: How do you comprehend the saying that the kernel's memory is not pageable whereas get_free_page use a page-oriented technique?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: How do you comprehend the saying that the kernel's memory is not pageable whereas get_free_page use a page-oriented technique?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• How do you comprehend the saying that the kernel's memory is not pageable whereas get_free_page use a page-oriented technique?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Why does “page allocation failure” occur whereas there are still “58*4096kB (C)” could be used?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• What the differences between "__GFP_NOFAIL" and "__GFP_REPEAT"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: Crash recovery kernel error
  • From: Sebastian Fricke <sebastian.fricke.linux@xxxxxxxxx>
• About the uage of "__GFP_COMP"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: [staging-testing] drivers/staging/wfx/hif_tx.c
  • From: Jérôme Pouiller <jerome.pouiller@xxxxxxxxxx>
• Re: Current Instruction Pointer Along Memory Access for A specific Process
  • From: Garrit Franke <garritfranke@xxxxxxxxx>
• Crash recovery kernel error
  • From: Harsh chopra <serviceprovider.tester@xxxxxxxxx>
• Why did not the kernel use the memory block named by "Node 0 DMA" while the argument of funtion kzalloc is "GFP_KERNEL"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Why the kernel could not use the memory block contained by "Node 0 DMA" while the argument of kzalloc() is "GFP_KERNEL"?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• Re: There is a question mark in front of the function name in the call trace log.What does the question mark imply?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Why does “page allocation failure” occur whereas there are still “58*4096kB (C)” could be used?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Why does “page allocation failure” occur whereas there are still “58*4096kB (C)” could be used?
  • From: 孙世龙 sunshilong <sunshilong369@xxxxxxxxx>
• There is a question mark in front of the function name in the call trace log.What does the question mark imply?
  • From: 孙世龙 <sunshilong369@xxxxxxxxx>
• Re: Why does “page allocation failure” occur whereas there are still “58*4096kB (C)” could be used?
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: DKMS module and recipe for target '.../virtualbox/5.2.34/build/vboxdrv' failed
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: DKMS module and recipe for target '.../virtualbox/5.2.34/build/vboxdrv' failed
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Why does “page allocation failure” occur whereas there are still “58*4096kB (C)” could be used?
  • From: 孙世龙 <sunshilong369@xxxxxxxxx>
• Re: DKMS module and recipe for target '.../virtualbox/5.2.34/build/vboxdrv' failed
  • From: Greg KH <greg@xxxxxxxxx>
• DKMS module and recipe for target '.../virtualbox/5.2.34/build/vboxdrv' failed
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Greg KH <greg@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Greg KH <greg@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Cannot get FIQ to work properly on raspberry zero
  • From: Sietse Achterop <s.achterop@xxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Martin Kaiser <lists@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Greg KH <greg@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Greg KH <greg@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Greg KH <greg@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• Re: the cost of EXPORT_SYMBOL_GPL
  • From: Greg KH <greg@xxxxxxxxx>
• the cost of EXPORT_SYMBOL_GPL
  • From: Tomek The Messenger <tomekthemessenger@xxxxxxxxx>
• issue with ASUS Fan maximal mode
  • From: Sergey Ivanov <icegood1980@xxxxxxxxx>
• Re: replacing if-then-else strcmp ladders with switch cases
  • From: jim.cromie@xxxxxxxxx
• Re: replacing if-then-else strcmp ladders with switch cases
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• replacing if-then-else strcmp ladders with switch cases
  • From: jim.cromie@xxxxxxxxx
• Re: sticky bits in /proc etc
  • From: jim.cromie@xxxxxxxxx
• Re: sticky bits in /proc etc
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Generic way for verifying GPIO wakeup capability
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• sticky bits in /proc etc
  • From: jim.cromie@xxxxxxxxx
• [staging-testing] drivers/staging/wfx/hif_tx.c
  • From: Mohamed Dawod <mhm.dawod@xxxxxxxxx>
• Re: Current Instruction Pointer Along Memory Access for A specific Process
  • From: Irfan Ullah (울라 이르판) <irfan@xxxxxxxxxxxxx>
• Generic way for verifying GPIO wakeup capability
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Current Instruction Pointer Along Memory Access for A specific Process
  • From: Greg KH <greg@xxxxxxxxx>
• Current Instruction Pointer Along Memory Access for A specific Process
  • From: Irfan Ullah (울라 이르판) <irfan@xxxxxxxxxxxxx>
• Re: IPX support
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• IPX support
  • From: Dmitry Podgorny <pasis.ua@xxxxxxxxx>
• Re: Computing resources required for kernel development
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Computing resources required for kernel development
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Computing resources required for kernel development
  • From: Harsh chopra <serviceprovider.tester@xxxxxxxxx>
• Re: Computing resources required for kernel development
  • From: Suraj Upadhyay <usuraj35@xxxxxxxxx>
• Computing resources required for kernel development
  • From: Harsh chopra <serviceprovider.tester@xxxxxxxxx>
• Re: sdhci_msm issues with cold-plugged SD cards
  • From: Iskren Chernev <iskren.chernev@xxxxxxxxx>
• Re: sdhci_msm issues with cold-plugged SD cards
  • From: Veerabhadrarao Badiganti <vbadigan@xxxxxxxxxxxxxx>
• sdhci_msm issues with cold-plugged SD cards
  • From: Iskren Chernev <iskren.chernev@xxxxxxxxx>
• Check for preemption only when returning from interrupt ?
  • From: Taeung Song <treeze.taeung@xxxxxxxxx>
• Re: sound over USB
  • From: Ricard Wanderlof <ricardw@xxxxxxxx>
• Re: sdhci_msm issues with cold-plugged SD cards
  • From: Ulf Hansson <ulf.hansson@xxxxxxxxxx>
• How to find the wait_queue of a task in TASK_INTERRUPTIBLE or TASK_UNINTERRUPTIBLE state
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: __STDC_VERSION__ : What C dialect c89, c99,gnu90 kernel compiies
  • From: 67hz <67hz@xxxxxxxxxxxxxx>
• Re: __STDC_VERSION__ : What C dialect c89, c99,gnu90 kernel compiies
  • From: Greg KH <greg@xxxxxxxxx>
• __STDC_VERSION__ : What C dialect c89, c99,gnu90 kernel compiies
  • From: "Lev R. Oshvang ." <levonshe@xxxxxxxxx>
• Re: Estimating total memory usage in any Linux system
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Estimating total memory usage in any Linux system
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>
• Re: Estimating total memory usage in any Linux system
  • From: Pintu Agarwal <pintu.ping@xxxxxxxxx>
• Re: Estimating total memory usage in any Linux system
  • From: "Valdis Klētnieks" <valdis.kletnieks@xxxxxx>