From: Peter Geis <firstname.lastname@example.org> To: Stephen Warren <email@example.com> Cc: Dmitry Osipenko <firstname.lastname@example.org>, Bob Ham <email@example.com>, Stefan Agner <firstname.lastname@example.org>, Rob Herring <email@example.com>, Thierry Reding <firstname.lastname@example.org>, Jonathan Hunter <email@example.com>, Matt Merhar <firstname.lastname@example.org>, Leonardo Bras <email@example.com>, Michael Brougham <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, Lukas Rusak <firstname.lastname@example.org> Subject: Re: [PATCH v3 0/3] Support NVIDIA Tegra-based Ouya game console Date: Wed, 7 Oct 2020 13:18:36 -0400 [thread overview] Message-ID: <CAMdYzYrNg39QmR3QDG4T5DTOht=8p4LvFon14M1J7HkEZo4KRQ@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Wed, Oct 7, 2020 at 12:08 PM Stephen Warren <firstname.lastname@example.org> wrote: > > > This definitely isn't the correct attitude to copyright. > > The facts 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/ > >  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.  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.  https://github.com/ouya/ouya_1_1-kernel/commit/407e72990e39d5c29d015e21110b9497aea2dfe3
next prev parent reply other threads:[~2020-10-07 17:18 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-04 13:31 Peter Geis 2020-10-04 13:31 ` [PATCH v3 1/3] ARM: tegra: Add device-tree for Ouya Peter Geis 2020-10-05 14:02 ` Dmitry Osipenko 2020-10-05 14:22 ` Peter Geis 2020-10-05 14:29 ` Dmitry Osipenko 2020-10-05 14:29 ` Dmitry Osipenko 2020-10-04 13:31 ` [PATCH v3 2/3] dt-bindings: Add vendor prefix for Ouya Inc Peter Geis 2020-10-05 14:32 ` Dmitry Osipenko 2020-10-04 13:31 ` [PATCH v3 3/3] dt-bindings: ARM: tegra: Add Ouya game console Peter Geis 2020-10-05 14:32 ` Dmitry Osipenko 2020-10-05 15:47 ` [PATCH v3 0/3] Support NVIDIA Tegra-based " Thierry Reding 2020-10-07 7:22 ` Stefan Agner 2020-10-07 13:36 ` Bob Ham 2020-10-07 13:53 ` Dmitry Osipenko 2020-10-07 14:01 ` Dmitry Osipenko 2020-10-07 16:08 ` Stephen Warren 2020-10-07 17:18 ` Peter Geis [this message] 2020-10-08 5:05 ` Dmitry Osipenko 2020-11-10 17:42 ` Thierry Reding
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAMdYzYrNg39QmR3QDG4T5DTOht=8p4LvFon14M1J7HkEZo4KRQ@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v3 0/3] Support NVIDIA Tegra-based Ouya game console' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).