Maybe the way to stop this sort of problem is to enforce it in the kernel
build procedure/Makefiles (and/or in the module's build procedure, if it's
separate to the kernel's).
Eg: Anything that produces output code (bzImage, modules, etc) should fail
if .config is newer than any of the dependencies. Maybe even spit out a
"You need to run 'make dep' before using 'make bzImage'" or something like
that. If they really want to get round it, they can play with 'touch'.
This seems perfectly logical to me.
AMC Enterprises P/L - Stuart Young
First Floor - Network and Systems Admin
3 Chesterville Rd - email@example.com
Cheltenham Vic 3192 - Ph: (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/