Posts
215
Following
35
Followers
247
Linux Kernel developer and maintainer
#standwithukraine 🇵🇱 🇪🇺 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
krzk
repeated
timkmak@journa.host

Tim Mak

Good morning to readers; remains in Ukrainian hands.

helped the U.S. in its invasion of Iraq, losing 18 of its own men.

But when needed help, the U.S. leveraged Ukraine's weakness.

Serhii, who served in Iraq, knows the risks of allying with the U.S.

1
4
1
krzk
repeated
monsieuricon

K. Ryabitsev 🍁

Edited 2 months ago
PSA: please don't use git.kernel.org directly for your CI needs. It is not viable for us to provide enough capacity to withstand dozens of CI nodes all trying to clone linux.git at the same time for multiple CI farms. You *will* get ip-blocked. Please set up a local mirror and hit that instead.
2
44
55
krzk
repeated
sima@chaos.social

🐧sima🐧

uspol
Show content

if it walks like a russian agent and quacks like a russian agent, then it probably doesn't matter whether it really is a russian agent or not

0
1
1
krzk
repeated
nivex@tenforward.social

Nivex 🐧 📻

Edited 3 months ago

I made a developer meme
cc @Codeberg

0
4
1
krzk
repeated
0xB0D@mastodon.social

Bryan O'Donoghue

Reply to @rbreich@masto.ai

@rbreich
The leader of the free world right now is Zelenskyy.

While Trump fumes at home Zelenskyy is becoming an icon.

0
1
1
krzk

Krzysztof Kozlowski

Not only new Linux kernel releases count! Look at LWN summary of v4.19-stable life and how many fixes that kernel received:
https://lwn.net/Articles/1000933/

Appearing on top-bugfix contributors list for v4.19.x series is a pleasant reminder that my contributions might actually help some real users on real products.
1
9
21
krzk
repeated
SecureOwl@infosec.exchange

Mike Sheward

If you've ever wondered what it is like to throw up and have diarrhea simultaneously, JIRA now has an AI button.

1
3
1
krzk

Krzysztof Kozlowski

Reply to @kernellogger@fosstodon.org
@kernellogger Wasn't. Although if you combine it with these one-liners:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=812a33a65d00e3d813f5ed2c9923569acd0b445c
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da968c3ce459442e83b021d73417b9402c8b14c5
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=824ed4cb629c87b0b8aec997d3b7f6f77143ad25
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=859a661eb493fffa88ea5c94b0cd62ecc7b24634
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aaf69c606f0865c8ad3571e1725372f21b5ad97a
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9b995d1af162f1736dd1d62ec3f6f9a5d6be5c84

... you will get on average not that big patchset, so maybe it was on-average-reviewed-by.
1
0
2
krzk

Krzysztof Kozlowski

Reply to @geert@society.oftrolls.com
@geert Irony is here that since some time, if as a contributor you receive no responses to your patch or to your ping, please check if you are not on the SDN list or if you are not suspected to be on the SDN list, because even a reply like "I cannot work with you" might be tricky for maintainers. Basically it is indistinguishable between being lost in maintainer's mailbox, being PLONK-ed or being sanctioned. :)
0
0
4
krzk

Krzysztof Kozlowski

Reply to @sima@chaos.social
@sima We can rephrase your surprise into:
"Big subsystem had only one maintainer for ~10 years"

That's also wild.
0
0
7
krzk

Krzysztof Kozlowski

Anyone has cool Arm topics to share? The Call For Papers for Linaro Connect conference in Lisbon is still open (till 13th Feb)!
https://www.linaro.org/connect/call-for-proposals

The Connect will be in May:
https://www.linaro.org/connect/
0
3
3
krzk
repeated
luis_in_brief@social.coop

Luis Villa

I’ve told LF repeatedly that “education” as the leading point is insulting. Many maintainers know exactly what they need to do, but they lack time and energy for it. Lecturing them, I mean “giving them skills”, is… not actually a solution.

But it allows LF (and friends like GH) to continue elephant-in-the-room-ing the actual solution, which is paying maintainers for the trillions of dollars of value they create.

