Posts
185
Following
30
Followers
182
Linux Kernel developer and maintainer
🇵🇱 🇪🇺 🇰🇷 🇮🇱 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
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
18
27
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 9 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
krzk

Krzysztof Kozlowski

Edited 10 months ago
Tensor is coming to the next Linux kernel: v6.8!
I just applied last patches for Linux kernel bringing support for the Google Tensor GS101 SoC (derivative of Samsung Exynos):
https://lore.kernel.org/linux-samsung-soc/170249498744.308886.17508790332822828341.b4-ty@linaro.org/T/#u

Commits will hit tomorrow's linux-next and probably next week I will send pull request with them to SoC (@arnd@society.oftrolls.com and Olof) for the next merge window. Good job Peter Griffin and @LinaroLtd :)
3
13
39
krzk

Krzysztof Kozlowski

Reply to @partim@social.tchncs.de
@partim It's the state of the taste of German beer. Quality is not a problem. The taste is...
0
0
1
krzk
repeated
q3k@social.hackerspace.pl

q3k blobcatcoffee

I can finally reveal some research I've been involved with over the past year or so.

We (@redford, @mrtick and I) have reverse engineered the PLC code of NEWAG Impuls EMUs. These trains were locking up for arbitrary reasons after being serviced at third-party workshops. The manufacturer argued that this was because of malpractice by these workshops, and that they should be serviced by them instead of third parti
es.

1/4

6
58
2
krzk

Krzysztof Kozlowski

Reply to @hrw@society.oftrolls.com
@hrw It's there since six years (2017)...
1
0
1
krzk

Krzysztof Kozlowski

Reply to @kernellogger@fosstodon.org
Edited 10 months ago
@kernellogger What was making me sad with such bisection, that after few hours of bisecting, not fully automated so with my personal (not work!) time spent on this, I send a report or even a fix and the maintainer squashes it with original commit. No credits about my work, no Reported-by, nothing for my few hours of personal time which I could spend on eating skittles.
After few of such cases, I stopped entirely reporting linux-next issues hit on my systems, unless the issue is visible for like two weeks. After two weeks, if my CI is still finding the issue, then there is a chance I will be credited with finding it...
1
0
3
krzk

Krzysztof Kozlowski

Reply to @kernellogger@fosstodon.org
@kernellogger Bisecting should be on or start with linux-next. I don't think we should be sending fixes to Linus' somehow faster. Rather people should learn to work on linux-next.
1
0
0
krzk
repeated
oleksandr@natalenko.name

Oleksandr Natalenko, MSE

A reminder about what Muscovy did to us in 1932/33: https://en.wikipedia.org/wiki/Holodomor. Today is the Remembrance Day: https://en.wikipedia.org/wiki/Holodomor_Memorial_Day

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