Live now! @helenleigh from @crowdsupply talks to @oshwassociation about the 2026 Open Hardware Summit coming to #Berlin next May! https://www.youtube.com/watch?v=AY1IItsM_ds #OSHWA #OpenHardware #OSHW

Stephen Rothwell is "stepping down as #Linux-Next maintainer on Jan 16, 2026. Mark Brown [@broonie] has generously volunteered to take up the challenge.":

https://lore.kernel.org/linux-next/20251218180721.20eb878e@canb.auug.org.au/T/#u

To quote: ""It seems a long time since I read Andrew Morton's "I have a dream" email and decided that I could help out there - little did I know what I was heading for.""

Many many thx Stephen for all your really hard work on this over all those years, it helped a tremendous lot!

#LinuxKernel #kernel

apparently gentoo penguins specifically are doing very well despite climate change because they're very adaptable to their local environment. poetic

"yeah, just... let me rebuild my mitochondria with different USE flags"

For those who are curious about tomorrow's Maintainers Summit session on machine-learning tools, Sasha Levin has put together a good summary of the state of the discussion: https://lwn.net/ml/all/aTYmE53i3FJ_lJH2@laps

kernel.org tooling update from @monsieuricon

https://lore.kernel.org/all/20251209-roaring-hidden-alligator-068eea@lemur/

