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

Krzysztof Kozlowski

Edited 7 months 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
krzk

Krzysztof Kozlowski

Reply to @jarkko
@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
krzk

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
krzk
repeated
vbabka

Vlastimil Babka

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

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
krzk

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
krzk

Krzysztof Kozlowski

Reply to @airtower@woem.men
Edited 9 months 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
krzk

Krzysztof Kozlowski

Reply to @airtower@woem.men
@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
krzk

Krzysztof Kozlowski

Reply to @airtower@woem.men
@airtower @pavel `b4 trailers -u -F ....` and don't worry about any orders or forgotten tags.
1
0
2
krzk
repeated
monsieuricon

K. Ryabitsev

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
17
28
krzk

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
krzk

Krzysztof Kozlowski

Reply to @gregkh
@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
krzk

Krzysztof Kozlowski

Reply to @krzk
If you want to get something done, do it yourself.
https://lore.kernel.org/linux-devicetree/170626764360.50413.9381526885560837347.b4-ty@linaro.org/
0
0
5
krzk

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
krzk

Krzysztof Kozlowski

Reply to @Logical_Error@fosstodon.org
@Logical_Error No, but I hope someone someday will add it to clang-format for example.
0
0
1
krzk

Krzysztof Kozlowski

Linux v6.8-rc1 comes with new document describing coding style for DTS (Devicetree sources):
https://www.kernel.org/doc/html/latest/devicetree/bindings/dts-coding-style.html

This marks the end of many unwritten rules, varying between subsystems and maintainers. At least, like with every coding style document, in theory. :)
2
10
22
krzk

Krzysztof Kozlowski

Edited 10 months ago
I was always using git branch --edit-description && git format-patch && git send-email, but now I tried preparing and sending patchset with b4 (b4 prep && b4 send). It works great! It is trivial in use and really solves the workflow. I cannot understand why people still Cc wrong people or are unable to send one patchset properly threaded.

Edit: --edit-cover->--edit-description
3
1
15
krzk

Krzysztof Kozlowski

Reply to @abelvesa
@abelvesa Great news!
0
0
1
krzk

Krzysztof Kozlowski

Reply to @krzk
Phoronix also noticed it:
https://www.phoronix.com/news/Linux-6.8-GS101-SoC-Pixel-6
0
0
1
krzk
repeated
abelvesa

Abel Vesa

FYI, Qualcomm Snapdragon X Elite (X1E80100) now boots to shell with today's -next.

More support is already sent on the list for review:
https://lore.kernel.org/all/?q=X1E80100

And here is a public branch with all support currently available on top of -next:
https://git.codelinaro.org/abel.vesa/linux/-/tree/x1e80100-next
2
7
18
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: