@krzk@social.kernel.org
@krzk@social.kernel.org avatar

krzk

@krzk@social.kernel.org

Linux Kernel developer and maintainer
🇵🇱 🇪🇺 🇰🇷 🇮🇱 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk

This profile is from a federated server and may be incomplete. Browse more on the original instance.

krzk, to random
@krzk@social.kernel.org avatar

That's an interesting session: @cas explaining current status of upstream U-Boot on Qualcomm robotic platforms - using mainline kernel DTS and getting to SystemReady IR.
Slides: https://calebs.dev/u-boot24.pdf
https://www.kitefor.events/events/linaro-connect-24/submissions/183

kernellogger, to linux
@kernellogger@fosstodon.org avatar

regressions only reported after a long time[1] will be handled as bugs (IOW: the "no regressions" rule does not really apply any more), as this recent mail from Linus shows:

https://lore.kernel.org/all/CAHk-%3DwgFuoHpMk_Z_R3qMXVDgq0N1592%2BbABkyGjwwSL4zBtHA@mail.gmail.com/

[1] How long? Not sure, in the end that's up to Linus. But from an earlier mail of him I guess it everything found after more that a year might become problematic:

https://lore.kernel.org/all/CAHk-=wis_qQy4oDNynNKi5b7Qhosmxtoj1jxo5wmB6SRUwQUBQ@mail.gmail.com/

krzk,
@krzk@social.kernel.org avatar

@kernellogger Linus expressed few times that if something was broken for very long time, was not working for long time, it should not be treated as urgent/important fix thus should not go to current RC cycle. Instead, should go via normal development branch, so for the next merge window. I know that stable folks have different point of view - they also expressed it.

I personally follow exactly the same approach in handling fixes: if something was broken for long time, it is regular bugfix thus goes to "for-next" branch, not "fixes / for-linus / for-current-rc".

Now, if a regression was unnoticed for 8 years, it kinda fits above criteria.

krzk, to random
@krzk@social.kernel.org avatar

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. :)

krzk, to random
@krzk@social.kernel.org avatar

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 and Olof) for the next merge window. Good job Peter Griffin and @LinaroLtd :)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • provamag3
  • ngwrru68w68
  • InstantRegret
  • ethstaker
  • magazineikmin
  • osvaldo12
  • rosin
  • mdbf
  • Youngstown
  • khanakhh
  • slotface
  • Durango
  • kavyap
  • DreamBathrooms
  • JUstTest
  • thenastyranch
  • tacticalgear
  • cisconetworking
  • GTA5RPClips
  • modclub
  • cubers
  • normalnudes
  • everett
  • tester
  • megavids
  • Leos
  • anitta
  • lostlight
  • All magazines