From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Kiran Venkatappa <quic_kiranv@quicinc.com>,
ath12k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath12k-ng 03/13] wifi: ath12k: Move Wi-Fi 7 WMI configuration to dedicated file
Date: Wed, 13 Aug 2025 11:06:21 -0700 [thread overview]
Message-ID: <bce51392-d5f1-40a2-ae22-58df01b993e7@oss.qualcomm.com> (raw)
In-Reply-To: <2025081320-coastal-graded-40a2@gregkh>
On 8/13/2025 9:24 AM, Greg Kroah-Hartman wrote:
> On Wed, Aug 13, 2025 at 06:00:44PM +0200, Krzysztof Kozlowski wrote:
>> On 13/08/2025 17:43, Jeff Johnson wrote:
>>> On 8/12/2025 10:52 PM, Krzysztof Kozlowski wrote:
>>>> On 12/08/2025 19:09, Kiran Venkatappa wrote:
>>>>> +}
>>>>> diff --git a/drivers/net/wireless/ath/ath12k/wmi_wifi7.h b/drivers/net/wireless/ath/ath12k/wmi_wifi7.h
>>>>> new file mode 100644
>>>>> index 0000000000000000000000000000000000000000..1514e3e8d4cb65d3d95d95a1c1593a7b66abcf58
>>>>> --- /dev/null
>>>>> +++ b/drivers/net/wireless/ath/ath12k/wmi_wifi7.h
>>>>> @@ -0,0 +1,15 @@
>>>>> +/* SPDX-License-Identifier: BSD-3-Clause-Clear */
>>>>> +/*
>>>>> + * Copyright (c) 2018-2021 The Linux Foundation. All rights reserved.
>>>>> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
>>>>
>>>> Don't rewrite the copyrights. Original file had different one. GPL FAQ
>>>> also EXPLICITLY asks for date in copyrights and does not allow one
>>>> without the date.
>>>>
>>>> (and before you bring internal qcom regulations, let me remind that they
>>>> do not matter. we discussed this in other thread)
>>>
>>> Wi-Fi team wasn't party to the other thread, and this series was following the
>>> legal guidance we were given. I'm circling with the core kernel team and the
>>> legal team to make sure your concerns are resolved.
>>
>> +Cc Greg,
>
> Oops, I just responded to this issue elsewhere.
>
>> Please follow legal guidance expressed in:
>> https://www.gnu.org/licenses/gpl-howto.en.html#copyright-notice
>>
>> and the license you agreed by signing of the patch:
>> LICENSES/preferred/GPL-2.0:
>>
>> "Copyright (C) <year> <name of author> "
>> ...
>> "... publish on each copy an appropriate
>> copyright notice and disclaimer of warranty;"
>
> Nope, we do NOT force the FSF's legal intrepretation of copyright marks
> on any company at all. It's up to the copyright holders themselves for
> how they wish to mark the copyright, if at all.
>
> And really, Qualcomm is a company that is run by lawyers, they know what
> they want to do for whatever reason that might be...
>
>> Just to remind - you as author sign off your patch, not your legal team.
>
> Agreed, but in some cases, I have forced legal teams to sign off on
> patches, so don't rule that out :)
Thanks for the clarification, Greg.
Just for reference, the guidance we received follows. In that guidance:
- LF means Linux Foundation, the entity to which Qualcomm assigned copyright
when open source development was being done as Code Aurora Forum (though
December 2021)
- QuIC means Qualcomm Innovation Center, the open source entity used from
December 2021 until March 2025.
- QTI means Qualcomm Technologies, Inc., the entity now being used for open
source contributions.
Guidance:
1. Should existing QuIC copyright be left alone or absorbed into the added QTI
copyright text?
Yes, all QuIC copyright years should be absorbed. Replace the QuIC copyrights
with the QTI copyright. Leave LF and other 3rd party copyrights alone.
2. When we are creating new file in open source, if it is copied/derived from
existing QUIC authored open source file, should we retain the QUIC markings?
No, the QuIC copyright years should be absorbed into the year-less QTI copyright.
3. Is there any use case where we MUST keep the QuIC copyright?
No, all projects can move to using QTI copyright.
/jeff
next prev parent reply other threads:[~2025-08-13 19:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 17:09 [PATCH ath12k-ng 00/13] wifi: ath12k: Ath12k modularization changes Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 01/13] wifi: ath12k: Restructure PCI code to common and Wi-Fi 7 specific logic Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 02/13] wifi: ath12k: Move Copy Engine configuration to Wi-Fi 7 specific file Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 03/13] wifi: ath12k: Move Wi-Fi 7 WMI configuration to dedicated file Kiran Venkatappa
2025-08-13 5:52 ` Krzysztof Kozlowski
2025-08-13 15:43 ` Jeff Johnson
2025-08-13 16:00 ` Krzysztof Kozlowski
2025-08-13 16:24 ` Greg Kroah-Hartman
2025-08-13 18:06 ` Jeff Johnson [this message]
2025-08-12 17:09 ` [PATCH ath12k-ng 04/13] wifi: ath12k: Move Wi-Fi 7 MHI " Kiran Venkatappa
2025-08-13 5:52 ` Krzysztof Kozlowski
2025-08-12 17:09 ` [PATCH ath12k-ng 05/13] wifi: ath12k: Rename hw.c to Wi-Fi 7 specific implementation file Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 06/13] wifi: ath12k: Rename ahb_hif_ops to reflect generic usage Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 07/13] wifi: ath12k: Restructure ahb.c into common and Wi-Fi 7 specific modules Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 08/13] wifi: ath12k: Move Wi-Fi 7 specific init routines to dedicated file Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 09/13] wifi: ath12k: Move hw_init invocation to target-specific probe Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 10/13] wifi: ath12k: Modularize driver into common and Wi-Fi 7 specific components Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 11/13] wifi: ath12k: Rename ath12k_* symbols to ath12k_wifi7_* for clarity Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 12/13] wifi: ath12k: Remove HAL defines from shared PCI code Kiran Venkatappa
2025-08-12 17:09 ` [PATCH ath12k-ng 13/13] wifi: ath12k: Remove HAL define dependencies from shared AHB code Kiran Venkatappa
2025-08-20 4:50 ` [PATCH ath12k-ng 00/13] wifi: ath12k: Ath12k modularization changes Vasanthakumar Thiagarajan
2025-08-20 7:11 ` Baochen Qiang
2025-08-20 20:57 ` Jeff Johnson
2025-08-21 1:46 ` Baochen Qiang
2025-08-20 21:44 ` Jeff Johnson
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=bce51392-d5f1-40a2-ae22-58df01b993e7@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_kiranv@quicinc.com \
/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