[dom0]

Besides some scattered text files and the Linux man pages, there is this: https://www.kernel.org/doc/html/latest/

It's fairly new - started about a year ago, but there's quite a lot of stuff in there already (bootstrapped from the old XML stuff, I believe).

[SunnySkies]

... That guide is actually fucking hilarious.

'However, that’s not too bad, because even the makers of GNU indent recognize the authority of K&R (the GNU people aren’t evil, they are just severely misguided in this matter)'

[mindcrime]

but the preferred way, as shown to us by the prophets Kernighan and Ritchie, is to put the opening brace last on the line, and put the closing brace first, thusly:

So much for the idea that kernel developers are super-smart programming "gods". Formatting code that way is brain-dead and Kernighan and Ritchie are false prophets. The real prophet, Allman, tells us the Truth - curly braces go on a line by themselves, aligned vertically and indented to the same level as their corresponding control structure.

[int_19h]

These theories were ultimately settled by trial by combat between the champions representing each: Linux and BSD. Linux has clearly won this battle, and thus, the gods have spoken. ~

[kruczek]

For a quick overview, I like http://www.makelinux.net/kernel_map/ - even though it's a bit dated (the map mentions kernel 2.6.36), I find it a good starting point for digging deeper.