From: bryanh@codeaurora.org (Bryan Huntsman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/5] ARM: qcom: Split Qualcomm support into legacy and multiplatform
Date: Tue, 11 Feb 2014 10:10:20 -0800 [thread overview]
Message-ID: <52FA678C.6050000@codeaurora.org> (raw)
In-Reply-To: <392A0D29-65A3-403D-B645-DB74A1897170@codeaurora.org>
On 02/11/2014 07:13 AM, Kumar Gala wrote:
>>> * Copyright (c) 2010, Code Aurora Forum. All rights reserved.
>>> >> + * Copyright (c) 2014 The Linux Foundation. All rights reserved.
>> >
>> > We should replace the Code Aurora Forum copyright with Linux
>> > Foundation here.
> Is this something we?ve been doing? Its normally bad form to make such changes, but I don?t know what the details re when LF took over CAF w/regards to something like Copyright.
>
> - k
Yes, the line should read:
- * Copyright (c) 2010, Code Aurora Forum. All rights reserved.
+ * Copyright (c) 2010,2014 The Linux Foundation. All rights reserved.
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-02-11 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 22:24 [PATCH v3 0/5] Split mach-msm into legacy and mach-qcom (multiplatform) Kumar Gala
2014-02-06 22:24 ` [PATCH v3 1/5] ARM: msm: kill off hotplug.c Kumar Gala
2014-02-06 22:24 ` [PATCH v3 2/5] clocksource: qcom: Move clocksource code out of mach-msm Kumar Gala
2014-02-11 5:38 ` Stephen Boyd
2014-02-06 22:24 ` [PATCH v3 3/5] ARM: qcom: Split Qualcomm support into legacy and multiplatform Kumar Gala
2014-02-08 3:26 ` Stephen Boyd
2014-02-11 15:13 ` Kumar Gala
2014-02-11 18:10 ` Bryan Huntsman [this message]
2014-02-06 22:24 ` [PATCH v3 4/5] clocksource: qcom: split building of legacy vs multiplatform support Kumar Gala
2014-02-06 22:24 ` [PATCH v3 5/5] ARM: qcom: Rename various msm prefixed functions to qcom Kumar Gala
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=52FA678C.6050000@codeaurora.org \
--to=bryanh@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).