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.

If you're a swiss resident ( or know one ... ) you can get a custom hardware design onto an ASIC for FREE !!!

You get back one chip with your design (and a bunch of others!) and some board to help bring up/testing.

Also, this is "resident", no need to be a student or at uni or anything, you just need a valid Swiss address ...

I know I might be repeating myself here because I mentioned it a few month back but this bear repeating IMHO.

https://swisschips.ethz.ch/news-and-events/tiny-tapeout-submission-form.html

PS: Can I haz boost for reach ?

I just got spam email from PyTorch Foundation / Linux Foundation to my email address used purely in Linux kernel sources and LKML. Email not passed to anyone, not even used as reply/from ever, not used on conferences (so not scan badging) so PyTorch Foundation <pytorchevents@linuxfoundation.org> apparently just grabbed it from kernel sources or kernel mailing list to create database of users for spam mailing.

Such a disappointment @lfeurope @linuxfoundation

Brewing low alcohol beers is tricky, because without good amount of malt for the yeast the taste flattens and becomes boring, watery. If you ever tried low or non-alcohol beers form the store, you know what I am talking about. They are either water or even disgusting fakes of real beer.

Yet my newest brew on https://brewalot.ch/ - the Milkshake New England IPA - gets nice low 3.7% alcohol by volume at 11 *P, beautiful creamy foam, intense fruity smell and low hoppy bitterness with just a pinch of sweetness.

Om nom nom...

I just finished updating Ansible scripts for the new 64x core AWS instance and it is already happy building mainline Linux kernel maintainer trees!

Thanks to #Qualcomm for sponsoring the machine.

In case you missed the announcement:
Both - Google/Gmail and Microsoft/Outlook - probably should be considered as evil and non-cooperative email providers.

Our decentralized workflow met reality of big monopolies caring only about themselves. Basically Google and Microsoft (lack of) response is actively impacting kernel development in a negative way.

I know this post will be ignored, so how about removing Google and Microsoft @LWN Kernel Development Statistics, so they will notice the problem?

Who would think that removing myself from Linux kernel maintainers was such a good feeling. :)

Naaah, I'm a bit joking, just a proper thing to do instead of hoarding maintainers entry and not replying to emails.

First pulls merged to Linux SoC tree as part of new co-maintainership done!
https://web.git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?h=arm/fixes&id=a3b80161fbd06b5dbc0af8f29f8ae58c4aebf0b2

"... I'll be going very, very, very fast. (...) I work for Qualcomm, I'm maintainer, taratatata..."

That's how you don't waste time of the audience during your speech. :)

Tokyo was cool, that was my third visit to Japan and second trip to Tokyo. But beside the city, time spent for Linux Plumbers Conference is as usual priceless. See you next year in Prague!

https://youtu.be/AN_3EA7gv04?si=1eBljSyw57zuzcNt&t=5

I don't want to take all the credits, but FWIW, after pointing out publicly DTBs check compliance warnings for some platforms during my OSS Japan talk, two platforms/archs already received patches to fix several warnings (Loongarch and Aspeed).

It seems I will need to keep repeating this talk :)

https://sched.co/29Foi

Many types of nodes in the Linux kernel explained by Bartosz Golaszewski from Qualcomm at OSS Summit Japan.
#OSSumit

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

This is not a peace plan. It is a proposal that weakens Ukraine and divides America from Europe, preparing the way for a larger war in the future. In the meantime, it benefits unnamed Russian and American investors, at the expense of everyone else.
https://www.theatlantic.com/ideas/2025/11/trumps-war-peace/685024/?gift=hVZeG3M9DnxL4CekrWGK3x5H8-x30wTOq6lDtv0xjW4&utm_source=copy-link&utm_medium=social&utm_campaign=share

$ git describe 
v6.18-rc3
$ git shortlog -s -n --no-merges

Oh! 5th place!

Don’t stop me now

I’m having such a good time

I’m having a ball

Don’t stop me now

SoC maintainership in the Linux kernel (long time ago called arm-soc) is growing into a group of maintainers. Four new people joined @arnd for SoC: Alexandre Belloni, Linus Walleij and me (yay!) as co-maintainers, and @fustini as a reviewer:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b2a578f3127ab9ef80114cef9b20a2b42a8ee77a

Arnd, previously the sole SoC maintainer, handled pull requests and patches from several other sub-maintainers for each SoC sub-architecture (e.g. Qualcomm, NXP) and other driver trees. The SoC tree was one of the busiest, if not the busiest, trees in kernel - visible on @LWN graph: https://lwn.net/Articles/981742/

With this change the load will hopefully spread.