On Mon, 15 May 2006, Nutan C. wrote:
> Ok, so now, I have a new doubt :-) Forgive me, if I am asking a lot, but
> I really don't want to move ahead with the development, until and unless
> I am sure I am not violating GPL. So, please bear with me. Here's the
> question:
>
> 1. I developed a code which interfaces well with a proprietary OS. Now,
> somebody else feels to use the same module in his Linux Kernel. So, he
> comes up with a patch, which interfaces and talks to my module with my
> interfaces and then makes a release with the patch. And, I would have no
> idea of my module being really compatible/used in Linux Kernel. One fine
> day, I would get a mail saying that I need to make my code open source.
> What would be my reply?
>
Big fat answer is No! You are not distributing GPL code. Just because
someone made GPL code that interacts with your module, doesn't make you
responsible for it. (OK now for a IANAL disclaimer) I'm not a lawyer, but
I would bet my career on this one (at least in the US).
You cant be held responsible for someone else's actions.
So your reply is simple:
I'm sorry, but I don't distribute GPL code, please see your distributor.
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
