From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Forking pciehp
Date: Thu, 03 Oct 2013 13:23:20 +0000 [thread overview]
Message-ID: <20131003132320.GA14504@kroah.com> (raw)
In-Reply-To: <SNT149-W11A0AD93792AA76B54826E9A170@phx.gbl>
On Thu, Oct 03, 2013 at 12:24:48AM -0700, Shiro Itou 伊東 wrote:
> Hi All,
>
>
> We make some product specific change to "pciehp" and want to give
> modified "pciehp" with our product to customer. I read GPL and I see
> that we have to add change log in license header.
Who is "we"?
And secondly, for all legal questions, please consult a lawyer for your
company, they are the best to answer these questions, not random
developers on a public mailing list.
And no, the GPL does not say you have to add a changelog to the license
header.
> Should we or can we change module author to our company name? Now I
> see many authors, Greg, IBM, Intel etc. in pciehp code. Or we have to
> add our company with other names?
No, no need to change the author, just know about the copyrights of the
other companies and authors and deal with it properly as per copyright
law.
> Can we change driver version?
What did you change? Why not just post your change as a patch and get
it accepted upstream properly for everyone to then use?
Please read the kernel files, Documentation/SubmittingPatches and
Documentation/development-model/ for how kernel development works.
> Is code has to be opensource?
Yes of course, you can not change the license of the file, or the Linux
kernel, why would you think otherwise?
> If yes, then where to keep the source code? Is our company website ok
> or public source website?
That is up to you.
> I tried to get information other place about GPL but not get wanted
> information.
Where did you look, there is lots of public information out there.
But again, you should always ask lawyers about legal things, not
programmers.
Hope this helps,
greg k-h
prev parent reply other threads:[~2013-10-03 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 7:24 Forking pciehp Shiro Itou 伊東
2013-10-03 13:23 ` gregkh [this message]
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=20131003132320.GA14504@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-hotplug@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).