From: Stephen Warren <firstname.lastname@example.org> To: Dmitry Osipenko <email@example.com>, Bob Ham <firstname.lastname@example.org>, Stefan Agner <email@example.com>, Peter Geis <firstname.lastname@example.org> Cc: 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 10:08:10 -0600 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 10/7/20 7:53 AM, Dmitry Osipenko wrote: > 07.10.2020 16:36, Bob Ham пишет: >> Hi all, >> >> The Bluetooth controller driver sent to linux-input by Lukas Rusak >> (CC'd) is a bit of a concern. Here is the original driver: >> >> https://github.com/ouya/ouya_1_1-kernel/blob/master/drivers/hid/hid-ouya.c >> >> and you can see that there is no SPDX header, no license information and >> no MODULE_LICENSE declaration. I'd previously noticed this as a >> possible cause for concern in upstreaming the driver. >> >> Meanwhile, Lukas's driver is clearly derived from the Ouya Inc. driver >> and even retains the Ouya Inc. copyright notice line. However, Lukas's >> driver now has a MODULE_LICENSE("GPL") declaration added. >> >> Lukas, did you get clear permission to license the driver as GPL? >> >> Alternatively, kernel developers with greater legal or Ouya knowledge, >> is this actually a concern or is it nothing to worry about? > > Hello Bob, > > That can't be a problem because: > > 1. Ouya Inc. doesn't exists anymore. > > 2. If code was officially published, then this implies that it can be > derived. > > 3. Ouya's driver uses kernel symbols that are explicitly marked as > GPL-only, see hid_open_report for example. Hence Ouya's driver inherents > the GPL license. > > 4. Lukas's patch doesn't remind the original code at all. > > 5. In practice nobody cares about legal much if money aren't involved. > Even if it happened that driver was 100% violating some copyrights, then > it either won't be accepted to upstream or will be removed by request > from the copyrights holder. 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.
next prev parent reply other threads:[~2020-10-07 16:15 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 [this message] 2020-10-07 17:18 ` Peter Geis 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 \ --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 \ --firstname.lastname@example.org \ --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).