[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTikSqdHDzQUZdh87YX3y+=GtKDe27g@mail.gmail.com>
Date: Fri, 10 Jun 2011 14:08:10 -0400
From: Mike Frysinger <vapier.adi@...il.com>
To: Lars-Peter Clausen <lars@...afoo.de>
Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Liam Girdwood <lrg@...com>,
uclinux-dist-devel@...ckfin.uclinux.org,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
device-drivers-devel@...ckfin.uclinux.org
Subject: Re: [Device-drivers-devel] [PATCH 1/3] ASoC: Add ADAU1701 codec driver
On Fri, Jun 10, 2011 at 13:57, Lars-Peter Clausen wrote:
> On 06/10/2011 07:43 PM, Mike Frysinger wrote:
>> On Fri, Jun 10, 2011 at 13:18, Lars-Peter Clausen wrote:
>>> +MODULE_AUTHOR("Lars-Peter Clausen <lars@...afoo.de>");
>>
>> did you actually rewrite this thing from scratch ? seems like you
>> should keep Cliff as the author in git/MODULE_AUTHOR, and then add
>> your name to the s-o-b list and this macro.
>
> Not from scratch, but I guess except for the register definitions and the
> copyright header not much of the original driver is left:
> sound/soc/codecs/adau1701.c | 662 ++++++++++++++++++++++++-------------------
> 1 files changed, 371 insertions(+), 291 deletions(-)
based purely on LoC, Cliff wrote 467, so you took that and punted 291
(62%) and then added 371. that leaves the final file with 32% Cliff
and 68% you.
however, some of that was register renaming and shuffling between the
adau1701.c and adau1701.h, and it's easier to start with a base and
clean up than from scratch.
so i'm definitely not comfortable dropping Cliff's completely from the
file and the log (which means he needs to be readded and made sure to
be retained in all the other ADAU drivers going forward), and i'm not
entirely sold about changing of the Author field in the git commit.
don't get me wrong ... i'm not a fanboi of Cliff or something, i just
think credit is due to him for his work.
-mike
--
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