| Message ID | 20230305210245.9831-1-bage@debian.org |
|---|---|
| Headers | show |
| Series | wifi: ath9k: Remove Qwest/Actiontec 802AIN ID | expand |
Bastian Germann <bage@debian.org> writes: > Drop a wrongly claimed USB ID. > > Bastian Germann (1): > wifi: ath9k: Remove Qwest/Actiontec 802AIN ID > > drivers/net/wireless/ath/ath9k/hif_usb.c | 2 -- > 1 file changed, 2 deletions(-) I can't find the actual patch anywhere, I only see the cover letter: https://lore.kernel.org/all/20230305210245.9831-1-bage@debian.org/
Bastian Germann <bage@debian.org> writes: > The USB device 1668:1200 is Qwest/Actiontec 802AIN which is also > correctly claimed to be supported by carl9170. > > Supposedly, the successor 802AIN2 which has an ath9k compatible chip > whose USB ID (unknown) could be inserted instead. > > Drop the ID from the wrong driver. > > Signed-off-by: Bastian Germann <bage@debian.org> Thanks, I see this patch now. I guess there's a bug report somewhere, do you have a link?
Bastian Germann <bage@debian.org> writes: > Am 06.03.23 um 14:07 schrieb Kalle Valo: >> Bastian Germann <bage@debian.org> writes: >> >>> The USB device 1668:1200 is Qwest/Actiontec 802AIN which is also >>> correctly claimed to be supported by carl9170. >>> >>> Supposedly, the successor 802AIN2 which has an ath9k compatible chip >>> whose USB ID (unknown) could be inserted instead. >>> >>> Drop the ID from the wrong driver. >>> >>> Signed-off-by: Bastian Germann <bage@debian.org> >> >> Thanks, I see this patch now. >> >> I guess there's a bug report somewhere, do you have a link? > > No, I happened to find this by chance while packaging the ath9k and > carl9170 firmware for Debian, > which have the ID represented in an XML format: > https://salsa.debian.org/debian/open-ath9k-htc-firmware/-/blob/master/debian/firmware-ath9k-htc.metainfo.xml Do you mind if we add this (without the link) to the commit log? It's good to always document the background of the patch.
Bastian Germann <bage@debian.org> writes: > The USB device 1668:1200 is Qwest/Actiontec 802AIN which is also > correctly claimed to be supported by carl9170. > > Supposedly, the successor 802AIN2 which has an ath9k compatible chip > whose USB ID (unknown) could be inserted instead. > > Drop the ID from the wrong driver. > > Signed-off-by: Bastian Germann <bage@debian.org> Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>