mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bastian Germann <bage@debian.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: toke@toke.dk, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] wifi: ath9k: Remove Qwest/Actiontec 802AIN ID
Date: Mon, 6 Mar 2023 14:51:09 +0100	[thread overview]
Message-ID: <0e708039-1a1d-92a8-28c5-ebb69cd1aad0@debian.org> (raw)
In-Reply-To: <87sfeioupw.fsf@kernel.org>

Am 06.03.23 um 14:49 schrieb Kalle Valo:
> 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

The "which" should be removed as well.

>>>> 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.

Please go ahead.

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 21:02 [PATCH 0/1] " Bastian Germann
2023-03-06  6:19 ` Kalle Valo
2023-03-06 12:50 ` [PATCH 1/1] " Bastian Germann
2023-03-06 13:07   ` Kalle Valo
2023-03-06 13:36     ` Bastian Germann
2023-03-06 13:49       ` Kalle Valo
2023-03-06 13:51         ` Bastian Germann [this message]
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=0e708039-1a1d-92a8-28c5-ebb69cd1aad0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®