This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Licensing conflict with OpenAFS kernel module

On 26 Apr 2006, at 17:29, Anthony Liguori wrote:

Those symbols are used by some extremely primitive and ubiquitous kernel macros (e.g., local_irq_enable(), local_irq_restore(), pagetable macros, page_to_phys(), ...).

I think the obvious course of action is to make those two EXPORT_SYMBOL() and add a comment to explain why. There's not exactly a lot of GPL'ed goodness hidden behind them!

Agreed, and in general, my suspicion is that for upstream merge, we have to make sure that we're not changing the license constraints of any existing EXPORT_SYMBOL().

The whole EXPORT_SYMBOL thing is pretty insane anyway. Given that the whole kernel is GPL, the concept of non-GPL hooks is a legal nonsense (or the GPL itself is a legal nonsense).

 -- Keir

Xen-devel mailing list