Inside individual drivers, or a set of compat macros, it makes sense.
But as a general module.h primitive it doesn't.
Imagine a structure adds an owner field in 2.5. This macro doesn't
help you, you need a specific compat macro for that struct.
ie. AFAICT it only buys you 2.2 compatibility, and even then only if
you #define it at the top of your driver.
I still don't understand: please demonstrate a use in existing source.
Rusty.
-- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - 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/