""These are the topics that were touched on at the [#Linux #kernel] maintainer summit […]

# What is the state of tooling?

## b4 development update

[…]

- Seeing lots of adoption and use across subsystem,

[…]

I spent a lot of time on trying to integrate AI into b4 workflows, but with little to show for it in the end due to lackluster results.

[…]

it was certainly ironic that one of the top challenges for us was to try to keep AI crawlers from overwhelming kernel.org infrastructure.

[…]

## Are we finally moving away from patches sent over email?

[…]

With lore and public-inbox, we *are* in the process of moving away from
relying on the increasingly unreliable SMTP layer.

[…]

## Work on "local lore"

[…]

## Other tools

### Bugzilla

It may be time to kill bugzilla:

[…]""

#LinuxKernel

Recordings from last week's @linuxplumbersconf 2025 are now available.🥳

You have two options to find the ones you might be interested in:

* Look through this YouTube-Playlist (https://www.youtube.com/playlist?list=PLVsQ_xZBEyN3-ZbrEgTiCpm1-Sg_ihLVF)

* Find and open interesting talks via the Schedule Overview (https://lpc.events/event/19/timetable/#all) or the Detailed Schedule (https://lpc.events/event/19/timetable/?view=lpc), as the individual talk descriptions link to the videos. And as a bonus, they besides the summary usually contain links to the slides shown, too.

#Linux #kernel #LinuxPlumbersConference #LinuxPlumbersConference2025 #eBPF #BPF

Wow, day 3 of @linuxplumbersconf has arrived quickly! Thanks to everyone involved in another great LPC 🗼🐧❤️

#Linux 6.18.y is now officially a longterm kernel series, as can be seen here:

https://www.kernel.org/category/releases.html

Projected EOL is Dec, 2027 (two years from now) – just like the 6.1.y series. All the other series as of now are scheduled for EOL in about one year from now – and 5.4.y just was EOLed, as planned (see https://social.kernel.org/objects/da258e20-22b9-4805-a9e5-5a506eb2bf91 and https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=0f52d79a5053091c95a269ff6fddbece27ea1d64 ).

Note, the kernel.org front page for the next ~two months (e.g. until 6.19 is out) will keep listing 6.18.y as latest stable series, as it might break peoples scripts to call it longterm there:

https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=b9ea3472ee1d973f4c27d075c7e4445afa7ade89

The @lwn article "The current state of #Linux architecture support" is now freely available:

https://lwn.net/Articles/1045363/

""There have been several recent announcements about Linux distributions changing the list of architectures they support, or adjusting how they build binaries for some versions of those architectures. […] Linux supports a large number of architectures, and it's not always clear where or by whom they are used. With increasing concerns about diminishing support for legacy architectures, it's a good time to look at the overall state of architecture support on Linux.

The 6.17 #kernel supports 21 different architectures […]""

#LinuxKernel

Wow! I only just realized that there is a 'nested' thread view on lore. I've been using the default 'flat' forever and randomly just clicked on 'nested'. So much better! :) https://lore.kernel.org/linux-riscv/37cfd941-f51d-44d8-8283-389ea8d53e69@codethink.co.uk/t/#mf12d1cd651f187f2558c14580056003899fe4876

Please donate to @conservancy if you can! They're doing great work keeping free software available to everyone.

https://sfconservancy.org/news/2025/nov/26/2025-fundraiser-launched-with-largest-match-yet/

When a kernel commit starts with "In A.D. 1582 Pope Gregory XIII found that ..." you know you're in for a ride:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f076ef44a44d02ed91543f820c14c2c7dff53716
tl;dr: Rockchip decided November should have 31 days...

If you ever wondered where do we stand in Linux kernel with DTS validation (dtbs_check) of various platforms, which architectures are fully compliant and where we see nice progress, please join my session on 9th of December in Tokyo during Open Source Summit Japan 2025: Status of DTS Validation in Linux Kernel
https://sched.co/29Foi

I will also have a shortened version at the Linux Plumbers Conference, just a few days after.

#OSSummit #OSSJapan2025 #LinuxPlumbers

#Linux #kernel explorer

https://reverser.dev/linux-kernel-explorer

""Chapter 1 — Understanding Linux Kernel Before Code

The kernel isn't a process—it's the system. It serves user processes, reacts to context, and enforces separation and control.

The Kernel Is Not a Process: It's the always-present authority bridging hardware and software.
Serving the Process: Orchestrates syscalls, interrupts, and scheduling to keep user tasks running.
System of Layers: Virtual, mapped, isolated, and controlled—structure at runtime.

📚 Study Files
init/main.c […]""

The Input Stack on Linux – An End-To-End Architecture Overview

https://venam.net/blog/unix/2025/11/27/input_devices_linux.html

Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:

#Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
[…]
Exposed layer (middle)
[…]
User-space handling:
[…]
The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything else

We’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""

#LinuxKernel #evdev

@ljs @ljs "This US experiment with 'what if we elect people with IQs much closer to the national average' is going brilliantly overall".... Ouch, but you're not wrong 🤣😨☠️

How big is lore.kernel.org? I counted 17,154,017 unique message-ids.

I think that's roughly how many emails @gregkh replies to every day.

The Life of a Packet in the #LinuxKernel

https://www.0xkato.xyz/life-of-a-packet-in-the-linux-kernel/

0xkato writes: ""A practical tour from write() to recv()

You run curl http://example.com and now you have some HTML in your terminal but what actually happened? Linux walks your bytes through a small set of well‑defined steps: pick a path, learn a neighbor’s MAC address, queue the packet, ask the NIC to send it, then reverse that on the other side.

This post tries to explain that path as simply as I can. If you’ve used #Linux, run curl, or poked at ip addr before, you’re qualified to read this. No deep #kernel background needed. […]""

If you had odd failures (like compilers or package manager aborting[1]) with #Linux 6.18-rc6 (and mainline snapshots a few days older and younger), then switch to latest mainline now, as it since about 12h contains a fix for the problem:

https://git.kernel.org/torvalds/c/5bebe8de19264946d398ead4e6c20c229454a552

[1] https://lore.kernel.org/lkml/20251117082023.90176-1-00107082@163.com/

#kernel #LinuxKernel

The company that provides LWN's health insurance just sent me a helpful thing about how a very small number of employees, those with expensive chronic conditions, drive the bulk of insurance claim costs.

We are far too small to have such a plan, but bigger companies pay their claim costs. As these companies lay people off, surely they wouldn't target the few employees that, we are being told, are the reason their health-insurance costs are going through the ceiling. The ones who most need the insurance they would stand to lose.

Right?

https://www.anthem.com/employer/the-benefits-guide/the-high-cost-reality-what-2024-trends-mean-for-self-funded-employers