From: Chris Ball <cjb@laptop.org>
To: Philip Rakity <prakity@marvell.com>
Cc: "<r66093@freescale.com> <r66093@freescale.com>"
<r66093@freescale.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Jerry Huang <Chang-Ming.Huang@freescale.com>
Subject: Re: [PATCH 1/4] SDHCI: add sdhci_get_cd callback to detect the card
Date: Tue, 13 Dec 2011 13:06:17 -0500 [thread overview]
Message-ID: <m2aa6wl52e.fsf@bob.laptop.org> (raw)
In-Reply-To: <F2681397-0395-43F7-902F-9A575EDD843B@marvell.com> (Philip Rakity's message of "Mon, 5 Dec 2011 10:48:50 -0800")
Hi,
On Mon, Dec 05 2011, Philip Rakity wrote:
>> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
>> index 6d8eea3..66afd82 100644
>> --- a/drivers/mmc/host/sdhci.c
>> +++ b/drivers/mmc/host/sdhci.c
>> @@ -2,6 +2,7 @@
>> * linux/drivers/mmc/host/sdhci.c - Secure Digital Host Controller
>> Interface driver
>> *
>> * Copyright (C) 2005-2008 Pierre Ossman, All Rights Reserved.
>> + * Copyright (C) 2011 Freescale Semiconductor Inc.
>
>
> Lots of folks have made mods to this code and they have not added a
> copyright name.
> What is the rule Chris ?
You're right that many people have added far more significant changes
than this without adding a copyright string, so we shouldn't add this
one now.
In general, though, I'd say that the rule is that you may (but are not
required to) add a copyright string if your change is reasonably large
and non-obvious/non-boilerplate. I don't think the copyright string
means anything -- copyright is implicit in the authorship history which
Git preserves -- but I'm not a lawyer. Having your name in the
copyright string may make enforcing the GPL for that driver slightly
easier for you, so for that reason I'm glad Pierre added himself.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-12-13 18:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 9:23 [PATCH 1/4] SDHCI: add sdhci_get_cd callback to detect the card r66093
2011-12-05 9:23 ` [PATCH 2/4] MMC/SD: Add callback function to detect card r66093
2011-12-05 9:23 ` [PATCH 3/4] MMC/core: Make sure the power is up, when detect the card r66093
2011-12-05 9:23 ` [PATCH 4/4] MMC/core: Add f_min to mmc_power_on() r66093
2011-12-05 15:48 ` [PATCH 3/4] MMC/core: Make sure the power is up, when detect the card Ulf Hansson
2011-12-06 5:40 ` Huang Changming-R66093
2011-12-07 9:04 ` Linus Walleij
2011-12-09 3:16 ` Huang Changming-R66093
2011-12-09 10:03 ` [PATCH 2/4] MMC/SD: Add callback function to detect card Adrian Hunter
2011-12-13 7:25 ` Huang Changming-R66093
2011-12-13 8:01 ` Adrian Hunter
2011-12-13 8:26 ` Huang Changming-R66093
2011-12-13 8:54 ` Adrian Hunter
2011-12-13 9:55 ` Huang Changming-R66093
2011-12-13 10:26 ` Adrian Hunter
2011-12-14 2:21 ` Huang Changming-R66093
2011-12-05 11:25 ` [PATCH 1/4] SDHCI: add sdhci_get_cd callback to detect the card Dong, Chuanxiao
2011-12-06 5:43 ` Huang Changming-R66093
2011-12-05 18:48 ` Philip Rakity
2011-12-06 5:35 ` Huang Changming-R66093
2011-12-13 18:06 ` Chris Ball [this message]
2011-12-14 2:31 ` Huang Changming-R66093
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=m2aa6wl52e.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=Chang-Ming.Huang@freescale.com \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.com \
--cc=r66093@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).