All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastian Germann <bage@debian.org>
To: toke@toke.dk, Kalle Valo <kvalo@kernel.org>
Cc: Bastian Germann <bage@debian.org>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] wifi: ath9k: Remove Qwest/Actiontec 802AIN ID
Date: Mon,  6 Mar 2023 13:50:40 +0100	[thread overview]
Message-ID: <20230306125041.2221-1-bage@debian.org> (raw)
In-Reply-To: <20230305210245.9831-1-bage@debian.org>

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>
---
 drivers/net/wireless/ath/ath9k/hif_usb.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/net/wireless/ath/ath9k/hif_usb.c b/drivers/net/wireless/ath/ath9k/hif_usb.c
index f521dfa2f194..1395536720b0 100644
--- a/drivers/net/wireless/ath/ath9k/hif_usb.c
+++ b/drivers/net/wireless/ath/ath9k/hif_usb.c
@@ -42,8 +42,6 @@ static const struct usb_device_id ath9k_hif_usb_ids[] = {
 
 	{ USB_DEVICE(0x0cf3, 0x7015),
 	  .driver_info = AR9287_USB },  /* Atheros */
-	{ USB_DEVICE(0x1668, 0x1200),
-	  .driver_info = AR9287_USB },  /* Verizon */
 
 	{ USB_DEVICE(0x0cf3, 0x7010),
 	  .driver_info = AR9280_USB },  /* Atheros */
-- 
2.39.2


  parent reply	other threads:[~2023-03-06 12:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 21:02 [PATCH 0/1] wifi: ath9k: Remove Qwest/Actiontec 802AIN ID Bastian Germann
2023-03-06  6:19 ` Kalle Valo
2023-03-06 12:50 ` Bastian Germann [this message]
2023-03-06 13:07   ` [PATCH 1/1] " Kalle Valo
2023-03-06 13:36     ` Bastian Germann
2023-03-06 13:49       ` Kalle Valo
2023-03-06 13:51         ` Bastian Germann
2023-03-06 13:59   ` Toke Høiland-Jørgensen
2023-03-15 10:14   ` Kalle Valo

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=20230306125041.2221-1-bage@debian.org \
    --to=bage@debian.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=toke@toke.dk \
    /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.