linux-kernel - Re: [PATCH 2/2] Add at24 based EEPROMs to the eeprom

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:	Thu, 23 Jan 2014 19:15:38 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Laszlo Papp <lpapp@....org>
Cc:	Curt Brune <curt@...ulusnetworks.com>,
	Thomas De Schampheleire <patrickdepinguin@...il.com>,
	gregkh@...uxfoundation.org,
	Shrijeet Mukherjee <shm@...ulusnetworks.com>,
	wolfram@...-dreams.de, linux-i2c@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] Add at24 based EEPROMs to the eeprom_dev hardware
 class


> Well, it is not the Copyrights section, or you are saying the same
> people should go to MODULE_AUTHOR as in the Copyrights section, even
> if it is potentially several names? I thought this would be the name
> of the person who put the file together even if from existing sources.

You may be right that the two can be viewed differently. Nonetheless,
adding 10 lines to an existing driver already upstream does not count
for both.

> >> PS.: Fixing the broken i2c mailing list typo, and updating Wolfram's
> >> address from the broken (obsolete?) version.
> >
> > It came through to the i2c list? What was wrong?
> 
> Yes, it did, _after_ fixing the typo in the mailing list address.
> Check the original mailing list address typed for details.

I did. That's why I asked :) Plus, since I got the original mail, it
must have come via i2c-list since my pengutronix address was in deed
wrong.


Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)