Posts
464
Following
144
Followers
150
The cat is not mine :(

I like cycling, powerlifting, bad video games and metal.
Otherwise, I occupy my time with various bits in RISC-V land.

~useless, placeholder, website: https://www.conchuod.ie/

I'm excited to announce I've joined @olofj's RISC-V Software team at Tenstorrent! If you aren't familiar with Tenstorrent, then check this recent talk from CEO Jim Keller https://www.youtube.com/watch?v=lPX1H3jW8ZQ

2
6
2

We're proud to announce the official release of Fedora Asahi Remix! 🎉

Learn more:
https://asahilinux.org/fedora/

10
26
4
Being in my 20s, I was confused as to why YouTube keeps showing me adverts for toys for young children. I realised all I watch on this particular computer is videos about programming and 10+ year old MMOs and it all started to make a lot of sense.
0
0
3
@monsieuricon @a1ba there were plenty of younger developers at LPC, some significant contributors, sounds like it is time for current maintainers to start recruiting some of them as subsystem reviewers or co-maintainers!
0
0
4
Reading some patch discussion today (between two experienced developers/maintainers) and one cracked out a "I believe the kids these days would say '"Say you don't understand the
code without saying you don't understand the code."'

lmao, good one chief
0
1
4

Krzysztof Kozlowski

I announced it before on social.kernel.org, mailing lists and finally in the Linux kernel (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c25223cba5aa9a536392933782d4a7df71d9093b). So one more time, same announcement:
None of the Samsung and Samsung Foundry platforms can bring any new `dtbs_check W=1` warning.

Contributor can easily test it, so sending code which introduces such warnings is considered close to sending code which does not compile. Fast step to get your maintainer grumpy.
0
1
6
note to self: stop looking at patches when you are meant to be asleep
0
0
3

@vegard @marcan @CyReVolt @lschuermann @monsieuricon imho, anyone who's getting into kernel development or who is open to changing their workflow should use b4 right away and avoid using git-send-email

https://b4.docs.kernel.org/en/latest

1
6
1
@janne @hrw probably cos of
git log --oneline --no-merges Documentation/devicetree/bindings/arm/cpus.yaml
...
355d090ecbbc dt-bindings: arm: cpus: Add apple,avalanche & blizzard compatibles
0
0
2
@jarkko @gregkh just to note, it does not have to be part of OpenSBI. It just needs to be a frozen SBI extension. OpenSBI is but one one SBI implementation, and being part of it is not a requirement for patch acceptance.
1
0
1
"Detection of individual cryptography extensions uses the unified software-based RISC-V discovery method.

 At the time of writing, these discovery mechanisms are still a work in progress."

...from the documentation for ratified extensions :)
1
0
4
@sima @nicofee @marcan @nicolas17 unfortunately I know how things work for dt-bindings, and drag may be an apt word ;)
0
0
1
@sima @nicofee @marcan @nicolas17 it'd be nice of the email fallback was automated via get_maintainer and hooked into a b4-relay type thing, so that contributors don't need to give a shit about what is and what isn't cross forge.

Also, since I'm not a DRM contributor, is drm-misc where the dt based stuff for arm etc ends up? That's probably quite a big chunk of where your cross subsystem/forge stuff is, given there's very often bindings & devicetree changes mixed in with drivers?
1
0
1
@marcan @nicofee @nicolas17 @sima (and this isn't some antagonistic questioning shit, I actually want to know how that's going to work)
1
0
1
If there was some tool that gave me my review queue from a forge as something I can handle via my editor & synced my responses, I'd overwhelmingly rather use that than email.
0
0
0
@marcan @sima @nicofee @nicolas17 What I mean is, if you have some changes that affect both drivers/soc/apple and, idk, drivers/dma, how do you interact with the relevant maintainers for that code?
1
0
0
That said, forge ci integration is so so much better. I hate all the hoops that must be jumped through for patch-based CI...
1
0
1
I see today is iteration N of hating email based workflows. My 0.02 € is that I hate both, clunky aul email and clunky new UIs :)
1
0
2
@sima @nicofee @marcan @nicolas17 If you switch to those, how would you interact with the rest of the kernel?
1
0
1
Show older