Posts
195
Following
32
Followers
215
Linux Kernel developer and maintainer
🇵🇱 🇪🇺 🇰🇷 🇮🇱 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
krzk

Krzysztof Kozlowski

Reply to @rmader@floss.social
@rmader @mort @cassidy @agx @cas I do not see any bindings patch there. No comments from DT maintainers either.
1
0
1
krzk

Krzysztof Kozlowski

Reply to @rmader@floss.social
@rmader @agx @mort @cassidy @cas DT is not for software properties. Camera orientation is a hardware property. I don't know from where you get the impression that properties useful to user-space are no allowed. The user of bindings can be in user-space, firmware, bootloader etc.
2
0
1
krzk
repeated
corbet

Jonathan Corbet

So they made a movie about my dad ...

https://fullcirclefilm.co/

...and about a crazy kid named Trevor Kennison and how both recovered their lives after a devastating injury. I've seen it, it's definitely worth a watch. The site lists a lot of upcoming screenings (all just in North America, alas).
0
6
16
krzk

Krzysztof Kozlowski

Reply to @MishaalRahman@androiddev.social
@MishaalRahman News were dropped half a year ago. Nothing new was said this week. :/
1
0
1
krzk

Krzysztof Kozlowski

What a pleasant surprise - I am going to Plumbers! My talk about useful tool-set for fresh Linux kernel maintainers was accepted for this years Linux Plumbers Conference:
https://lpc.events/event/17/contributions/1498/
The cool part is that I will speak very early - on the second slot of the first day.
0
1
11
krzk

Krzysztof Kozlowski

Reply to @gregkh
@gregkh @corbet @sjvn I guess we should start making full, regular press releases, so journalists will not wake up surprised half a year later after the decision is made public.
1
0
4
krzk

Krzysztof Kozlowski

Reply to @kernellogger@fosstodon.org
@kernellogger yeah, it's not the first time news talk about stuff already known in the community...
0
0
1
krzk

Krzysztof Kozlowski

Edited 1 year ago
For a year I have been keeping a branch on top of linux-next with all the cleanups and fixes for Qualcomm SoCs Devicetree sources. Goal is to pass DT schema validation someday (just like Samsung does). I update and rebase the branch frequently. I also add new patches to fix existing warnings. Unfortunately, the branch actually never gets smaller: I always have around 120-200 patches on top of linux-next. Always. Now, after rebasing on next-20230913 it is ~150 patches. Still 150 patches just cannot get applied...

If anyone tells you "Linux kernel development goes too fast", he is wrong. It's too slow. For one year I was able to create fixes much faster than people were applying then.

Branch is here if anyone wants to avoid duplicating work/effort:
https://github.com/krzk/linux/tree/pending/dt-bindings-qcom-new-and-fixes-for-warnings-linux-next
0
0
3
krzk

Krzysztof Kozlowski

Syzkaller now creates nice monthly reports reminding what could be fixed. Anyone bored enough or having enough of spare time to fix these NFC issues (having repro!)?
https://lore.kernel.org/all/0000000000008253550604ac4d36@google.com/
0
1
2
krzk

Krzysztof Kozlowski

Reply to @jarkko
@jarkko @vbabka Hiding your master (primary or [C]) key is a bit independent step and usually done before moving subkeys to crypto device.
1
0
2
krzk

Krzysztof Kozlowski

Reply to @vbabka
@vbabka @jarkko Yes, that's the best, but I would start from basics - definitely not having master's secret key in your workstation keyring.
1
0
0
krzk

Krzysztof Kozlowski

Reply to @gregkh
@gregkh @jakub ID is needed for the press release, TicToc, Snapchat and all the hype :)
1
0
2
krzk

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
krzk

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
krzk

Krzysztof Kozlowski

Reply to
@linuxplumbersconf Thanks. Good to know, although better would be to have in the Mastodon profile. It would avoid any misunderstandings.
0
0
0
krzk

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
krzk

Krzysztof Kozlowski

Reply to
Edited 1 year ago
@siddhesh_p @gregkh @sj You did not really cover the case. Either this customer had outdated kernel, thus the group should not even start creating CVE, or this kernel did not have basic fix which was fixed 7 years ago. In the latter case it would be enough just to backport the fix, not go through ridiculous CVE assignment.

Anyway, it is not really professional and what RedHat is doing with CVEs is awesome example how useless CVEs are.
1
0
2
krzk

Krzysztof Kozlowski

Reply to
@siddhesh_p @gregkh @sj Independently? Something fixed 7 years ago? How can you trigger such bug?

I can barely believe that any customer discovered now a bug which was fixed 7 years ago. Even if this is possible, I can hardly believe any sane person on distro side would request for CVE for such bug, instead of replying: "dude, you forgot to update your system for the last 7 years".

So no, much more likely is that RedHat was actually shipping some crazy old kernel to some people without that fix and needed CVE to justify touching this old stuff...
1
0
0
krzk

Krzysztof Kozlowski

Reply to
Edited 1 year ago
@siddhesh_p @gregkh @sj Yeah, maybe they do not require CVE for every backport anymore... but then:
"Heh, apparently Red Hat recently assigned a CVE for a random kernel fix I did 7 years ago"
so not really.
https://mastodon.social/@vegard/110933167051678536
1
0
1
krzk

Krzysztof Kozlowski

Reply to @yassie_j@0w0.is
@yassie_j So the time came for: "Oh, you solved captcha in your first try, you clearly must be a robot. Bye.".
0
0
0
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: