linux-kernel - Re: [PATCH] arm64: zynqmp: Switch to amd.com emails

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]

Message-ID: <c03d5e9a-7f04-5a26-8e6f-635c526bc859@amd.com>
Date:   Tue, 16 May 2023 19:20:06 +0200
From:   Michal Simek <michal.simek@....com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        linux-kernel@...r.kernel.org, monstr@...str.eu,
        michal.simek@...inx.com, git@...inx.com
Cc:     Amit Kumar Mahapatra <amit.kumar-mahapatra@...inx.com>,
        Andrew Davis <afd@...com>, Conor Dooley <conor+dt@...nel.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Harini Katakam <harini.katakam@....com>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Michael Grzeschik <m.grzeschik@...gutronix.de>,
        Michael Tretter <m.tretter@...gutronix.de>,
        Parth Gajjar <parth.gajjar@....com>,
        Piyush Mehta <piyush.mehta@...inx.com>,
        Rob Herring <robh+dt@...nel.org>,
        Robert Hancock <robert.hancock@...ian.com>,
        Srinivas Neeli <srinivas.neeli@...inx.com>,
        Tanmay Shah <tanmay.shah@....com>,
        Vishal Sagar <vishal.sagar@....com>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm64: zynqmp: Switch to amd.com emails



On 5/16/23 18:05, Krzysztof Kozlowski wrote:
> On 16/05/2023 15:41, Michal Simek wrote:
>> Update my and DPs email address to match current setup.
>>
>> Signed-off-by: Michal Simek <michal.simek@....com>
>> ---
>>
>>   arch/arm64/boot/dts/xilinx/avnet-ultra96-rev1.dts      | 5 +++--
>>   arch/arm64/boot/dts/xilinx/zynqmp-clk-ccf.dtsi         | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revA.dtso   | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revB.dtso   | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-sm-k26-revA.dts      | 5 +++--
>>   arch/arm64/boot/dts/xilinx/zynqmp-smk-k26-revA.dts     | 5 +++--
>>   arch/arm64/boot/dts/xilinx/zynqmp-zc1232-revA.dts      | 5 +++--
>>   arch/arm64/boot/dts/xilinx/zynqmp-zc1254-revA.dts      | 7 ++++---
>>   arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm015-dc1.dts | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm016-dc2.dts | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm017-dc3.dts | 5 +++--
>>   arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm018-dc4.dts | 5 +++--
>>   arch/arm64/boot/dts/xilinx/zynqmp-zc1751-xm019-dc5.dts | 7 ++++---
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu100-revC.dts      | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.0.dts    | 5 +++--
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.1.dts    | 5 +++--
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revA.dts      | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revB.dts      | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu104-revA.dts      | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu104-revC.dts      | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu106-revA.dts      | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu111-revA.dts      | 2 +-
>>   arch/arm64/boot/dts/xilinx/zynqmp-zcu1275-revA.dts     | 7 ++++---
>>   arch/arm64/boot/dts/xilinx/zynqmp.dtsi                 | 5 +++--
>>   24 files changed, 51 insertions(+), 39 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/xilinx/avnet-ultra96-rev1.dts b/arch/arm64/boot/dts/xilinx/avnet-ultra96-rev1.dts
>> index 88aa06fa78a8..1495272e5668 100644
>> --- a/arch/arm64/boot/dts/xilinx/avnet-ultra96-rev1.dts
>> +++ b/arch/arm64/boot/dts/xilinx/avnet-ultra96-rev1.dts
>> @@ -2,9 +2,10 @@
>>   /*
>>    * dts file for Avnet Ultra96 rev1
>>    *
>> - * (C) Copyright 2018, Xilinx, Inc.
>> + * (C) Copyright 2018 - 2022, Xilinx, Inc.
>> + * (C) Copyright 2022 - 2023, Advanced Micro Devices, Inc.
> 
> I think these should be split. Your commit suggests only update to email
> but you add copyrights. While email change is trivial, 

ok

> the copyright
> change is not (at least not for everyone and for every legal system).
> 
> What's more, there were no changes to this file after 2018. What
> copyrighted work did you add in 2019, 2020, 2021, 2022 and 2023? For
> this file clear: NAK

All these files are regularly updated in soc vendor tree. I can do stats to 
double check every file but I am quite sure that every year we did touch these 
files at least with single line of change (and not just copyright update).
It means at least it is not big concern from me that we created file in 2018 and 
then touch them this year.
The question is if this is valid argument which could be accepted upstream.
TBH I don't mind too much because primary reason for this patch was updating my 
email address.

> 
> Same concerns for most of other files.

Sure

Thanks,
Michal