https://fosstodon.org/@donmccurdy/113512775802077660

5
11
1
krzk

Krzysztof Kozlowski

Reply to @donmccurdy@fosstodon.org
@donmccurdy Copilot training and "3-week program consisting of a 5-10 hour commitment each week" is exactly what community needs to fix cases like XZ with busy maintainer bullied by bad actors.

Microsoft, are you ill? Are you just joking here around or just want to sell your crapy Copilot? This is just an insult to Open Source maintainers.

@martin.social You do not see how inappropriate this is?
0
3
4
krzk
repeated
donmccurdy@fosstodon.org

Don McCurdy

I've been expecting something like this since the XZ hack, but still ... frustrated/annoyed/sad to see Microsoft and 13 (!) partners jointly announcing that their answer is to “educate” open source maintainers.

It's nice that they're compensating maintainers for the time spent on that training, but ... compliance with corporate security policies is still a whole lot of ongoing, unpaid work after that? Sigh.

https://github.blog/news-insights/company-news/announcing-github-secure-open-source-fund/

3
9
0
krzk

Krzysztof Kozlowski

Reply to @luis_in_brief@social.coop
@luis_in_brief Aaah, so now I know what was missing in my maintainer's life:
"Maintainers will get hands-on learning of security principles, tools like GitHub Copilot and Copilot Autofix"
Github Copilot!

Microsoft jokes from open-source...
0
1
1
krzk

Krzysztof Kozlowski

Reply to @jarkko
@jarkko What I miss in LWN stats is the employer stats for Tested/Reviewed-by. There are such for committer Signed-offs, which shows only part of employer support for long term maintenance.

@corbet Maybe for the next LWN stats? (Tested/Reviewed aggregated over employer names)
1
0
0
krzk

Krzysztof Kozlowski

Edited 6 months ago
Last year, for each of six Linux kernel releases - v6.7, v6.8 ... v6.12 - I was topping the list of most active contributors. This consistency led to a more interesting stat: I am one of the most active Linux kernel contributors for this period (and I don't count Kent here as he just dropped stuff out of tree... and then developed things to his own tree without review or mailing list collaboration) with 1339 commits upstream.

I am however more proud of another impact I made: I am one of the most active reviewers of the last one year of Linux kernel development. Reviewing takes a lot of time, a lot of iterations, a lot of patience, a lot of template answers and results with only "some" of reviewed-by credit going to Linux kernel git history. Yet here I am: ~1000 reviewed-by credits for last year v6.7 - v6.12 Linux kernel.

Source, LWN.net:
https://lwn.net/SubscriberLink/997959/377cf2f076306247/
2
9
54
krzk
repeated
monsieuricon

K. Ryabitsev 🍁

1000 days since the Russian army invaded Ukraine, destroying its cities and murdering civilians, all because Putin needed a "quick victorious war" to remain in power.

I will never forget, and I will never forgive.
0
24
49
krzk

Krzysztof Kozlowski

Reply to @thibaultmol@en.osm.town
Edited 6 months ago
@thibaultmol @kernellogger @tuxedocomputers " this license allows them to prevent from someone else" - this is exactly something they should not do. We all know open-source compliance releases have poor quality and we do not have problems with that. That's life. But what they did is:
1. Release poor quality code.
2. Restrict community rights of improving it and bringing upstream.
That's a big no-go, big NAK for Tuxedo. Interesting twist, how one can release something open-source but not in open-source spirit.
0
2
8
krzk

Krzysztof Kozlowski

Reply to @kernellogger@fosstodon.org
@kernellogger @tuxedocomputers I wonder what is actually worse for customers: crappy driver release from vendors just for open-source compliance or this pseudo-open-source-move from Tuxedo which effectively blocks any community from upstreaming this code.

Let's recap what Tuxedo said:
> We do not plan to relicense the tuxedo-drivers project directly as we want to keep control of the upstream pacing,

This is absolutely terrible move, restricting community and customers from working upstream. Kind of what proprietary company would like to do... Bleh, just choose other laptops.
0
1
11
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: