linux-kernel - Re: [PATCH 3/4] arm64: dts: Move NS2 clock DT nodes to separate DT file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 29 Mar 2016 13:27:43 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	Markus Mayer <markus.mayer@...adcom.com>,
	Anup Patel <anup.patel@...adcom.com>
CC:	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	Device Tree <devicetree@...r.kernel.org>,
	Linux ARM Kernel <linux-arm-kernel@...ts.infradead.org>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>, Ray Jui <rjui@...adcom.com>,
	Scott Branden <sbranden@...adcom.com>,
	Jon Mason <jon.mason@...adcom.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH 3/4] arm64: dts: Move NS2 clock DT nodes to separate DT file

On March 29, 2016 11:47:10 AM PDT, Markus Mayer <markus.mayer@...adcom.com> wrote:
>> diff --git a/arch/arm64/boot/dts/broadcom/ns2.dtsi
>b/arch/arm64/boot/dts/broadcom/ns2.dtsi
>> index 940ed52..0a92a68 100644
>> --- a/arch/arm64/boot/dts/broadcom/ns2.dtsi
>> +++ b/arch/arm64/boot/dts/broadcom/ns2.dtsi
>> @@ -1,7 +1,7 @@
>>  /*
>>   *  BSD LICENSE
>>   *
>> - *  Copyright(c) 2015 Broadcom Corporation.  All rights reserved.
>> + *  Copyright (c) 2015 Broadcom.  All rights reserved.
>
>I am thinking the 2015 copyright notice should remain as is and a new
>2016 notice should be added underneath.
>
>Copyright (c) 2016 Broadcom.  All rights reserved.

IANAL, but the directions given by our management on how to deal with these were clear, and they mentioned the use of Broadcom as holder name here irrespective of the time frame.

-- 
Florian