From: Kalle Valo <kvalo@kernel.org>
To: Josh Boyer <jwboyer@kernel.org>
Cc: Christian Lamparter <chunkeey@gmail.com>,
Linux Firmware <linux-firmware@kernel.org>,
ath10k@lists.infradead.org,
Linux Wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@qca.qualcomm.com>
Subject: Re: [PATCH v2 1/5] ath10k: QCA4019 hw1.0: update board-2.bin
Date: Sat, 26 Feb 2022 15:24:33 +0200 [thread overview]
Message-ID: <87sfs5squm.fsf@kernel.org> (raw)
In-Reply-To: <CA+5PVA5hPn9QDkmwJE3E7NU3hv08t416DfLvxeJFJCxWSzSCDg@mail.gmail.com> (Josh Boyer's message of "Thu, 24 Feb 2022 15:24:25 -0500")
Josh Boyer <jwboyer@kernel.org> writes:
> On Wed, Feb 23, 2022 at 2:53 PM Christian Lamparter <chunkeey@gmail.com> wrote:
>>
>> syncs linux-firmware.git with the latest releases from Kalle Valo (QCA):
>> <https://github.com/kvalo/ath10k-firmware/tree/master/QCA4019/hw1.0>
>>
>> Includes the following changes:
>> 93591ce ath10k-firmware: QCA4019 hw1.0: Add ZTE MF286D specific BDFs
>> 29b419c ath10k-firmware: QCA4019 hw1.0: Add ASUS RT-AC42U specific BDFs
>> fb4e69f ath10k-firmware: QCA4019 hw1.0: Add Linksys WHW01 v1 specific BDFs
>> ff8c56b ath10k-firmware: QCA4019 hw1.0: Add Plasma Cloud PA1200 specific BDFs
>> 89492ce ath10k-firmware: QCA4019 hw1.0: Add Plasma Cloud PA2200 specific BDFs
>> faf338c [v2] ath10k-firmware: QCA4019 hw1.0: Add Linksys MR8300 V1.0 specific BDFs
>> 725d7f6 ath10k-firmware: QCA4019 hw1.0: Add Luma WRTQ-329ACN BDFs
>> a92ca29 ath10k-firmware: QCA4019 hw1.0: Add Buffalo WTR-M2133HP specific BDFs
>> 9f771d2 ath10k-firmware: QCA4019 hw1.0: Update AVM FritzBox 4040 specific BDFs
>> a633c15 [v2] ath10k-firmware: QCA4019 hw1.0: Add Cell C RTL30VW specific BDF
>> 46a4f4a ath10k-firmware: QCA4019 hw1.0: Add Aruba AP-303 specific BDFs
>> 0e51dac ath10k-firmware: QCA4019 hw1.0: Add MobiPromo CM520-79F
>> 15f1bdd ath10k-firmware: QCA4019 hw1.0: Add Cell C RTL30VW specific BDF
>> c07b12a ath10k-firmware: QCA4019 hw1.0: Add EZVIZ CS-W3-WD1200G EUP specific BDFs
>> f688435 ath10k-firmware: QCA4018: Add D-Link DAP-2610 specific BDFs
>> b529a8b ath10k-firmware: QCA4019 hw1.0: Add AVM FRITZ!Repeater 1200 specific BDFs
>> 8f150f4 ath10k-firmware: QCA4019 hw1.0: Add EnGenius EMR5000 specific BDFs
>> 1fad4d7 ath10k-firmware: QCA4019 hw1.0: Update 8devices Habanero specific BDFs
>> 08fccb1 ath10k-firmware: QCA4019 hw1.0: Add EnGenius ENH1350EXT specific BDFs
>> 0d2493a ath10k-firmware: QCA4019 hw1.0: Add EnGenius EMD1 specific BDFs
>> 4f719af ath10k-firmware: QCA4019 hw1.0: Add EnGenius EMR3500 specific BDFs
>> e2fe755 ath10k-firmware: QCA4019 hw1.0: Add 8devices Habanero specific BDFs
>> 38ebb2d ath10k-firmware: QCA4019 hw1.0: Add EnGenius EAP2200 specific BDFs
>> bc42587 ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A42 specific BDFs
>> f305604 ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A62 specific BDFs
>>
>> Cc: Kalle Valo <kvalo@qca.qualcomm.com>
>> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
>
> Forgive me, but I have to ask. Kalle, is there a reason you aren't
> sending these or including a Signed-off-by?
I have not sent any new pull requests to linux-firmware while we are
trying to sort out the notice.txt problem discussed in the other thread:
https://lore.kernel.org/all/CA+5PVA4WEuJDB3OCKfYK-BPaccpVWd9t_au9S7MCEtpy7cdF-A@mail.gmail.com/
My plan was to send ath10k and ath11k updates once we find a solution
for the notice files. I'm guessing Christian wanted to get these board
files to linux-firmware quickly and decided to submit them directly, I
was not involved with that at all.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Josh Boyer <jwboyer@kernel.org>
Cc: Christian Lamparter <chunkeey@gmail.com>,
Linux Firmware <linux-firmware@kernel.org>,
ath10k@lists.infradead.org,
Linux Wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@qca.qualcomm.com>
Subject: Re: [PATCH v2 1/5] ath10k: QCA4019 hw1.0: update board-2.bin
Date: Sat, 26 Feb 2022 15:24:33 +0200 [thread overview]
Message-ID: <87sfs5squm.fsf@kernel.org> (raw)
In-Reply-To: <CA+5PVA5hPn9QDkmwJE3E7NU3hv08t416DfLvxeJFJCxWSzSCDg@mail.gmail.com> (Josh Boyer's message of "Thu, 24 Feb 2022 15:24:25 -0500")
Josh Boyer <jwboyer@kernel.org> writes:
> On Wed, Feb 23, 2022 at 2:53 PM Christian Lamparter <chunkeey@gmail.com> wrote:
>>
>> syncs linux-firmware.git with the latest releases from Kalle Valo (QCA):
>> <https://github.com/kvalo/ath10k-firmware/tree/master/QCA4019/hw1.0>
>>
>> Includes the following changes:
>> 93591ce ath10k-firmware: QCA4019 hw1.0: Add ZTE MF286D specific BDFs
>> 29b419c ath10k-firmware: QCA4019 hw1.0: Add ASUS RT-AC42U specific BDFs
>> fb4e69f ath10k-firmware: QCA4019 hw1.0: Add Linksys WHW01 v1 specific BDFs
>> ff8c56b ath10k-firmware: QCA4019 hw1.0: Add Plasma Cloud PA1200 specific BDFs
>> 89492ce ath10k-firmware: QCA4019 hw1.0: Add Plasma Cloud PA2200 specific BDFs
>> faf338c [v2] ath10k-firmware: QCA4019 hw1.0: Add Linksys MR8300 V1.0 specific BDFs
>> 725d7f6 ath10k-firmware: QCA4019 hw1.0: Add Luma WRTQ-329ACN BDFs
>> a92ca29 ath10k-firmware: QCA4019 hw1.0: Add Buffalo WTR-M2133HP specific BDFs
>> 9f771d2 ath10k-firmware: QCA4019 hw1.0: Update AVM FritzBox 4040 specific BDFs
>> a633c15 [v2] ath10k-firmware: QCA4019 hw1.0: Add Cell C RTL30VW specific BDF
>> 46a4f4a ath10k-firmware: QCA4019 hw1.0: Add Aruba AP-303 specific BDFs
>> 0e51dac ath10k-firmware: QCA4019 hw1.0: Add MobiPromo CM520-79F
>> 15f1bdd ath10k-firmware: QCA4019 hw1.0: Add Cell C RTL30VW specific BDF
>> c07b12a ath10k-firmware: QCA4019 hw1.0: Add EZVIZ CS-W3-WD1200G EUP specific BDFs
>> f688435 ath10k-firmware: QCA4018: Add D-Link DAP-2610 specific BDFs
>> b529a8b ath10k-firmware: QCA4019 hw1.0: Add AVM FRITZ!Repeater 1200 specific BDFs
>> 8f150f4 ath10k-firmware: QCA4019 hw1.0: Add EnGenius EMR5000 specific BDFs
>> 1fad4d7 ath10k-firmware: QCA4019 hw1.0: Update 8devices Habanero specific BDFs
>> 08fccb1 ath10k-firmware: QCA4019 hw1.0: Add EnGenius ENH1350EXT specific BDFs
>> 0d2493a ath10k-firmware: QCA4019 hw1.0: Add EnGenius EMD1 specific BDFs
>> 4f719af ath10k-firmware: QCA4019 hw1.0: Add EnGenius EMR3500 specific BDFs
>> e2fe755 ath10k-firmware: QCA4019 hw1.0: Add 8devices Habanero specific BDFs
>> 38ebb2d ath10k-firmware: QCA4019 hw1.0: Add EnGenius EAP2200 specific BDFs
>> bc42587 ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A42 specific BDFs
>> f305604 ath10k-firmware: QCA4019 hw1.0: Update OpenMesh A62 specific BDFs
>>
>> Cc: Kalle Valo <kvalo@qca.qualcomm.com>
>> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
>
> Forgive me, but I have to ask. Kalle, is there a reason you aren't
> sending these or including a Signed-off-by?
I have not sent any new pull requests to linux-firmware while we are
trying to sort out the notice.txt problem discussed in the other thread:
https://lore.kernel.org/all/CA+5PVA4WEuJDB3OCKfYK-BPaccpVWd9t_au9S7MCEtpy7cdF-A@mail.gmail.com/
My plan was to send ath10k and ath11k updates once we find a solution
for the notice files. I'm guessing Christian wanted to get these board
files to linux-firmware quickly and decided to submit them directly, I
was not involved with that at all.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-02-26 13:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 19:53 [PATCH v2 1/5] ath10k: QCA4019 hw1.0: update board-2.bin Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-23 19:53 ` [PATCH v2 2/5] ath10k: QCA9888 hw2.0: " Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-23 19:53 ` [PATCH v2 3/5] ath10k: QCA9984 hw1.0: " Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-23 19:53 ` [PATCH v2 4/5] ath10k: QCA99X0 hw2.0: replace board.bin, add updated board-2.bin Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-23 19:53 ` [PATCH v2 5/5] ath10k: QCA6174 hw3.0: update board-2.bin Christian Lamparter
2022-02-23 19:53 ` Christian Lamparter
2022-02-24 20:24 ` [PATCH v2 1/5] ath10k: QCA4019 hw1.0: " Josh Boyer
2022-02-24 20:24 ` Josh Boyer
2022-02-26 13:24 ` Kalle Valo [this message]
2022-02-26 13:24 ` Kalle Valo
2022-02-26 16:39 ` Christian Lamparter
2022-02-26 16:39 ` Christian Lamparter
2022-02-26 16:59 ` Sven Eckelmann
2022-02-26 16:59 ` Sven Eckelmann
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=87sfs5squm.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@gmail.com \
--cc=jwboyer@kernel.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-firmware@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.