Agreed, but letting modules_install parallel run increases the risk of
somebody doing that. Most users will think that they can combine two
parallel runs into a single command, but if they are forced to single
thread modules_install it reduces the risk of user error.
> A bit of documentation at the beginning of the Makefile would do wonders
>for kernel-developer (not end user, please!) clarity. I've oft'asked the question
>as to what really is supported. I've tried things like make dep bzImage modules --
>I noticed it didn't work fairly quickly. Same with modules/modules_install --
>people would probably figure that one out, but just a bit of documentation would
>help even that.
The 2.5 kbuild system will be fully documented, all the way from
reasons for doing things down to how they are down. Trust me on this!
I have had too many problems with undocumented changes in kbuild.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/