[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4559a710-8b4f-4988-b063-40486fe0ffe2@kernel.org>
Date: Sun, 20 Jul 2025 14:18:19 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Bjorn Andersson <andersson@...nel.org>
Cc: Pankaj Patil <pankaj.patil@....qualcomm.com>, sboyd@...nel.org,
mturquette@...libre.com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, quic_rjendra@...cinc.com, taniya.das@....qualcomm.com,
linux-clk@...r.kernel.org, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 7/7] clk: qcom: gcc: Add support for Global Clock
Controller
On 20/07/2025 05:46, Bjorn Andersson wrote:
> On Wed, Jul 16, 2025 at 06:28:15PM +0200, Krzysztof Kozlowski wrote:
>> On 16/07/2025 17:20, Pankaj Patil wrote:
> [..]
>>> diff --git a/drivers/clk/qcom/gcc-glymur.c b/drivers/clk/qcom/gcc-glymur.c
>>> new file mode 100644
>>> index 000000000000..a1a6da62ed35
>>> --- /dev/null
>>> +++ b/drivers/clk/qcom/gcc-glymur.c
>>> @@ -0,0 +1,8623 @@
>>> +// SPDX-License-Identifier: GPL-2.0-only
>>> +/*
>>> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
>>
>> Missing date.
>>
>
> Per updated company guidelines we don't want a year here. Please let us
> know if you have any concerns with this.
>
I remember the guidelines and they were about publishing your code, not
about contributing to open-source projects. And whatever you have
internally does not cover us at all. You can have internal guideline
saying you need to buy me a beer or I need to buy you a beer. Does not
matter.
That above copyright statement without date does not adhere to expected
format. Explanation how this should be written:
https://www.gnu.org/licenses/gpl-howto.en.html#copyright-notice
The GPL-2.0 license in the kernel also uses date:
"Copyright (C) <year> <name of author> "
There is no option without date in the license or GPL faq. I am not a
lawyer, so no clue whether this is what we want, but I also should not
be my task to figure out whether different copyright statement is okay
or not. It's your burden.
Or drop the Copyright statement complete to avoid any questions.
Best regards,
Krzysztof
Powered by blists - more mailing lists