public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: Andres Salomon <dilinger@queued.net>
Cc: rpurdie@rpsys.net, linux-geode@lists.infradead.org,
	const@mimas.ru, linux-kernel@vger.kernel.org,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: Feedback please: [PATCH] leds: New PCEngines Alix LED driver using gpio interface
Date: Thu, 17 Mar 2011 17:04:25 +0000	[thread overview]
Message-ID: <4D823F19.4070700@wildgooses.com> (raw)
In-Reply-To: <20110317084328.41831b4c@debxo>

Hi Andres

Thanks for your feedback!

>> Additionally it relies on parts of the patch: 7f131cf3ed
>> by: Daniel Mack <daniel@caiaq.de> to perform detection of the Alix
>> board

..
>> - * Copyright (C) 2008 Constantin Baranov <const@mimas.ru>
> 
> This copyright line should not be removed, so long as parts of the
> original driver (such as alix_present) remain.

Thanks for guidance here.

Can I ask for further thought on this - there is very close to zero
original driver present, and although I had better do some more diffs to
be sure, I think you would see the only common code was the #includes, a
"force" param and a few other { }s?

I did deliberately reuse the "alix_present" function, but this appears
to be written by Daniel Mack and contributed in patch: 7f131cf3ed -
however, Daniel is not listed in the current copyright statement on the
module (I did copy him and Constantin in on this patch so that either
might object?).  Also I have tried to show this code attribution in the
commit statement?

I have also noted in the code that this is based on leds-net5501.c - is
this a sufficient and normal attribution?

Can someone offer a final "ruling" as to how I should state the
copyright line given that the code was written by taking the
leds-net5501.c skeleton and approximately applying the commit
7f131cf3ed, to give the current code?

Many thanks

Ed W

  parent reply	other threads:[~2011-03-17 17:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D81D7FD.1040602@wildgooses.com>
2011-03-17 15:43 ` Feedback please: [PATCH] leds: New PCEngines Alix LED driver using gpio interface Andres Salomon
2011-03-17 16:08   ` Grant Likely
2011-03-17 17:24     ` Ed W
2011-03-17 17:52       ` Andres Salomon
2011-03-17 17:59         ` Ed W
2011-03-17 18:17           ` Grant Likely
2011-03-18 18:12             ` kernel
2011-03-18 18:32               ` Ed W
2011-03-18 22:48                 ` Grant Likely
2011-03-19 16:51                   ` [PATCH] leds: New PCEngines Alix system driver (enables LEDs via gpio interface) kernel
2011-03-19 17:21                     ` Ed W
2011-03-24  3:52                     ` Grant Likely
2011-03-19 17:46                   ` [PATCH] gpio: Show explicit dependency between GPIO_CS5535 and MFD_CS5535 kernel
2011-03-19 19:59                     ` Andres Salomon
2011-03-17 18:22           ` Feedback please: [PATCH] leds: New PCEngines Alix LED driver using gpio interface Andres Salomon
2011-03-17 18:12       ` Grant Likely
2011-03-17 17:04   ` Ed W [this message]
2011-03-17 18:07     ` Grant Likely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D823F19.4070700@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=const@mimas.ru \
    --cc=dilinger@queued.net \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-geode@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox