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: <a96f56b6-0959-b672-0521-e44e5d9f6fbc@linaro.org>
Date:   Wed, 13 Apr 2022 14:21:54 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Rohit Agarwal <quic_rohiagar@...cinc.com>, agross@...nel.org,
        bjorn.andersson@...aro.org, djakov@...nel.org, robh+dt@...nel.org,
        krzk+dt@...nel.org
Cc:     manivannan.sadhasivam@...aro.org, linux-arm-msm@...r.kernel.org,
        linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: Add Qualcomm SDX65 DT
 bindings

On 13/04/2022 14:14, Rohit Agarwal wrote:
> 
> On 4/13/2022 12:03 PM, Krzysztof Kozlowski wrote:
>> On 13/04/2022 08:29, Rohit Agarwal wrote:
>>> On 4/12/2022 2:52 PM, Krzysztof Kozlowski wrote:
>>>> On 12/04/2022 07:07, Rohit Agarwal wrote:
>>>>> Add interconnect IDs for Qualcomm SDX65 platform.
>>>>>
>>>>> Signed-off-by: Rohit Agarwal <quic_rohiagar@...cinc.com>
>>>> (...)
>>>>
>>>>> diff --git a/include/dt-bindings/interconnect/qcom,sdx65.h b/include/dt-bindings/interconnect/qcom,sdx65.h
>>>>> new file mode 100644
>>>>> index 0000000..8d02c79
>>>>> --- /dev/null
>>>>> +++ b/include/dt-bindings/interconnect/qcom,sdx65.h
>>>>> @@ -0,0 +1,67 @@
>>>>> +/* SPDX-License-Identifier: GPL-2.0-only */
>>>> Is it possible to license it the same as bindings (GPL-2.0 OR BSD-2-Clause)?
>>> The qcom related code are marked as GPL 2.0 license
>> This I see here, unless you meant some other qcom related code?
> 
> Yes, I meant the other codes as well because most of them I see (for eg. 
> sdx55) have added only GPL 2.0.

Happens, maybe no one pointed out this. The bindings, including headers
because these are part of bindings, are expected to have (GPL-2.0 OR
BSD-2-Clause) license. Just because some bindings or some binding
headers have GPL-2.0, is not a justification that wrong license should
be used.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