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

Jonathan Corbet

So they made a movie about my dad ...

https://fullcirclefilm.co/

...and about a crazy kid named Trevor Kennison and how both recovered their lives after a devastating injury. I've seen it, it's definitely worth a watch. The site lists a lot of upcoming screenings (all just in North America, alas).
0
6
16
krzk

Krzysztof Kozlowski

What a pleasant surprise - I am going to Plumbers! My talk about useful tool-set for fresh Linux kernel maintainers was accepted for this years Linux Plumbers Conference:
https://lpc.events/event/17/contributions/1498/
The cool part is that I will speak very early - on the second slot of the first day.
0
1
11
krzk

Krzysztof Kozlowski

Edited 1 year ago
For a year I have been keeping a branch on top of linux-next with all the cleanups and fixes for Qualcomm SoCs Devicetree sources. Goal is to pass DT schema validation someday (just like Samsung does). I update and rebase the branch frequently. I also add new patches to fix existing warnings. Unfortunately, the branch actually never gets smaller: I always have around 120-200 patches on top of linux-next. Always. Now, after rebasing on next-20230913 it is ~150 patches. Still 150 patches just cannot get applied...

If anyone tells you "Linux kernel development goes too fast", he is wrong. It's too slow. For one year I was able to create fixes much faster than people were applying then.

Branch is here if anyone wants to avoid duplicating work/effort:
https://github.com/krzk/linux/tree/pending/dt-bindings-qcom-new-and-fixes-for-warnings-linux-next
0
0
3
krzk

Krzysztof Kozlowski

Syzkaller now creates nice monthly reports reminding what could be fixed. Anyone bored enough or having enough of spare time to fix these NFC issues (having repro!)?
https://lore.kernel.org/all/0000000000008253550604ac4d36@google.com/
0
1
2
krzk

Krzysztof Kozlowski

Trimmed diffstat of v6.6-rc1 pull request ARM SoC changes from @arnd - the most active platforms for v6.6:

18.9% arch/arm64/boot/dts/qcom/
0.6% arch/arm/boot/dts/qcom/
1.0% drivers/soc/qcom/
...
9.6% arch/arm64/boot/dts/freescale/
3.6% arch/arm/boot/dts/nxp/imx/
0.7% arch/arm/boot/dts/nxp/ls/
0.9% arch/arm/boot/dts/nxp/mxs/
...
8.1% arch/arm/boot/dts/aspeed/
...
8.2% arch/arm64/boot/dts/ti/
0.5% arch/arm/boot/dts/ti/
...
6.6% arch/arm64/boot/dts/nvidia/
...
6.3% arch/arm64/boot/dts/rockchip/

Way to go Qualcomm SoC community!
Source: https://lore.kernel.org/all/4f60d13e-f060-491a-88c7-6f25323a48f8@app.fastmail.com/
0
3
5
krzk

Krzysztof Kozlowski

Edited 1 year ago
Corporate rules going mad: After replying to Nuvoton patches, I received now automated Out-of-office reply with "confidentiality" clause: "The privileged confidential information contained in this email is intended for use only". This is Out-of-office auto-reply, not confidential message. Get your silly systems together people...
0
0
1
krzk

Krzysztof Kozlowski

@linuxplumbersconf Hey Linux Plumbers! What is the point of the your mastodon account if you do not interact and do not respond here to any questions?
2
0
2
krzk

Krzysztof Kozlowski

When review happens too fast:
"You replied within the same minute of me posting that patch, which is the fastest review I've had to date on an upstream kernel list. Before we continue, please verify:

[ ] I am not a robot"

From Brian Masney: https://lore.kernel.org/all/ZN5KIlI+RDu92jsi@brian-x1/
0
1
9
krzk

Krzysztof Kozlowski

@kwilczynski The sales trick is neat! Let's suck out of maintainers even money, not only their time!

RE: https://fosstodon.org/users/kwilczynski/statuses/110864258072128850
0
0
1
krzk

Krzysztof Kozlowski

@kwilczynski No vendors stepped in to provide hardware for testing by Linux maintainers? No surprise...

There is somehow quite a big disconnection between big corporations making millions of products and Linux, and us - people actually developing Linux. Knowing enormous expenses in the marketing of big corporations, one could imagine what it is to donate a few boards to real Linux maintainers, right?

