On 11/06/2012 01:06 PM, Dmitry Osipenko wrote: > 06.11.2012 21:38, Stephen Warren wrote: >> OK, so only you and he have the binaries built from this repository? Or, >> are those binaries distributed to other people too? If the binaries are >> distributed, you need to distribute (or offer to make available) the >> source too. See the GPL for exact requirements. > > I'm not against GPL, but for now repo is private. It's something like nvidia's > private downstream kernel that I'm working on. Surely it will become public > but > bit later. > >> OK, so if I accept the private repo link, download the source, and >> repost it on my github account, you're fine with that? If not, then >> you're requesting something semantically equivalent to an NDA. > > For me it's not very important, but my companion may be unhappy with that. I > just believe that you are not so evil. As I understand NDA should be some > legally valid official document. I'm sure you are much better in this than me, > so let's stop discussing it. > >> However, I'd ask that we resolve the distribution issues of the source >> kernel first to avoid any tainting of the patch. > > I don't see any issues. It's my personal work that I'm contributing to the > kernel community. If nvidia is against of any public contributions just tell > me.
NVIDIA and indeed the kernel community welcome public contributions. However, the rules in SubmittingPatches (as set by the kernel community, not NVIDIA) are clear re: the licensing requirements for patches. If you're taking the patches from a downstream kernel that's published as binaries and not source, I believe that makes the patches non-compliant (since there's a GPL violation in the downstream kernel, so the patches can't be passed off as being GPL compliant), and hence your signed-off-by line is not valid. Once the downstream kernel's source is publicly available, I imagine there will be no problem accepting patches that are derived from it. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
