does anyone know of a fairly comprehensive rules to follow for Linux kernel code (or any other kernel)? not talking about coding style but rather stuff like "keep interrupt handlers below 5 microseconds" or "don't touch user-mode memory directly"
-
-
Replying to @johnregehr
If such a thing existed, the kernel wouldn't be such a shitshow.
1 reply 0 retweets 6 likes -
Replying to @RichFelker @johnregehr
The SPI layer developers literally didn't even understand the rules for their own subsystem's locks....
1 reply 0 retweets 1 like -
Replying to @RichFelker @johnregehr
There is literally no documentation of the interface contracts of 99% of the kernel-internal interfaces. It's all either purely in somebody's head, or nowhere at all!
2 replies 0 retweets 4 likes
Replying to @RichFelker @johnregehr
It's no accident that musl mostly avoids having internal interfaces at all; not having them means not having to document/specify them.
4:16 PM - 16 Nov 2017
0 replies
0 retweets
2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.