From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Raj Kumar Bhagat <raj.bhagat@oss.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: [PATCH ath-next v3 1/6] dt-bindings: net: wireless: add ath12k wifi device IPQ5424
Date: Tue, 31 Mar 2026 08:44:54 -0700 [thread overview]
Message-ID: <cf1d8b38-a5d0-46c6-8016-b366637d6c72@oss.qualcomm.com> (raw)
In-Reply-To: <0de0574a-04ce-45d0-946d-5fdc1a7b8181@kernel.org>
On 3/31/2026 7:42 AM, Krzysztof Kozlowski wrote:
> On 31/03/2026 16:23, Jeff Johnson wrote:
>> On 3/31/2026 12:24 AM, Krzysztof Kozlowski wrote:
>>> On Tue, Mar 31, 2026 at 02:09:06AM +0530, Raj Kumar Bhagat wrote:
>>>> $id: http://devicetree.org/schemas/net/wireless/qcom,ipq5332-wifi.yaml#
>>>> @@ -17,6 +17,7 @@ properties:
>>>> compatible:
>>>> enum:
>>>> - qcom,ipq5332-wifi
>>>> + - qcom,ipq5424-wifi
>>>
>>> No, use previous patch.
>>>
>>> I am annoyed that you keep making changes even for such trivialities and
>>> require re-review from the community. Previous patch was correct. This
>>> one doing whatever you want to do in copyrights is too much. You don't
>>> change copyrights just because you wrote one device model.
>>
>> Krzysztof,
>>
>> FYI here is the guidance I received from Qualcomm legal (links to internal
>> documentation, removed -- I've forwarded the entire e-mail to your Qualcomm
>> mailbox):
>
> As I explained already more than once, legal can engage in open source
> discussions directly. I am not going to discuss with them via proxies.
>
>>
>> ... Repos under copyleft license [...] QTI copyright must be added when we
>> make significant changes.
>>
>> ... Repos under friendly license (BSD, Apache, MIT, ...) [...] QTI copyright
>> must be added for any changes, not just significant ones.
>>
>> ... under the regular QUIC to QTI open-source copyright transitioning [...]
>> all QUIC Copyright instances should be replaced with year-less QTI OSS Copyright.
>>
>> I'll follow up with them on this case where there is a dual-license file.
>
> You nicely removed the quote where they ask to follow what the upstream
> maintainer asks for. So as one of the maintainers I ask not to change
> it, because it is churn and pointless waste of my time.
Although I feel the latest patch correctly represents Qualcomm legal guidance,
I'm not going to insist upon the copyright change.
/jeff
next prev parent reply other threads:[~2026-03-31 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 20:39 [PATCH ath-next v3 0/6] wifi: ath12k: Enable IPQ5424 AHB WiFi device Raj Kumar Bhagat
2026-03-30 20:39 ` [PATCH ath-next v3 1/6] dt-bindings: net: wireless: add ath12k wifi device IPQ5424 Raj Kumar Bhagat
2026-03-31 7:24 ` Krzysztof Kozlowski
2026-03-31 14:23 ` Jeff Johnson
2026-03-31 14:42 ` Krzysztof Kozlowski
2026-03-31 15:44 ` Jeff Johnson [this message]
2026-03-31 19:23 ` Raj Kumar Bhagat
2026-03-30 20:39 ` [PATCH ath-next v3 2/6] wifi: ath12k: Add ath12k_hw_params for IPQ5424 Raj Kumar Bhagat
2026-03-30 20:39 ` [PATCH ath-next v3 3/6] wifi: ath12k: add ath12k_hw_version_map entry " Raj Kumar Bhagat
2026-03-30 20:39 ` [PATCH ath-next v3 4/6] wifi: ath12k: add ath12k_hw_regs " Raj Kumar Bhagat
2026-03-30 20:39 ` [PATCH ath-next v3 5/6] wifi: ath12k: Add CE remap hardware parameters " Raj Kumar Bhagat
2026-03-30 20:39 ` [PATCH ath-next v3 6/6] wifi: ath12k: Enable IPQ5424 WiFi device support Raj Kumar Bhagat
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=cf1d8b38-a5d0-46c6-8016-b366637d6c72@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=raj.bhagat@oss.qualcomm.com \
--cc=robh@kernel.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