Age | Commit message (Collapse) | Author |
|
other parts of the kernel don't need to care about which process exactly
gets switched into
|
|
|
|
|
|
|
|
|
|
|
|
proper multiprocess support!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
it's not related to logging but to general io, the old name didn't make
sense
|
|
While I personally don't see a reason to use NULL instead of 0, I assume
that whoever made that a sparse default knew what they were doing.
|
|
|
|
thanks to this i can tell which ones are placeholders, and which ones
should stay
|
|
makes the code slightly simpler, imo
|
|
|
|
i think that making the call a bit more "transparent" makes the code
nicer
|
|
|
|
|
|
otherwise this doesn't compile with -O0
|
|
|
|
|
|
|
|
this avoid accidental dereferences, and now it's easy to tell apart
which pointers are safe to directly read and which aren't.
cons:
- const is completely discarded
|
|
`()` means that any amt of arguments will be accepted, which isn't what
i want
|
|
|