org.kernelnewbies.kernelnewbies archive

410 archived articles, newest first (page 1 of 5). Latest articles →

Runtime ownership and driver binding for SPI-NOR shared with FPGA
Wed, 15 Jul 2026 18:13:15 +0200
Patryk <[email protected]> • #23575
Re: Seeking guidance on detecting mount point inactivity
Mon, 6 Jul 2026 10:27:47 +0330
Ali Nasrolahi <[email protected]> • #23574
Re: Seeking guidance on detecting mount point inactivity
Sun, 5 Jul 2026 17:34:23 +0100
Raka Gunarto <[email protected]> • #23573
Re: Seeking guidance on detecting mount point inactivity
Sun, 5 Jul 2026 08:34:06 +0330
Ali Nasrolahi <[email protected]> • #23572
Re: Seeking guidance on detecting mount point inactivity
Fri, 3 Jul 2026 10:54:09 +0100
Raka Gunarto <[email protected]> • #23571
Re: Seeking guidance on detecting mount point inactivity
Fri, 3 Jul 2026 09:05:16 +0000
Ali Nasrolahi <[email protected]> • #23570
Re: Seeking guidance on detecting mount point inactivity
Tue, 30 Jun 2026 16:21:31 +0200
Richard <[email protected]> • #23569
Seeking guidance on detecting mount point inactivity
Thu, 25 Jun 2026 14:37:27 +0000
Ali Nasrolahi <[email protected]> • #23568
[PATCH] docs fix typo 'busses' --> 'buses' in phy.rst
Fri, 19 Jun 2026 18:36:32 +0000
Pratik <[email protected]> • #23567
Re: Stack Sizes
Sun, 14 Jun 2026 19:17:00 -0300
Agatha Isabelle Moreira <[email protected]> • #23566
Re: Stack Sizes
Fri, 12 Jun 2026 10:11:28 +0100
Anuz Pratap Singh Tomar <[email protected]> • #23565
Stack Sizes
Fri, 12 Jun 2026 01:04:40 -0300
Agatha Isabelle Moreira <[email protected]> • #23564
Re: [PATCH] get_maintainer: add recipients to output of script
Mon, 8 Jun 2026 16:32:20 -0300
Agatha Isabelle Moreira <[email protected]> • #23563
Re: [PATCH] get_maintainer: add recipients to output of script
Mon, 8 Jun 2026 13:50:19 -0300
Agatha Isabelle Moreira <[email protected]> • #23562
Re: [PATCH] get_maintainer: add recipients to output of script
Mon, 08 Jun 2026 09:00:33 -0700
Joe Perches <[email protected]> • #23561
Re: [PATCH] get_maintainer: add recipients to output of script
Mon, 08 Jun 2026 08:52:00 -0700
Joe Perches <[email protected]> • #23560
Re: [PATCH] get_maintainer: add recipients to output of script
Mon, 08 Jun 2026 08:29:16 -0700
Joe Perches <[email protected]> • #23559
Re: why don't unlock_buffer call directly clear_and_wake_up_bit?
Tue, 19 May 2026 19:51:18 -0300
Agatha Isabelle Moreira <[email protected]> • #23558
Re: why don't unlock_buffer call directly clear_and_wake_up_bit?
Tue, 19 May 2026 19:42:39 -0300
Agatha Isabelle Moreira <[email protected]> • #23557
Re: Question
Tue, 19 May 2026 17:42:54 -0300
Agatha Isabelle Moreira <[email protected]> • #23556
Re: Newbie Question: Clarifying I2C Master/Slave roles and device tree binding for client hardware info
Mon, 18 May 2026 07:30:08 +0200
Greg KH <[email protected]> • #23555
Newbie Question: Clarifying I2C Master/Slave roles and device tree binding for client hardware info
Sun, 17 May 2026 12:13:05 -0600
William Torrez Corea <[email protected]> • #23554
Question
Sun, 17 May 2026 12:08:01 -0600
William Torrez Corea <[email protected]> • #23553
Newbie Question: Clarifying I2C Master/Slave roles and device tree binding for client hardware info
Sat, 9 May 2026 21:41:59 +0530
Momin M <[email protected]> • #23552
Re: Upstreaming - how to deal with vendor fork
Fri, 01 May 2026 23:13:52 +0200
"Linus Probert" <[email protected]> • #23551
Re: Upstreaming - how to deal with vendor fork
Thu, 30 Apr 2026 09:15:39 +0200
Greg KH <[email protected]> • #23550
Re: Upstreaming - how to deal with vendor fork
Wed, 29 Apr 2026 19:42:14 +0200
"Linus Probert" <[email protected]> • #23549
Upstreaming - how to deal with vendor fork
Wed, 29 Apr 2026 15:27:57 +0200
Patryk <[email protected]> • #23548
why don't unlock_buffer call directly clear_and_wake_up_bit?
Sat, 21 Mar 2026 07:54:39 +0000
shuo chen <[email protected]> • #23547
Re: Kernel test
Sun, 1 Mar 2026 20:44:53 +0200
David Lishchyshen <[email protected]> • #23546
Re: Kernel test
Sat, 28 Feb 2026 20:45:49 +0000
Ozgur Kara <[email protected]> • #23545
Re: Kernel test
Sun, 01 Mar 2026 01:26:36 +0530
Siddh Raman Pant <[email protected]> • #23544
Re: Kernel test
Sat, 28 Feb 2026 21:29:16 +0200
David Lishchyshen <[email protected]> • #23543
Re: Kernel test
Sun, 01 Mar 2026 00:08:08 +0530
Siddh Raman Pant <[email protected]> • #23542
Re: Kernel test
Sat, 28 Feb 2026 20:19:32 +0200
David Lishchyshen <[email protected]> • #23541
Re: संदर्भ: Fw d: Custom email
Sat, 28 Feb 2026 15:41:11 +0530
Siddh Raman Pant <[email protected]> • #23540
Re: संदर्भ: Fwd: Custom email
Sat, 28 Feb 2026 11:59:52 +0200
David Lishchyshen <[email protected]> • #23539
Re: Kernel test
Sat, 28 Feb 2026 15:23:24 +0530
Siddh Raman Pant <[email protected]> • #23538
Re: संद र्भ: Fw d: Custom email
Sat, 28 Feb 2026 15:20:15 +0530
Siddh Raman Pant <[email protected]> • #23537
Kernel test
Sat, 28 Feb 2026 07:12:25 +0000
"David Lishchyshen" <[email protected]> • #23536
Re: Mailing list for a question related to ethernet phy
Wed, 25 Feb 2026 11:42:25 -0300
"Giovanni Tirloni" <[email protected]> • #23535
Mailing list for a question related to ethernet phy
Wed, 25 Feb 2026 08:36:08 +0100
Patryk <[email protected]> • #23534
Re: संदर्भ: Fwd: Custom email
Tue, 24 Feb 2026 18:44:13 +0000
"David Lishchyshen" <[email protected]> • #23533
Re: संदर्भ: Fwd: Custom email
Tue, 24 Feb 2026 18:37:22 +0000
"David Lishchyshen" <[email protected]> • #23532
Re: संदर्भ: Fwd: Custom email
Tue, 24 Feb 2026 11:19:03 +0200
David Lishchyshen <[email protected]> • #23531
Re: संद र्भ: Fw d: Custom email
Tue, 24 Feb 2026 14:16:54 +0530
Siddh Raman Pant <[email protected]> • #23530
Re: संदर्भ: Fwd: Custom email
Tue, 24 Feb 2026 10:24:11 +0200
David Lishchyshen <[email protected]> • #23529
संदर्भ: Fwd: Custom email
Tue, 24 Feb 2026 13:35:54 +0530
Siddh Raman Pant <[email protected]> • #23528
Fwd: Custom email
Tue, 24 Feb 2026 09:54:32 +0200
David Lishchyshen <[email protected]> • #23527
Re: Query: Y2038 patch series for 3.18 Kernel
Tue, 20 Jan 2026 10:03:49 +0100
"Arnd Bergmann" <[email protected]> • #23526
Help figuring out how to associate a device with GNSS subsystem (gnss_* modules)
Tue, 20 Jan 2026 00:17:32 +0000
John Scott <[email protected]> • #23525
Re: [PATCH 0/2] UIO: Optional custom threaded IRQ handler
Mon, 5 Jan 2026 13:45:41 +0100
Greg KH <[email protected]> • #23524
Re: [PATCH 0/2] UIO: Optional custom threaded IRQ handler
Mon, 5 Jan 2026 11:25:48 +0100
Greg KH <[email protected]> • #23523
Re: [PATCH 0/2] UIO: Optional custom threaded IRQ handler
Sun, 4 Jan 2026 09:41:47 +0100
Greg KH <[email protected]> • #23522
Apology for accidental spam Re: post
Sat, 20 Dec 2025 19:55:44 +0800
laughing lucky <[email protected]> • #23521
Re: post
Fri, 19 Dec 2025 23:35:00 -0700
Louis-Ladd <[email protected]> • #23520
post
Sat, 20 Dec 2025 13:10:52 +0800
laughing lucky <[email protected]> • #23519
Re: Development environment discussion
Thu, 18 Dec 2025 16:02:50 +0000
Raka Gunarto <[email protected]> • #23518
Re: Development environment discussion
Thu, 18 Dec 2025 14:50:21 +0100 (CET)
[email protected] • #23517
Re: Development environment discussion
Thu, 18 Dec 2025 01:26:39 -0700
Louis <[email protected]> • #23516
Re: Development environment discussion
Wed, 17 Dec 2025 20:41:15 -0600
Isaac Gonzalez <[email protected]> • #23515
Re: Development environment discussion
Wed, 17 Dec 2025 17:44:38 +0000
"Billie Alsup (balsup)" <[email protected]> • #23514
Re: Development environment discussion
Wed, 17 Dec 2025 17:39:44 +0100 (CET)
[email protected] • #23513
Development environment discussion
Wed, 17 Dec 2025 08:49:46 -0600
Isaac Gonzalez <[email protected]> • #23512
Re:  Query: Y2038 patch series for 3.18 Kernel
Wed, 17 Dec 2025 10:23:09 +0530
Pintu Kumar Agarwal <[email protected]> • #23511
Re: Hello form a new Kernel contributor
Thu, 20 Nov 2025 12:46:58 -0500 (EST)
"Robert P. J. Day" <[email protected]> • #23510
Re: Simple mutex_destroy question
Thu, 20 Nov 2025 14:43:58 +0100
Greg KH <[email protected]> • #23509
Re: Simple mutex_destroy question
Thu, 20 Nov 2025 10:27:06 +0000
Lucas Tanure <[email protected]> • #23508
Re: Simple mutex_destroy question
Wed, 19 Nov 2025 16:27:40 +0000
"Billie Alsup (balsup)" <[email protected]> • #23507
Re: Simple mutex_destroy question
Wed, 19 Nov 2025 13:08:56 +0000
Raka Gunarto <[email protected]> • #23506
Re: Simple mutex_destroy question
Wed, 19 Nov 2025 10:08:50 +0000
Lucas Tanure <[email protected]> • #23505
Simple mutex_destroy question
Fri, 14 Nov 2025 10:42:21 +0000
Lucas Tanure <[email protected]> • #23504
Re:  Query: Y2038 patch series for 3.18 Kernel
Thu, 06 Nov 2025 09:17:21 +0100
"Arnd Bergmann" <[email protected]> • #23503
Re:  Query: Y2038 patch series for 3.18 Kernel
Wed, 5 Nov 2025 15:17:58 +0530
Pintu Kumar Agarwal <[email protected]> • #23502
Re:  Query: Y2038 patch series for 3.18 Kernel
Tue, 04 Nov 2025 10:47:33 +0100
"Arnd Bergmann" <[email protected]> • #23501
Re:  Query : Y2038 patch series for 3.18 Kernel
Tue, 4 Nov 2025 14:08:48 +0900
Greg KH <[email protected]> • #23500
Re:  Query: Y2038 patch series for 3.18 Kernel
Tue, 4 Nov 2025 10:32:28 +0530
Pintu Kumar Agarwal <[email protected]> • #23499
Re: Query: Y2038 patch series for 3.18 Kernel
Mon, 03 Nov 2025 10:34:45 +0530
Siddh Raman Pant <[email protected]> • #23498
Query: Y2038 patch series for 3.18 Kernel
Mon, 3 Nov 2025 09:57:18 +0530
Pintu Kumar Agarwal <[email protected]> • #23497
Re: Rust: how to implement file_operations for a misc device?
Wed, 24 Sep 2025 12:27:30 +0200
Greg KH <[email protected]> • #23496
Rust: how to implement file_operations for a misc device?
Tue, 23 Sep 2025 18:47:25 +0200
Fabio <[email protected]> • #23495
Re: Existing patches of similar content
Mon, 15 Sep 2025 12:41:06 +0000
Torin Carey <[email protected]> • #23494
Re: Existing patches of similar content
Mon, 8 Sep 2025 14:48:27 -0700
Alison Schofield <[email protected]> • #23493
Existing patches of similar content
Sun, 07 Sep 2025 18:57:02 +0000
Torin Carey <[email protected]> • #23492
Re: Where is getname () defined
Sun, 31 Aug 2025 12:25:37 -0400
"Partha P. Mukherjee" <[email protected]> • #23491
Re: Where is getname () defined
Fri, 29 Aug 2025 12:38:20 -0700
Alison Schofield <[email protected]> • #23490
Re: Where is getname () defined
Fri, 29 Aug 2025 15:19:59 -0400
Dan Bokser <[email protected]> • #23489
Where is getname () defined
Fri, 29 Aug 2025 18:43:32 +0000
Vulturus <[email protected]> • #23488
FPGA based system controller
Thu, 28 Aug 2025 10:37:25 +0200
Patryk <[email protected]> • #23487
Re: git: list of my complaints about future graft removal
Wed, 20 Aug 2025 21:11:30 +0700
Bagas Sanjaya <[email protected]> • #23486
Exchanging data between CPU and FPGA through shared DDR
Tue, 19 Aug 2025 12:52:28 +0200
Patryk <[email protected]> • #23485
a little testing help from my friends
Sat, 2 Aug 2025 23:18:46 -0600
[email protected] • #23484
Re: Linux Device Performance Analyses - Where are my cylces?
Fri, 1 Aug 2025 22:42:03 +0800
Levi Zim <[email protected]> • #23483
Linux Device Performance Analyses - Where are my cylces?
Fri, 1 Aug 2025 10:34:34 +0100
Lucas Tanure <[email protected]> • #23482
Re: [RFC PATCH 0/1] compiler_types.h: introduce ASSUME_NONNULL macro for static analysis
Fri, 25 Jul 2025 10:04:56 -0700
Tom Mitchell <[email protected]> • #23481
Re: [RFC PATCH 0/1] compiler_types.h: introduce ASSUME_NONNULL macro for static analysis
Fri, 25 Jul 2025 16:07:36 +0100
Raka Gunarto <[email protected]> • #23480
Re: [RFC PATCH 0/1] compiler_types.h: introduce ASSUME_NONNULL macro for static analysis
Fri, 25 Jul 2025 15:56:11 +0200
Greg KH <[email protected]> • #23479
Re: [RFC PATCH 0/1] compiler_types.h: introduce ASSUME_NONNULL macro for static analysis
Fri, 25 Jul 2025 18:58:53 +0530
Siddh Raman Pant <[email protected]> • #23478
Re: [RFC PATCH 0/1] compiler_types.h: introduce ASSUME_NONNULL macro for static analysis
Fri, 25 Jul 2025 13:42:14 +0100
Raka Gunarto <[email protected]> • #23477
Re: [RFC PATCH 0/1] compiler_types.h: introduce ASSUME_NONNULL macro for static analysis
Fri, 25 Jul 2025 19:18:29 +0700
Mulyadi Santosa <[email protected]> • #23476
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.