The long term goal of kernel developers is to move the display drivers out the kernel. Then the proprietary vendors will only have to provide the X window driver library. This eliminates most of the objections and increases stability. The problem is that the current user to hardware access abstractions aren't rich enough or performant enough yet.
In my experience code reviews also bring to the surface any organizationl disfunction. Examples:
- Managers who refuse to allocate time for engineers to inspect the code.
- Quality bean counters that want the inspection check off more than the results.
- Pre-madonna engineers who believe their way is better than the rest of the code.
- Sloppy coding
- Personality clashes.
If these underlying issues don't get resolved, any push for code inspection just blows up in your face.
That said, good reviews do bring to light lots of potential bugs especially in SMP and other areas where automated checking tools are not enough.
Slashdot Mirror
The long term goal of kernel developers is to move the display drivers out the kernel. Then the proprietary vendors will only have to provide the X window driver library. This eliminates most of the objections and increases stability. The problem is that the current user to hardware access abstractions aren't rich enough or performant enough yet.
In my experience code reviews also bring to the surface any organizationl disfunction. Examples: - Managers who refuse to allocate time for engineers to inspect the code. - Quality bean counters that want the inspection check off more than the results. - Pre-madonna engineers who believe their way is better than the rest of the code. - Sloppy coding - Personality clashes. If these underlying issues don't get resolved, any push for code inspection just blows up in your face. That said, good reviews do bring to light lots of potential bugs especially in SMP and other areas where automated checking tools are not enough.