linux-kernel - RE: [PATCH 1/1 V2] rtc: Add real-time clock driver for Tegra.

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] [day] [month] [year] [list]

Message-ID: <643E69AA4436674C8F39DCC2C05F763816BB82899B@HQMAIL03.nvidia.com>
Date:	Fri, 15 Oct 2010 15:57:26 -0700
From:	Andrew Chew <AChew@...dia.com>
To:	'Erik Gilling' <konkers@...gle.com>, Greg KH <greg@...ah.com>
CC:	Jon Mayo <jmayo@...dia.com>,
	"a.zummo@...ertech.it" <a.zummo@...ertech.it>,
	"olof@...om.net" <olof@...om.net>,
	"mcuos.com@...il.com" <mcuos.com@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>
Subject: RE: [PATCH 1/1 V2] rtc: Add real-time clock driver for Tegra.

> >> This is kinda odd.  Usually when doing work on behalf of 
> the company
> >> you work for, the code is (c) the company.  Consider changing Jon's
> >> line to "Author: Jon Mayo <jmayo@...dia.com>"
> >
> > Woah, are you sure?  Some companies, and countries, 
> allow/require dual
> > copyright.  The only one who can change this for sure is 
> Jon, not anyone
> > else.
> 
> I stand corrected.  However, I have yet to see a Tegra patch from
> nvidia that lists any author name, copyright or no.  Jon, can you
> clarify?

I've already corrected this (see V3 of this patch).  I removed Jon from the top comment block, and put him instead into MODULE_AUTHOR.--
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/