Nope.

I had a similar problem some time ago - till I gave up - with Samsung. I am the maintainer of Samsung SoC in Linux kernel, but all the boards were either purchased by me, donated by a friend in Germany, donated by a friend from Google or donated unofficially by a few good folks from Samsung R&D Poland.
When I asked Samsung Open-source or Samsung LSI (the one making SoCs I maintain) the answer was either silence or "no boards". One more board might now come from Samsung thanks to a project between Linaro and Samsung, but it is an exception.

And that makes me every time very rough in reviewing big-corporations code. Sorry guys, you do not play fair.
1
1
3
krzk

Krzysztof Kozlowski

@hyeyoo Cass I remember - water, sorry :). Terra - I did not try. From all the industrial companies only Klaud had a bit of taste. Beer revolution moves slowly :) but I remember few places with some nice choice, e.g. Cocky Pub.

RE: https://social.kernel.org/objects/fee182c1-7174-4348-90bb-f7f9cf196c39
0
0
1
krzk

Krzysztof Kozlowski

Edited 1 year ago
@T_X Not everyone has some spare money for engineers full time salary in non-profit way... They already have such updated kernels, just on their website, not on kernel.org. Your suggestion would benefit community, but what would be the benefit of this to Canonical?

RE: https://chaos.social/users/T_X/statuses/110847464823963952
2
0
4
krzk

Krzysztof Kozlowski

Edited 1 year ago
First Linux Kernel beer in Zurich organized with @Andi was a success - many beers were drunk. :) Stay in touch for more events!
0
0
8
krzk

Krzysztof Kozlowski

Edited 1 year ago

Once you see it, you cannot unsee:

+#ifndef MSM_VIDC_EMPTY_BRACE
+#define MSM_VIDC_EMPTY_BRACE {},
+#endif
...
+static const struct of_device_id msm_vidc_dt_match[] = {
+	{.compatible = "..."},
...
+	MSM_VIDC_EMPTY_BRACE
+};

We are back to the past! To year 2000-something to be precise. This reminds me ARM Mali Linux kernel drivers which were using MALI_SUCCESS instead of return 0.

1
0
5
krzk

Krzysztof Kozlowski

Anyone around Zurich up for a beer on 3rd of August with me and @andi?

RE: https://social.kernel.org/objects/ddc0aef7-fe3b-493a-8523-af4ad17ee4e0
0
0
1
krzk

Krzysztof Kozlowski

Edited 1 year ago
Anyone from Samsung has some inputs on Qualcomm minidump solution? Without any feedback we'll assume Samsung is fine with Qualcomm's choices. Thread:
https://lore.kernel.org/all/0199db00-1b1d-0c63-58ff-03efae02cb21@quicinc.com/

#samsung #samsunglsi #exynos
0
0
2
krzk
repeated
monsieuricon

K. Ryabitsev

Just a regular reminder that the war isn't over, civilians are still murdered in their homes by cruise missiles, and war crimes are committed daily by the invasion force occupying the sovereign territory of Ukraine.

Until the 1991 borders are restored, all war criminals are in jail, and reparations are paid off, I will continue to #StandWithUkraine, and so should you.
1
8
28
krzk

Krzysztof Kozlowski

Oh, the amazing construction of silosed Business Units of big corporations. When interacting with Open Source communities, one team in some Business Unit of that company cannot learn from the past experience of some other team, because they are silosed. Separate. Thus this team makes the same mistakes other teams already did. However Open Source community sees it differently - one company sending contributions with the same mistakes. It is always okay to make a mistake, but making the same mistake again and again, is a bit waste of our time.
1
0
1
krzk

Krzysztof Kozlowski

Edited 1 year ago
Trying to sell something on Facebook marketplace: 99% of interested people are scammers. I found a pervert joy in playing with them, requiring rather small effort from my side and ending in some amusement. This one gave up just after two days off wasting his time.
0
0
1
krzk

Krzysztof Kozlowski

Edited 1 year ago

Cleanup of inactive maintainer entries is coming :) - docs: maintainer: document expectations of small time maintainers

0
3
8
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: