Posts
162
Following
29
Followers
146
Linux Kernel developer and maintainer
🇵🇱 🇪🇺 🇰🇷 🇮🇱 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social

Krzysztof Kozlowski

Just a reminder: only a week to hear me babbling about Linux kernel DTS validation and shared reset GPIOs on Embedded Open Source Summit/OSSNA 2024. Don't miss it and come to say hi!
EOSS: https://sched.co/1aBEf
OSSNA: https://sched.co/1aPvr
0
3
5
@kernellogger Oh, interesting, I did not know about the "delay" argument. The no-stable is so far a bit per subsystem. Some of them, like I think netdev, rely on marking things explicitly cc-stable. Most don't care thus anything with Fixes tag is picked up.
1
0
0
@kernellogger That's reasonable classification. Some kernel users also need some time to take new kernel release, thus actual tests and results might be coming 1-2 years after a release.
0
0
1
@kernellogger Linus expressed few times that if something was broken for very long time, was not working for long time, it should not be treated as urgent/important fix thus should not go to current RC cycle. Instead, should go via normal development branch, so for the next merge window. I know that stable folks have different point of view - they also expressed it.

I personally follow exactly the same approach in handling fixes: if something was broken for long time, it is regular bugfix thus goes to "for-next" branch, not "fixes / for-linus / for-current-rc".

Now, if a regression was unnoticed for 8 years, it kinda fits above criteria.
1
0
3
@sam_ravnborg so far lore got my emails, but that does not mean they will pass spam filters on receiver's side.
0
0
0
@sam_ravnborg I use b4, but maybe you meant b4 relay? I used kernel.org, but I wonder how emails from other domain will be treated (From is @linaro, smtp is mail.kernel.org).
3
0
0

Krzysztof Kozlowski

Edited 19 days ago

Hey, Google, not again! How am I supposed to send my patches?

smtplib.SMTPDataError: 5.4.5 Daily user sending limit exceeded.

2
0
1
@jarkko It's not that bad... I still find it more useful than: "Where do you see yourself in five years?" (and responding: "Hm, working and earning currency in exchange of performing the work"). Or: "Why do you want to work for us?" To receive currency in exchange of performing services. "Who is your idol and why?" Cats, because they don't have to come to such crappy interviews...
1
0
2

Krzysztof Kozlowski

Preparing speeches for conferences was always rather difficult for me. Went slow, somehow painful. But now I have wonderful data, which I am going to present, and it is just pleasure to write the slides slowly reaching the conclusion I want to share!
https://sched.co/1aBEf
0
1
3

Vlastimil Babka

Thanks Pope for making me angry enough! Don't like your fundraising campaign style, but it worked! #DronesNotWhiteFlags
2
2
14

Krzysztof Kozlowski

If you ever wondered how Linux kernel can handle multiple devices sharing the same GPIO, you got one more reason to go to Seattle this April:
https://sched.co/1aPvr

My second talk got accepted to LinuxCon / Open Source Summit NA 2024.
0
1
8

Krzysztof Kozlowski

About current EU and Polish farmer protests, let's digest this meme. Left pic is from Poland, where Polish farmers protest with Soviet Union flag and banner saying:
"Puting clean up mess with Ukraine, Brussels and our government."

Right picture is from Ukraine (quite old btw)...
0
0
1

Krzysztof Kozlowski

Edited 1 month ago
@airtower @pavel These are documents describing rules and the contribution process. These are not tutorials and they have never been such. They do not mention tools at all, e.g. people submit/manage patchsets with quilt, git or whatever. That's why there is no place for b4 there. You can use any tools...

Tutorials are for example:
https://people.kernel.org/monsieuricon/sending-a-kernel-patch-with-b4-part-1
https://www.youtube.com/watch?v=QBR06ml2YLQ&ab_channel=KonstantinRyabitsev
https://www.marcusfolkesson.se/blog/use-b4-for-kernel-contributions/
and others presented on conferences or on blogs...
0
0
0
@airtower @pavel b4 simplifies entire workflow with Linux contributions and it also makes sure that in certain aspects it is correct, e.g. CC-ing proper people, applying tags, providing versioning. We keep repeating it all the time, that all new contributors should use it. I think also all new tutorials rely on b4...
1
0
0
@airtower @pavel `b4 trailers -u -F ....` and don't worry about any orders or forgotten tags.
1
0
2
In the face of hundreds of thousands murdered in Ukraine, and millions more displaced fleeing Russian military aggression, it is hard to focus on the death of one man. And yet, Navalny meant a lot to the Russian opposition and his death is just another proof that Putin's regime is criminal to the core and cannot be dealt with by appeasement or backroom deals. Ukrainians are the only force actively fighting the Kremlin mafia regime and we should continue to give them all they need to achieve a swift and decisive victory.
0
20
27

Krzysztof Kozlowski

Is DT schema validation of DTS boards helpful or not? Get ready to find it out during my talk on EOSS 2024 conference in April:
https://sched.co/1aBEf
See you in Seattle!
0
3
9
@gregkh I love the remark: "Because of this, the CVE assignment team is overly cautious and assign CVE numbers to any bugfix that they identify."! I hope my CV will be nice and beautiful with all my stable-target commits being translated into CVEs :)
1
0
3

Krzysztof Kozlowski

10 years ago I sent a patch to fix one compatible in one Marvell SoC board:
https://lore.kernel.org/linux-devicetree/1410884282-18041-1-git-send-email-k.kozlowski@samsung.com/
Obvious fix but was never picked up.

In 2021 Sebastian tried to fix it:
https://lore.kernel.org/linux-devicetree/20210412230320.382885-2-sebastian.reichel@collabora.com/

Now in 2023 and 2024, Duje tries the same:
https://lore.kernel.org/linux-devicetree/20240125-brownstone-typo-fix-v2-1-45bc48a0c81c@skole.hr/

Will it succeed?
2
1
8
Show older