lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 18 Nov 2006 18:46:09 +0100
From:	Pavel Machek <pavel@....cz>
To:	Vivek Goyal <vgoyal@...ibm.com>
Cc:	Andi Kleen <ak@...e.de>, Paul Mackerras <paulus@...ba.org>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Reloc Kernel List <fastboot@...ts.osdl.org>,
	ebiederm@...ssion.com, akpm@...l.org, hpa@...or.com,
	magnus.damm@...il.com, lwang@...hat.com, dzickus@...hat.com,
	rjw@...k.pl
Subject: Re: [PATCH 20/20] x86_64: Move CPU verification code to common file

Hi!

> > > > > + *	Copyright (c) 2006-2007  Vivek Goyal (vgoyal@...ibm.com)
> > > >
> > > > Normally it's not ok to take sole copyright on code that you mostly copied ...
> > >
> > > Is this a case where the original had no copyright notice?  If so,
> > > what do you suggest Vivek should have done?
> > 
> > The head.S code this was copied from definitely had a copyright.
> > 
> 
> I am sorry but I am completely unaware of the details of Copyright
> information. Somebody please tell me what should be the right info
> here given that basically I have taken the code from
> arch/x86_64/boot/head.S, picked modifications done by Eric and minor
> changes of my own.
> 
> Do I copy here all the copyright info of head.S and then add Eric's
> name and mine too?

Yes, that's "the safest" method to do it. (Or most politicaly correct
or something.)
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