The intention of the module is being GPL 2.0+, not 3.0+. Those files were a contribution by Johannes Schmid (added to the CC); what's the problem in having some GPL 3.0+ files in a GPL 2.0+ package? Otherwise we can ask Johannes if he's OK with changing the license for them to GPL 2.0+.

(In reply to comment #1)
> what's the problem in having some GPL 3.0+ files in a GPL 2.0+ package?

There's no problem; it just means the module is GPL 3.0+. In that case, COPYING should specify this :-)

I don't really see the relevance of GPL 3+ vs. GPL 2+ on this module so I am fine with changing it.

Thanks Johannes! I now changed the offending headers to read GPL v2+ on git master.