Messages in this thread |  | | | Date | Mon, 5 Jun 2006 12:27:46 +0200 (MEST) | | From | Jan Engelhardt <> | | Subject | Re: [Updated v3]: How to become a kernel driver maintainer |
| |
>With the large amount of hardware available for Linux, it's becoming > I do not know about LK customs, but in school we were always forced to write truncations out ("it is" rather than "it's").
>Some even see it as giving up control of their code. This is simply not the >case, and the end result is always beneficial to users and developers alike. > Frankly, they have to give up their coding style. A common style throughout the kernel is reasonable, though. But in some aspects it really gets nitpicky (spaces vs tabs to name one).
>The code review process is there for two reasons. First, it ensures that >only good code, that follows current API's and coding practices, gets into
Should read: "that follows current APIs"
>locking issues as well as big-endian/little-endian and 64-bit portability.
Suggestion: "as well as endianness and ..."
Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |