* Forking pciehp
@ 2013-10-03 7:24 Shiro Itou 伊東
2013-10-03 13:23 ` gregkh
0 siblings, 1 reply; 2+ messages in thread
From: Shiro Itou 伊東 @ 2013-10-03 7:24 UTC (permalink / raw)
To: linux-hotplug
SGkgQWxsLAoKCldlIG1ha2Ugc29tZSBwcm9kdWN0IHNwZWNpZmljIGNoYW5nZSB0byAicGNpZWhw
IiBhbmQgd2FudCB0byBnaXZlIG1vZGlmaWVkICJwY2llaHAiIHdpdGggb3VyIHByb2R1Y3QgdG8g
Y3VzdG9tZXIuIEkgcmVhZCBHUEwgYW5kIEkgc2VlIHRoYXQgd2UgaGF2ZSB0byBhZGQgY2hhbmdl
IGxvZyBpbiBsaWNlbnNlIGhlYWRlci4KClNob3VsZCB3ZSBvciBjYW4gd2UgY2hhbmdlIG1vZHVs
ZSBhdXRob3IgdG8gb3VyIGNvbXBhbnkgbmFtZT8gTm93IEkgc2VlIG1hbnkgYXV0aG9ycywgR3Jl
ZywgSUJNLCBJbnRlbCBldGMuIGluIHBjaWVocCBjb2RlLiBPciB3ZSBoYXZlIHRvIGFkZCBvdXIg
Y29tcGFueSB3aXRoIG90aGVyIG5hbWVzPwoKQ2FuIHdlIGNoYW5nZSBkcml2ZXIgdmVyc2lvbj8K
CklzIGNvZGUgaGFzIHRvIGJlIG9wZW5zb3VyY2U/IElmIHllcywgdGhlbiB3aGVyZSB0byBrZWVw
IHRoZSBzb3VyY2UgY29kZT8gSXMgb3VyIGNvbXBhbnkgd2Vic2l0ZSBvayBvciBwdWJsaWMgc291
cmNlIHdlYnNpdGU/CgoKSSB0cmllZCB0byBnZXQgaW5mb3JtYXRpb24gb3RoZXIgcGxhY2UgYWJv
dXQgR1BMIGJ1dCBub3QgZ2V0IHdhbnRlZCBpbmZvcm1hdGlvbi4gU29ycnkgaWYgaXQgaXMgbm90
IGNvcnJlY3QgbWFpbCBsaXN0LgoKUGxlYXNlIGhlbHAuCgoKVGhhbmtzLApTaGlybyAJCSAJICAg
CQkgIA=
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Forking pciehp
2013-10-03 7:24 Forking pciehp Shiro Itou 伊東
@ 2013-10-03 13:23 ` gregkh
0 siblings, 0 replies; 2+ messages in thread
From: gregkh @ 2013-10-03 13:23 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-10-03 13:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-03 7:24 Forking pciehp Shiro Itou 伊東
2013-10-03 13:23 ` gregkh
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).