Posts
229
Following
38
Followers
266
Linux Kernel developer and maintainer
#standwithukraine ๐Ÿ‡ต๐Ÿ‡ฑ ๐Ÿ‡ช๐Ÿ‡บ ๐Ÿ‡บ๐Ÿ‡ฆ ๐Ÿ‡จ๐Ÿ‡ญ
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social

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

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

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

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

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

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

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

Krzysztof Kozlowski

Edited 2 years 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

Krzysztof Kozlowski

Edited 2 years 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

Krzysztof Kozlowski

Edited 2 years 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

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

Krzysztof Kozlowski

Edited 2 years 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

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

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

Krzysztof Kozlowski

Edited 2 years 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

Krzysztof Kozlowski

Edited 2 years ago

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

0
3
8

Krzysztof Kozlowski

Go Beavers! I mean, the true beavers, the greatest ecosystem engineers, which are vital in bringing diversity, richness, and healing degraded landscapes. โ€œBeaver settlements triple in 15 years in Switzerlandโ€ https://www.swissinfo.ch/eng/beavers-increase-threefold-in-15-years-in-switzerland/48657934

If you want to learn more, why beavers are important, I recommend Andrew Millisonโ€™s: https://youtu.be/43bmtqKDhBE

0
1
3

Krzysztof Kozlowski

With v6.5-rc1 merge window, my remaining few fixes for Samsung Exynos SoC dtbs_check compliance were merged. This means that with v6.5-rc1 all ARM and ARM64 Samsung Exynos SoC Devicetree sources (DTS) pass in-kernel Devicetree bindings compliance tests. I can finally enable a builder testing mainline DTS for this:
https://krzk.eu/#/builders/92
https://krzk.eu/#/builders/91
https://github.com/krzk/tools/commit/743f694cfe4d18dd5f92728967aa762edd59c84e

P.S. The ARM64 Exynos DTS was actually compliant since v6.3-rc1, so that part I could have enabled earlier.
0
5
14

Krzysztof Kozlowski

Edited 2 years ago
Is fixing the same issue over and over again, and expecting it to be fixed, also definition of insanity? Or just Groundhog Day? Or Whack-A-Mole game?
https://lore.kernel.org/linux-devicetree/20230711063011.16222-1-krzysztof.kozlowski@linaro.org/T/#u
https://lore.kernel.org/all/20230410175232.22317-1-krzysztof.kozlowski@linaro.org/
1
0
3

Krzysztof Kozlowski

Hey @linuxfoundation
Do you plan to upload more photos of EOSS 2023? I see pictures from only the first two days of EOSS, not even complete two days... Other days are not uploaded at all. As you can see in the link below, count stays at 150 pictures is since last Thursday:
https://www.flickr.com/photos/linuxfoundation/albums/72177720308904909/page2
#eoss2023 #elce2023 #EmbeddedOSSummit
0
0
2
Show older