Posts
210
Following
33
Followers
231
Linux Kernel developer and maintainer
#standwithukraine πŸ‡΅πŸ‡± πŸ‡ͺπŸ‡Ί πŸ‡ΊπŸ‡¦ πŸ‡¨πŸ‡­
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
krzk

Krzysztof Kozlowski

Reply to @conor
@conor Indeed. I refurbished a bit my templates and added more personal-like-phrases. Maybe I need to work on them a bit more... But I am also not a native English speaker, so I don't know how to exactly write a really nice message which will be kind but not exaggerated, so silly. I bet if I write "Please be so kind and use scripts/checkpatch.pl." there will be a person who will feel mocked by this.
1
0
1
krzk

Krzysztof Kozlowski

Reply to @krzk
0
6
9
krzk

Krzysztof Kozlowski

In a perfect world, I would have enough of time and energy to give every patch submitter personalized review, with a touch and nice words. I remember the times when I got one patch per week for my subsystem. Now, with like 600 patches and replies to me per week, I cannot. Reviewers are scarce and day has only 24h.

Unfortunately many issues are the same and do not require me, but ChatGPT. I figured out solution for all such trivialities: review templates.

But now, it's the second time submitter felt offended that I gave too obvious advice for an issue. What to do then? I will not write hundred times "please run checkpatch.pl", it's just waste of my time.
3
0
4
krzk

Krzysztof Kozlowski

Reply to
Edited 1 year ago
@klausman @kernellogger The commit pointed by bisect might not be the real cause. Issue can be triggered by enabling via CONFIG change or just be interacting with something else. What now? Investigate the commit. It might tell you next steps...
Another solution could be to do second bisect - which second commit brought the issue when testing without the first one (then just remember to mark with git bisect good/bad proper commits).
1
1
2
krzk

Krzysztof Kozlowski

Edited 1 year ago
The first pancake is always spoiled? https://lore.kernel.org/linux-devicetree/20230511105006.176979-1-krzysztof.kozlowski@linaro.org/

BTW, above proverb in Polish is a bit more drastic: "Pierwsze koty za pΕ‚oty", so literally: "The first cats over the fence". :)
0
0
6
krzk

Krzysztof Kozlowski

My bedroom has a view on few trees with three young squirrels, jumping, running and foraging every morning. I bet I would not have done any work there... Squirrels are too addictive.
0
0
2
krzk
repeated
monsieuricon

K. Ryabitsev 🍁

This is a regular reminder that Russian military is still dropping high-yield explosives onto Ukrainian homes, killing women and children.

This is not f'n okay.
1
11
16
krzk

Krzysztof Kozlowski

They have taken me by surprise. If I knew, I would put a bit different t-shirt on me.
1
0
3
krzk

Krzysztof Kozlowski

@monsieuricon If few years ago all patch discussions and development processes were moved to Twitter, the problem with such discussions would be solved now. We lost our chance.

RE: https://social.kernel.org/objects/a89443f9-061f-479e-9f89-f6bbdd8b383c
1
0
3
krzk

Krzysztof Kozlowski

Few more points to add to my own notes about handling kernel maintainership: https://lwn.net/Articles/926240/
Now my maintainer howto/reference guide has exactly 4 pages. Not bad. Still shorter than my 23-pages long guide on Swiss taxes...
0
0
2
krzk

Krzysztof Kozlowski

Reply to @krzk
Edited 2 years ago
Not again.... "5.4.5 Daily user sending quota exceeded." So it is a 24-hour moving window.
0
0
0
krzk

Krzysztof Kozlowski

Reply to
@mjg59 @monsieuricon Now it is www.codelinaro.org (at least some parts of it are there already).
0
0
0
krzk

Krzysztof Kozlowski

5.4.5 Daily user sending quota exceeded. - gsmtp

I think Google underestimated my patch creating abilities…

1
1
5
krzk

Krzysztof Kozlowski

Finding email addresses to Cc on patch submission is tricky. If only there was some tool, which can print these and simplify the entire process... Ehh, dreams...
BTW, simple wrapper to send entire patchset to all maintainers (--to-cmd collects addresses per-patch):
https://github.com/krzk/tools/blob/18363551d119c27f3b42cc856cf70ac7d62a78f2/linux/.bash_aliases_linux#L89
0
0
0
krzk

Krzysztof Kozlowski

Reply to @monsieuricon
@monsieuricon @corbet I don't know what was more painful for the brain - "read" his "post" (let's "quote" everything because "why not"?) or try to navigate through the amazing user-interface of his few websites.
0
0
1
krzk

Krzysztof Kozlowski

Meeting in person is cooler than just TOFU. :)
Therefore I will be organizing two PGP key signing parties at Linaro Connect 2023 in London: https://sched.co/1KXDZ and https://sched.co/1KXDq
I hope to see some faces there.
0
0
2
krzk

Krzysztof Kozlowski

Edited 2 years ago
With patches on the list: arm64 exynos/tesla passes dtbs_check. arm exynos has still 10 warnings to go... It would be useful to continue work on: https://lore.kernel.org/all/20221121122932.2493174-1-Naresh.Solanki@9elements.com/ as dependency for pwm-fan :)
0
0
2
krzk

Krzysztof Kozlowski

Reply to @palmer
@palmer @conor dtbs_check produces warnings thus it does not fail entire make command. Warnings are a bit non-standard, so for example for Buildbot I use "^.*\.dtb: " pattern to detect them.
0
0
1
krzk

Krzysztof Kozlowski

Reply to @conor
@conor @palmer Indeed, new things will keep popping up. New bindings might get converted to DT schema, Rob might add more checks/warnings... or new DTS can introduce something. I think the only way to keep near-zero warnings is to keep running dtbs_check on new patches, so you spot new issues fast.
1
0
1
krzk

Krzysztof Kozlowski

Edited 2 years ago

@conor @palmer With just two fixes in kernel RISC-V DTS have full dtbs_check compliance! Good job RISC-V folks!

  DTC_CHK arch/riscv/boot/dts/microchip/mpfs-icicle-kit.dtb
  DTC_CHK arch/riscv/boot/dts/allwinner/sun20i-d1-dongshan-nezha-stu.dtb
  ...

[1] https://lore.kernel.org/linux-devicetree/20230326164751.104789-1-krzysztof.kozlowski@linaro.org/T/#u

[2] https://lore.kernel.org/linux-devicetree/20230326164700.104570-1-krzysztof.kozlowski@linaro.org/T/#u

1
1
2
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: