It was just 8 hours for Loongarch contribution and ~2 days for Aspeed (that's also much bigger). Pretty good response time!

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

@corbet We were hanging out in a bar on 39th floor and all felt suddenly we have enough and should call it a day.. :)

You should have named the talk: why Linux kernel is a giraffe?

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

@llvm of course it's off, because it requires careful management how you actually resolve conflict, so only good resolutions are recorded. It's additional, complicating step, thus must be conscious opt in...

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

@hanfi @gregkh Making them public would help people to avoid wasting time in the future by adding the author's email address to ai-slop filters / PLONK. Or adding their domain because sometimes that's representing a company approach.

$ 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.net graph: https://lwn.net/Articles/981742/

With this change the load will hopefully spread.

TWIMC, the "Linus opposes Link: tags with links to the patch submission" is saga over, as Linus wrote:

""[…] I do think that at least if people use the different domain, I won't complain.

I'm still not convinced it's a great idea, but at least it means that the "this is the source of the commit" is clearly separate from the "this is actual background". […]""

https://lore.kernel.org/all/CAHk-%3Dwj5MATvT-FR8qNpXuuBGiJdjY1kRfhtzuyBSpTKR%2B%3DVtw@mail.gmail.com/

#Linux #kernel #LinuxKernel

Not only did a permanent member of the UN security council attack a clearly marked UN humanitarian convoy with FPV Drones, they also proceed to proudly share the footage of their appalling crime on the internet.

https://news.un.org/en/story/2025/10/1166099

@ptesarik @corbet OK, so answering more precisely your question from where does 100 come - from checkpatch. Sometimes people identify checkpatch as the coding style. But few maintainers expressed on mailing list preference of 100.

@ptesarik @corbet Coding style does not need update, it is vague on purpose, because sticking to hard limits is not necessarily good. That's why checkpatch has different limit - people treated its output too literally.
Now some maintainers PREFER 100. I don't know your case here - ask maintainer of that code, which might be that person nitpicking you :)

@conor @gregkh Conor, the last paragraph gives the answer :) http://www.kroah.com/log/blog/2025/10/01/the-only-benchmark-that-matters-is.../

@conor Ha! I got you into LWN :) https://lwn.net/Articles/1039531/

@conor I see now that the stalling-email from vendor partially worked and discouraged community from maintaining the code. Sigh...

@kernellogger @pojntfx @thomasmey yep, sending patch is the first step anyway, regardless of actual status in the maintainers file.

When a vendor wants to control upstreaming process and objects to community-led patches, I’ll just point to this brilliant response from @conor:

It’s only better if <vendor name> submits better quality patches (no evidence for that yet) or submits the patches more promptly than others (which clearly has not happened here), and offers review commentary etc at a higher standard and more frequently than a non-employee maintainer would be able to do (there’s no evidence for that so far either, given you’re trying to stall this patchset). Your claim seems to have no merit as there is no proof that you’d do a better job.

https://lore.kernel.org/all/20250925-jaundice-uneasy-ff8b3b595879@spud/