From: David Daney <ddaney.cavm@gmail.com>
To: "Hill, Steven" <sjhill@mips.com>
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH 00/33] Cleanup firmware support across multiple platforms.
Date: Tue, 26 Jun 2012 11:41:29 -0700 [thread overview]
Message-ID: <4FEA0259.5030005@gmail.com> (raw)
In-Reply-To: <31E06A9FC96CEC488B43B19E2957C1B8011469833E@exchdb03.mips.com>
On 06/26/2012 11:34 AM, Hill, Steven wrote:
> Jonas,
>
> Did you read the COPYING file of the kernel source tree? I'm pretty sure it states "or later" in the text. Therefore, I believe that my changes to the headers are alright.
>
Steve,
Why subject yourself to all these questions about changing the copyright
messages that the original authors put in there?
Would it be a problem for you to leave them intact?
I think you would have better luck splitting you patches like this:
1) A set that changes the code and only adds your own copyright for
files where you do major work.
2) A set that removes other people's copyright text.
Applying #1 should then be a no-brainer.
#2 might be more difficult, but if you were persistent, you might
eventually get it merged.
David Daney
next prev parent reply other threads:[~2012-06-26 18:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 4:41 [PATCH 00/33] Cleanup firmware support across multiple platforms Steven J. Hill
2012-06-26 4:41 ` [PATCH 01/33] MIPS: Add environment variable processing code to firmware library Steven J. Hill
2012-06-26 18:47 ` Hill, Steven
2012-06-26 4:41 ` [PATCH 02/33] MIPS: Alchemy: Cleanup firmware support for Alchemy platforms Steven J. Hill
2012-06-26 4:41 ` [PATCH 03/33] MIPS: Alchemy: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 04/33] MIPS: AR7: Cleanup firmware support for the AR7 platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 05/33] MIPS: AR7: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 14:29 ` Florian Fainelli
2012-06-28 6:45 ` Imre Kaloz
2012-06-28 14:06 ` Hill, Steven
2012-06-26 4:41 ` [PATCH 06/33] MIPS: ath79: Cleanup firmware support for the ath79 platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 07/33] MIPS: Cobalt: Cleanup firmware support for the Cobalt platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 08/33] MIPS: Cobalt: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 09/33] MIPS: Emma: Cleanup firmware support for the Emma platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 10/33] MIPS: Emma: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 11/33] MIPS: jz4740: Cleanup firmware support for the JZ4740 platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 12/33] MIPS: jz4740: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 13/33] MIPS: lantiq: Cleanup firmware support for the lantiq platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 14/33] MIPS: lantiq: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 15/33] MIPS: Lasat: Cleanup firmware support for the Lasat platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 16/33] MIPS: Lasat: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 17/33] MIPS: Loongson: Cleanup firmware support for the Loongson platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 18/33] MIPS: Loongson: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 19/33] MIPS: Malta: Cleanup firmware support for the Malta platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 20/33] MIPS: Malta: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 21/33] MIPS: Netlogic: Cleanup firmware support for the XLR platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 22/33] MIPS: MSP71xx, Yosemite: Cleanup firmware support for PMC platforms Steven J. Hill
2012-06-26 4:41 ` [PATCH 23/33] MIPS: MSP71xx, Yosemite: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 24/33] MIPS: PNX83xx, PNX8550: Cleanup firmware support for PNX platforms Steven J. Hill
2012-06-26 4:41 ` [PATCH 25/33] MIPS: PNX83xx, PNX8550: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 26/33] MIPS: PowerTV: Cleanup firmware support for PowerTV platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 27/33] MIPS: PowerTV: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 28/33] MIPS: RB532: Cleanup firmware support for RB532 platform Steven J. Hill
2012-06-26 4:41 ` [PATCH 29/33] MIPS: RB532: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 30/33] MIPS: txx9: Cleanup firmware support for txx9 platforms Steven J. Hill
2012-06-26 4:41 ` [PATCH 31/33] MIPS: txx9: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 4:41 ` [PATCH 32/33] MIPS: vr41xx: Cleanup firmware support for vr41xx platforms Steven J. Hill
2012-06-26 4:41 ` [PATCH 33/33] MIPS: vr41xx: Cleanup files effected by firmware changes Steven J. Hill
2012-06-26 9:25 ` [PATCH 00/33] Cleanup firmware support across multiple platforms Florian Fainelli
2012-06-26 15:11 ` Jonas Gorski
2012-06-26 18:34 ` Hill, Steven
2012-06-26 18:41 ` David Daney [this message]
2012-06-26 19:35 ` Hill, Steven
2012-06-26 18:47 ` Jonas Gorski
2012-06-26 18:52 ` Hill, Steven
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=4FEA0259.5030005@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=sjhill@mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.