From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/7] brcm80211: switch common header files to using SPDX license identifier
Date: Thu, 23 May 2019 12:17:10 +0300 [thread overview]
Message-ID: <871s0pedih.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <f4d582e8-3d65-959f-78bd-88b7c47131a5@broadcom.com> (Arend Van Spriel's message of "Tue, 21 May 2019 10:11:28 +0200")
Arend Van Spriel <arend.vanspriel@broadcom.com> writes:
> On 5/20/2019 6:54 PM, Kalle Valo wrote:
>> Arend Van Spriel <arend.vanspriel@broadcom.com> writes:
>>
>>> On 5/16/2019 10:57 PM, Arend Van Spriel wrote:
>>>> On 5/16/2019 2:04 PM, Arend van Spriel wrote:
>>>>> With ISC license text in place under the LICENSES folder switch
>>>>> to using the SPDX license identifier to refer to the ISC license.
>>>>
>>>> Hi Kalle,
>>>>
>>>> Given the feedback on checkpatch (or spdxcheck) failures let me
>>>> respin this series.
>>>
>>> Actually let's *NOT* respin and leave this series as is and ignore the
>>> warning for the header files as Thomas wrote in his response: " So we
>>> can fixup the documentation and allow // style for headers as well.".
>>
>> What about patch 3, should I drop that patch? Wasn't the conclusion that
>> you need separately change led.c?
>
> Okay. Let's do that.
Dropped it now.
> Or do you want me to resend the whole series without patch 3?
If the series applies without patch 3 (and I assume it does) no need to
resend the whole series.
--
Kalle Valo
next prev parent reply other threads:[~2019-05-23 9:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 12:04 [PATCH 0/7] brcm80211: SPDX tags and Kconfig cleanup Arend van Spriel
2019-05-16 12:04 ` [PATCH 1/7] brcm80211: switch common header files to using SPDX license identifier Arend van Spriel
2019-05-16 20:57 ` Arend Van Spriel
2019-05-17 18:04 ` Arend Van Spriel
2019-05-20 16:54 ` Kalle Valo
2019-05-21 8:11 ` Arend Van Spriel
2019-05-23 9:17 ` Kalle Valo [this message]
2019-05-23 10:53 ` Arend Van Spriel
2019-05-28 12:24 ` Kalle Valo
2019-05-16 12:04 ` [PATCH 2/7] brcmutil: switch source " Arend van Spriel
2019-05-16 12:04 ` [PATCH 3/7] brcmsmac: " Arend van Spriel
2019-05-16 17:31 ` Greg Kroah-Hartman
2019-05-16 19:45 ` Arend Van Spriel
2019-05-16 20:01 ` Greg Kroah-Hartman
2019-05-16 20:15 ` Arend Van Spriel
2019-05-17 18:07 ` Rafał Miłecki
2019-05-17 18:22 ` Arend Van Spriel
2019-07-08 10:07 ` Arend Van Spriel
2019-07-08 10:41 ` Greg Kroah-Hartman
2019-05-23 9:16 ` Kalle Valo
2019-05-16 12:04 ` [PATCH 4/7] brcmsmac: switch phy " Arend van Spriel
2019-05-16 12:04 ` [PATCH 5/7] brcmfmac: switch " Arend van Spriel
2019-05-16 12:04 ` [PATCH 6/7] brcmfmac: use separate Kconfig file for brcmfmac Arend van Spriel
2019-05-16 12:04 ` [PATCH 7/7] brcm80211: select WANT_DEV_COREDUMP conditionally " Arend van Spriel
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=871s0pedih.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).