Posts
252
Following
37
Followers
277
Linux Kernel developer and maintainer
#standwithukraine 🇵🇱 🇪🇺 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
krzk

Krzysztof Kozlowski

Reply to @ptesarik@infosec.exchange
Edited 5 days ago
@ptesarik @corbet OK, so answering more precisely your question from where does 100 come - from checkpatch. Sometimes people identify checkpatch as the coding style. But few maintainers expressed on mailing list preference of 100.
0
0
2
krzk

Krzysztof Kozlowski

Reply to @ptesarik@infosec.exchange
@ptesarik @corbet Coding style does not need update, it is vague on purpose, because sticking to hard limits is not necessarily good. That's why checkpatch has different limit - people treated its output too literally.
Now some maintainers PREFER 100. I don't know your case here - ask maintainer of that code, which might be that person nitpicking you :)
1
0
1
krzk

Krzysztof Kozlowski

Reply to @conor
@conor @gregkh Conor, the last paragraph gives the answer :) http://www.kroah.com/log/blog/2025/10/01/the-only-benchmark-that-matters-is.../
0
0
3
krzk

Krzysztof Kozlowski

Reply to @conor
@conor Ha! I got you into LWN :) https://lwn.net/Articles/1039531/
0
0
1
krzk

Krzysztof Kozlowski

Reply to @conor
@conor I see now that the stalling-email from vendor partially worked and discouraged community from maintaining the code. Sigh...
1
0
1
krzk

Krzysztof Kozlowski

Reply to @kernellogger@hachyderm.io
@kernellogger @pojntfx @thomasmey yep, sending patch is the first step anyway, regardless of actual status in the maintainers file.
0
0
4
krzk

Krzysztof Kozlowski

Edited 19 days ago

When a vendor wants to control upstreaming process and objects to community-led patches, I’ll just point to this brilliant response from @conor:

It’s only better if <vendor name> submits better quality patches (no evidence for that yet) or submits the patches more promptly than others (which clearly has not happened here), and offers review commentary etc at a higher standard and more frequently than a non-employee maintainer would be able to do (there’s no evidence for that so far either, given you’re trying to stall this patchset). Your claim seems to have no merit as there is no proof that you’d do a better job.

https://lore.kernel.org/all/20250925-jaundice-uneasy-ff8b3b595879@spud/

2
17
33
krzk
repeated
LinaroLtd@mastodon.social

Linaro Limited

Collaboration and communication are at the heart of Linux kernel development. In the second part of our series, we explore how to work effectively with the Linux kernel community.

Read more here 👉 https://lnkd.in/eYgrqWZs

0
2
1
krzk

Krzysztof Kozlowski

Reply to @gregkh
@gregkh Oh, thanks for sharing! People received only cover letter and we all know how we treat cover letters, especially ones without patches :)

Work looks interesting, maybe it will solve the problem Bartosz and Wolfram were speaking about on conferences.
0
0
1
krzk

Krzysztof Kozlowski

Reply to @brauner@mastodon.social
@brauner @monsieuricon @kernellogger @geert Please check the link to doc patch from @geert - different domain does not solve dislike for automated Link:, as it seems.
0
0
0
krzk

Krzysztof Kozlowski

Reply to @geert@society.oftrolls.com
@geert @kernellogger @monsieuricon So I guess that's the answer to question if patch.msgid.link domain solves Linus' issue:
https://lore.kernel.org/all/497c9c10-3309-49b9-8d4f-ff0bc34df4e5@suse.cz/
1
0
0
krzk

Krzysztof Kozlowski

Reply to @krzk
@geert @kernellogger @monsieuricon Very secretive:
" Name: On behalf of msgid.link OWNER
Organization: c/o whoisproxy.com "
0
0
0
krzk

Krzysztof Kozlowski

Reply to @geert@society.oftrolls.com
@geert @monsieuricon @kernellogger
https://b4.docs.kernel.org/en/latest/config.html
> can also use https://msgid.link/%s, which is an alias for lore.kernel.org.
So I would guess that should be same owner as for kernel.org. Otherwise b4 docs should not recommend it.
1
0
0
krzk

Krzysztof Kozlowski

Reply to @monsieuricon

@monsieuricon @geert @kernellogger So basically:

git config --global b4.linkmask 'https://patch.msgid.link/%s'
1
0
0
krzk

Krzysztof Kozlowski

Reply to @gregkh
@gregkh Maybe such reports should be made public afterwards to serve as a warning?
0
0
0
krzk
repeated
NGIZero@mastodon.xyz

NGI Zero open source funding

The European Commission has issued a survey on the Governance and Sustainability of Critical Open Source Software.

The survey hopes to identify "pathways for collective efforts" and make "actionable recommendations for public administrations".

It's a relatively short survey, takes max 15 minutes & provides lots of opportunities to rate FOSS as 'very important' 😛

https://ec.europa.eu/eusurvey/runner/FOSSEPS_Governance_and_Sustainability_Survey

2
14
1
krzk

Krzysztof Kozlowski

Reply to @kernellogger@hachyderm.io
@kernellogger @geert That 6.17-rc5 was third complain ~last two weeks about Link tag, so I dropped it from my scripts. I see the rationale that automatically added Link which points to latest patch version, not even to the one with some sort of review happening, is just convenience instead of copy-paste of subject to lore.kernel.org. Useful to me but not worth dying for and I actually understand preference of having really useful Link or no Link at all.
3
0
1
krzk

Krzysztof Kozlowski

With @andi we are organizing another Linux'n'Beer meeting in Zurich, CH:

When: Friday, 12th Sep, 18:00
Where: Bierwerk Zuri, https://maps.app.goo.gl/unN5AkKQUVj6DQ3H6

The place is known of good beer and they also have some beer-food (snacks, focaccia), but don't expect proper dinner served.

Please kindly let me know if you plan to come, so I will adjust the table booking if necessary.

Also just as reminder - we have a mailing list, so join if you do not want to miss such announcements
lch @ https://subspace.kernel.org/lists.linux.dev.html

And IRC channel #linuxnbeer-ch (on Libera)
0
0
3
krzk
repeated
fustini

Drew Fustini

Reply to @krzk
@krzk the videos are published now!
https://youtu.be/dQgiWiyxU3A?si=mWDEyQ0dAy5X1n7_

https://youtu.be/TeygIvk4UHg?si=SVWs0YBPNInHxQEF
1
2
1
krzk

Krzysztof Kozlowski

Reply to @fustini
@fustini Nice! Thanks for pinging!
0
0
1
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: