If someone asked me 5 years ago, I would not believe that I could produce such a statement about major SoC vendor:
https://lore.kernel.org/all/2509536d-cdec-448d-bf20-80d2b3d6728a@kernel.org/

Qualcomm and Linaro were upstreaming before significant amount of code to the Linux kernel for supporting their SoCs , but around 2021-2022 things changed significantly. Just to recap major milestones of:

2022 November: One day after public announcement of new Snapdragon 8 Gen 2 flagship SoC (SM8550), Qualcomm Landing Team in Linaro posted basic support for it:
https://lore.kernel.org/all/20221116103146.2556846-1-abel.vesa@linaro.org/

2023 October: One day after public announcement of next flagship Snapdragon 8 Gen 3 (SM8650), same team posts almost full (not basic!) support for it:
https://lore.kernel.org/all/20231025-topic-sm8650-upstream-dt-v1-0-a821712af62f@linaro.org/

2024 October: One day after public announcement of next flagship Snapdragon 8 Elite (SM8750), Linaro and Qualcomm team posts comprehensive support for it:
https://lore.kernel.org/all/20241021232114.2636083-1-quic_molvera@quicinc.com/

2025 September: Same day of public announcement of Snapdragon 8 Elite Gen 5 (Kaanapali), Qualcomm posts comprehensive support for it:
https://lore.kernel.org/all/20250924-knp-dts-v1-0-3fdbc4b9e1b1@oss.qualcomm.com/

Now things changed:

2026 March and from now on: Qualcomm posts patches for unannounced SoC yet, getting way ahead, for example:
Hawi: https://lore.kernel.org/all/20260330-clk-hawi-v1-0-c2a663e1d35b@oss.qualcomm.com/
Maili: https://lore.kernel.org/all/20260522-maili-pinctrl-v1-0-0a6636f5c277@oss.qualcomm.com/
(I don't know which models are these, what I know is they are not yet announced)

And this list above does not include upstreaming of many other models from different segments.

People really missed how big transformation Qualcomm did in upstream Linux kernel involvement.

their real worry is that the Ukrainians will find a way to improve the Patriot and then produce them at scale faster and for much less money than what the existing production lines in the U.S. could do

Yes, read this again.

Linux kernel Devicetree sources:

With my recent patches entire ARM, arm64 (except Broadcom Stingray and Apple) and RISC-V DTS files pass the dt-check-style linter, in default relaxed mode, so any new DTS is expected to not introduce new warnings.

IOW, in your contributions be sure that new DTS is dt-check-style warning-free.

I am working on fixing false positives for the strict mode and have some successes, but that is not yet ready.

Linux needs more maintainers. Myself must be overloaded, and heading for a burn-out:
$ git log --oneline MAINTAINERS | grep -i myself | head -3
51f449308506269e MAINTAINERS: make myself the maintainer of the Qualcomm QCE driver
12933e2bc5e07e15 MAINTAINERS: dmaengine/ti: Remove myself and add Vignesh as maintainer
4452b868d669fbf6 MAINTAINERS: Add myself as SCD30 maintainer
$ git log --oneline MAINTAINERS | grep -i myself | wc -l
348

[$] Development statistics for the 7.1 kernel

Linus Torvalds released the 7.1 kernel as expected on June 14. This development cycle brought in a lot of new features — and a lot of new developers as well. The time has come for [...]

https://lwn.net/Articles/1077425/ #LWN #Linux #kernel #SUSE #RedHat #ArchLinux #Rust #Git #io_uring

This is the first time I'm posting anything here but I figured this may be the right audience.

I've never run into something like this and I don't quite know what to make of it. I'm the author and maintainer of libgpiod. The official git repository is the one at kernel.org[1]. There's also a github mirror[2] as well as a documentation page[3] at readthedocs that I maintain.

I noticed (purely by chance) that there's a new website at libgpiod.com that's been created recently. I have nothing to do with it. It's clearly AI-generated but it redirects to my github. It's a 2 month old domain, anonymized registrar, protected by Cloudflare and NeoProtect and a Swedish host behind that.

Clearly someone went to great lengths to stay anonymous. I'm afraid of falling victim to some new elaborate supply chain attack. What should I do about it (if anything)? Has anyone else experienced something similar?

[1] https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/
[2] https://github.com/brgl/libgpiod
[3] https://libgpiod.readthedocs.io/

In a week, I will be presenting on the Open Source Summit India 2026 in Mumbai. I have two talks:

1. Semi-BoF titled "Guide to Becoming a Linux Kernel Maintainer" (https://sched.co/2KNFb) where I would be happy to have bigger discussion. I don't have many slides on that, so please come to the session and participate in the talk.

2. My standard Devicetree speech for beginners (DTS101, https://sched.co/2KNF4).

If you are going to attend OSS India, please come say hi. If you are already a Linux kernel maintainer, I can also sign GPG keys (I need printed `gpg --fingerprint` though!).

This one shows just people responding, deliberately not patch submissions (because Greg's and Sasha's stable patchbombs just dwarf everyone).

So, these are the people who are hitting "Reply All", and it's not even the full picture, because it only includes the LKML.

Embedded Recipes 2026 has officially kicked off!
It's fantastic to see so many talented engineers and developers gathered in one place to share knowledge, exchange ideas, and push the boundaries of embedded systems. Looking forward to two days of insightful talks and meaningful connections.

[ANNOUNCEMENT / CFP] LPC 2026 Devicetree MC CFP

There will be a dedicated Devicetree Microconference on Linux Plumbers
2026 in October in Prague. Call For Papers is currently open.

https://lpc.events/event/20/contributions/2317/

Topics suggested for discussion are mentioned in "Ongoing problems" in
session description (link above), but of course are not limited to
these. Topics should obviously follow standard Microconference
expectation, that is to be discussion oriented.

Allocated time per slot will be between 15 to 30 minutes (20 minutes
last year).

Proposals can be submitted here:
https://lpc.events/event/20/abstracts/

Please remember to choose "Devicetree MC" as the track.

AI slop in Open Source is not only about receiving poor quality LLM generated junk patches. It is also about receiving replies generated by LLM to reviewer's comments. Such replies are overly long, overly polite, unnecessarily "You are right, <here goes very long explanation>".

Reading an LLM generated answer to my review comment on the mailing list is a waste of my time.

If you are a contributor to an open source project, understand that maintainer has absolutely ZERO interest in talking to your LLM through you.

Drodzy Uczestnicy!

Sesja Linuksowa już trwa!
Jeżeli nie możecie pojawić się na miejscu, zapraszamy na streama z konferencji: https://www.youtube.com/watch?v=ZeS7QtMYXyw

Miłej zabawy!

In two weeks, I hope to tell a few weird things how Linux kernel is being developed during my speech "Peculiarities of Linux Kernel Development" at the "Sesja Linuksowa" conference in Wrocław, Poland. That will be my first speech in my home country. :)

Detailed schedule is on https://sesja.linuksowa.pl/

If you around, come say hi, I will stay at the conference through most of the Saturday.

P.S. The talk will be in English.

My speech proposals for OSS India 16-17 June were accepted (yay!) but the conference organizers weirdly ask to have slides ready TWO months before:
"Slide Submission Deadline: Monday, 15 April"
https://events.linuxfoundation.org/open-source-summit-india/program/speaker-guide/#welcome

Yeah, right. Dream on. I can send you the title slide on 15th of April.

Continuing PyTorch / Linux Foundation database of harvested emails and sending advertisements to them - https://social.kernel.org/notice/B3bhz39OUEdNndylVI

Linux Foundation apologized for "internal marketing operations error" and that "Your email address, along with those of other kernel maintainers, was included in a dataset from a third-party data provider that was improperly imported into our marketing systems without consent verification."

No name for 3rd party provider was given, so GDPR cannot follow to that provider, though...

Linux Foundation also stated they were executing a "permanent deletion". That was 5th of March.

However today I got message from other kernel maintainer, who just got spam/advertisement from the PyTorch Foundation. So saga keeps going.

Maybe they removed only my address from the harvested list. :)

New release: neard v0.20, the user-space counterpart of Linux NFC stack

The release includes a few minor fixes.

Source code release:
https://web.git.kernel.org/pub/scm/network/nfc/neard.git/tag/?h=v0.20
https://web.git.kernel.org/pub/scm/network/nfc/neard.git/snapshot/neard-0.20.tar.gz

I should have released it much earlier, though. I think this release thanks to Mark Greer finally dumps Python 2 dependency - last blocker of packaging for Debian. Anyone would like to revive the Debian package?

Since a year we got some contributions for converting Devicetree bindings from TXT to DT schema as part of some sort mentorship programs (e.g. GSoC). This is great although leads to some misunderstandings in that work, considering mentorships did not ask DT maintainers about some sort of guidance. To clarify:

1. Please convert bindings which have active DTS users. First choose bindings with DTS built by arm64 defconfig, then next choice by arm multi_v7 defconfig. Then any other ARM or different architecture DTS.

2. Be sure dt_binding_check (including yamllint) and checkpatch pass without any warnings. See writing-schema.rst document.

3. Be sure that all DTS files using this binding pass dtbs_check validation. If this means binding needs to be adapted during conversion, mention briefly in commit message changes done comparing to pure TXT->DT schema conversion. Sometimes DTS has to be fixed. Sometimes both - DTS and binding - must be changed, because actual ABI (Linux drivers) is different.

4. Do not send conversions of TXT bindings in staging, because these need to follow standard review process. Bindings in staging are not considered accepted/reviewed DT ABI.

5. Don't ever send output of LLM microslop tools. It's pointless and brings no benefits to the community. Rob already converted all TXT bindings with LLM, so why you doing this again would be beneficial to anyone?

6. Read also Rob's expectations and hints:
https://lore.kernel.org/linux-devicetree/CAL_JsqJp133hGSkja9tabtsE9D7MSA9JErVkmkcy91piHMgfwg@mail.gmail.com/

This is an updated guideline from 2025 https://social.kernel.org/notice/Ai9hYRUKo8suzX3zNY .

The accuracy of information added to Jira tasks by employees is inversely proportional to amount of detailed information being asked by managers to put there. So called overeager manager law, aka krzk's principle.

Review on mailing list:

Copyright (C) 2026 Variscite Ltd. AI bot review and may be useless.

Copyright year is 2026, which is in the future. Should be 2024 or current year.

Great, now everyone will get to read useless AI agent reviews.

https://lore.kernel.org/all/20260303210131.2966214-8-Frank.Li@nxp.com/

Every Google Maps review score in Germany is fake. Believe me.

Well, it does not have to be truly fake, but because of lack of negative reviews, what you have is score built only on positive experiences + advertisements.

Two of my honest, not defaming, describing real experience, negative (1-star and 2-star) reviews of two places in Munich from some visit in 2023 got removed by "defamation" process. It's the process where you as customer can do nothing, your review will be gone and Google will completely ignore your appeals.

I can assume that many or even most of negative reviews older than 2 years will be just removed by Google using this German defamation process, leaving only positive ones.

In the same time these places have many 5-star review written by agencies, posting similar AI-generated ludicrously exaggerated poetry, which obviously no one will ever drop, because they are not a defamation.

So please remember - Google Maps in Germany is full of crap reviews.