We started getting patches for Linux kernel with GPL-4.0 and GPL-6.0 license... Yes! GPL-4.0 and GPL-6.0!
https://lore.kernel.org/all/?q=GPL-4.0
https://lore.kernel.org/all/?q=GPL-6.0-only

Let's guess what was that:

2/ And to quote one bit from @corbet's[1] great #OSSNA25 talk:

""[…] there will be no core development conferences around #Linux and other things in the United States in the foreseeable future. […] this is a real problem […]""

Yes, this is not a formal announcement[2] – but it bears some weight, as Jonathan is well connected and among others sits in the Linux Foundation's Technical Advisory Board (TAB).

[1] https://www.youtube.com/watch?v=hNLBGiwfBSI&t=949s (for context starts a bit earlier; the quoted bit comes about a minute later)

[2] and kinda obvious for some of you

#kernel #LinuxKernel #FLOSS

@brauner Reminds me AMD - Acked-by + 3x SoB + Tested-by for bump in a version string in header.

Open Source Summit Europe 2025 is coming (in August)!

I will speak about two Linux kernel topics on introductory level, so if you want to learn something practical about Devicetree or using static analysis during development in Linux kernel then please come or watch online.

If you want to come and ask questions just find me around the hall or after the talks. We can also organize Unconference Session if there are more Devicetree topics.

1. DTS 101: From Roots To Trees, Aka Devicetree for Beginners
https://sched.co/25Vsl

2. Between Building and Testing Your Linux Driver
https://sched.co/25VoV

@T_X @kernellogger It is already happening. Many ARM64 platforms use ACPI in a sane way. Some, like Qualcomm Snapdragon, uses ACPI in borked way making it completely unusable for Linux. So yes, they adopted something from x86 world and still this makes it no easier for Linux or any other non-qcom OS.

The Wayback Machine managed to capture a Linux Journal article about the Arch Linux distribution's plan to switch to "rye-init" before whatever human intelligence remains there figured out that "rye-init" does not actually exist.

The Linux Journal predates LWN by some years and was, for a long time, the definitive read for Linux users. The Don Marti ( @dmarti ) years were especially noteworthy. It is sad to see where it has ended up now.

https://web.archive.org/web/20250618001301/https://www.linuxjournal.com/content/arch-linux-breaks-new-ground-official-rust-init-system-support-arrives

@axboe Cannot agree more. Also complained and now I just ignore several emails. If sender does not have time to trim the huge email, I don't have time to read it (thus also consider their Rb/Ack).

I noticed slides are not visible on the above page if you are not logged in, so I paste them here:

https://docs.google.com/presentation/d/1GGFM_dbo08XGvkRCdidWwKxcRMB7Z-R-KP6srT-cGGg/edit?usp=sharing

@pdp7 Not all of them were coming with the Samsung-based SoC, I think.

If you are on-site or virtual attendee of Linaro Connect 25 in Lisbon, join me and Google Landing Team today at 5 PM (Lisbon time) to see what is cooking in Samsung Exynos SoC and Google Pixel SoC in the upstream Linux kernel:
https://www.kitefor.events/events/linaro-connect-2025/submissions/307
... or just read the slides linked above! :)

We are doing our utmost to strengthen Ukraine's hand.

We've disbursed the fourth €1 billion tranche of our exceptional Macro-Financial Assistance loans.

This funding supports urgent military needs and will be repaid using proceeds from immobilised Russian state assets in the EU.

With this, the EU strengthens its role as Ukraine’s top donor since the full-scale invasion.

Our support to Ukraine is unwavering. We stay ready to respond swiftly to any further requests.

→ https://europa.eu/!P6YwqY

@ljs My post was of course simplifying or generalizing, because no one will take freshmen for example into maintaining MM or scheduling. What I wanted to say there are many non-complicated driver subsystems which need new maintainers and it is relatively easy to start there. If you have patches already in the kernel and the community recognizes you (vide xz case), then just start reviewing and in no time you will be there.

Assuming of course one knows Git, because that's another problem with young folks these days - they know Github but do not understand Git...

I think many kernel developers - including myself, a long time ago - believe that becoming a Linux kernel maintainer is a difficult process. As if some secret group has to choose you, you need to prove yourself, and then a Masonic lodge will select the best candidates from a huge pool of competition.

That's simply not true. Becoming a Linux kernel maintainer is actually quite easy.

The difficulty lies in staying one.

Every now and then, I notice subsystems that need more maintainers. Do you want to be one?

Of course taking maintainership position and being a true maintainer are a bit different things, but I hope you get the point...

@monsieuricon There was a guy who once called Linux communism, so obviously not that far away. What was the guy's job? Some big American company, right?

Today's misinformation provided by Google Search's "AI Overview" (which cannot be disabled, apparently):
"All EU member states are parties to the Rome Statute, except for Turkey."

(I am not complaining that the AI missed today's withdrawal of Hungary)

@Conan_Kudo @geert Plus, your tags given to cover letters suggest - following your logic - that you only reviewed cover letter and you did not read the patches at all.

@Conan_Kudo Well, your opinion here is contradictory to Linux kernel process. It's clear here:

> By offering my Reviewed-by: tag, I state that:
> (a) I have carried out a technical review of this patch to
> evaluate its appropriateness and readiness for inclusion into
> the mainline kernel.

Nowhere, nowhere in the Linux kernel process is any mention that the tag placement matters and suggesting that it does not only contradicts practice of all reviewers and maintainers but it makes no sense. It just creates noise and additional effort on receivers of your email.

@Conan_Kudo @geert Review under commit msg is the review of everything. Don't ask people to scroll through hundreds of lines just to figure out that they do not need to even scroll! (because b4 will collect the tag, but they had to be sure not to miss any feedback).

As I said, this is is disrespectful to me, this is wasting my time. The way to recover my time is to just ignore such emails.

2024 was a record-breaking year for forest fires in Ukraine.

This is another devastating consequence of Russia’s illegal invasion.

Nearly one million hectares were burnt in the country – more than twice the area burned in the EU in the same period.

The EU is committed to helping Ukrainians strengthen their rescue and fire services by providing them with machinery and protective equipment.

With Ukraine – and its brave firefighters – unflinchingly.

ℹ️ https://europa.eu/!fxW7MD

#EU

Therefore special thanks for Geert and Rob who did trim their replies - they end with Reviewed-by tag. :)