What about a different way of circumventing the GPL only symbols?
What prevents the author of a non-GPL module who needs access to a
GPL-only symbol from writing a small GPLed module which imports the
GPL-only symbol (this is allowed, because the small module is GPL),
and exports a basically identical symbol without the GPL-only
restriction?
Then he could use this new symbol from his non-GPL module.
Jan
-
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/