linux-kernel - Re: [PATCH 0/7] Nexus One Support

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]

Message-ID: <1295634906.19880.34.camel@m0nster>
Date:	Fri, 21 Jan 2011 10:35:06 -0800
From:	Daniel Walker <dwalker@...eaurora.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Joe Perches <joe@...ches.com>, Dima Zavin <dmitriyz@...gle.com>,
	linux-arm-msm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	davidb@...eaurora.org
Subject: Re: [PATCH 0/7] Nexus One Support

On Fri, 2011-01-21 at 10:27 -0800, Jesse Barnes wrote:

> Ok, then I'm sorry for jumping the gun.  The changelogs made the
> changes sound more trivial ("slight modifications and cleanup"); and
> those would only justify a small [] text near the s-o-b lines.  But if
> they're larger, maybe you should expand on the text and include the
> original authorship like Christoph suggested (or use the original
> author for patches where the changes really were trivial).

yeah, I didn't really think about that line when I wrote it.. It should
just says "Base on code from Google." I was just trying to give them
some credit.

I've done changes like your suggesting
(923a081c72fa2dccb7ea7070bd8e0f4dc99ceff8) so I'm not a novice to this.

Daniel


-- 
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum.


--
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/