On Wed, Oct 7, 2020 at 12:08 PM Stephen Warren <swarren@xxxxxxxxxxxxx> wrote: > > > This definitely isn't the correct attitude to copyright. > > The facts[1] that Ouya published the code and that it used GPL-only > symbols certainly does imply that they *should* have published under GPL > or a compatible license, but doesn't mean that they definitely did. The > only way to know that for sure is for there to be evidence in the file > content or git history, such as license headers or Signed-off-by lines. > > When someone writes Signed-off-by in their code submission, which is > required to contribute to upstream Linux, they are stating/warranting > certain things about the code they're submitting. One aspect is that > they definitely have the rights to submit the code under the given > license. Without evidence to this effect, or having written the code > themselves, nobody can state/warrant this. Take a look at the following > link to see what you're stating/warranting when writing Signed-off-by in > a code submission: > > https://developercertificate.org/ > > [1] I haven't checked the facts. Unfortunately the only source release I've been able to find is the last release. Ouya purposely purged the git history for the current source release, it's also completely lacking in signoffs and commit history. [1] is the commit that added this driver to their source. Their original source release had the git history intact, but I never got a copy of it before Ouya purged it from their repos. [1] https://github.com/ouya/ouya_1_1-kernel/commit/407e72990e39d5c29d015e21110b9497aea2dfe3
