From: Valo, Kalle <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Move generic entries below specific ones in ath_pci_id_table.
Date: Tue, 15 Nov 2016 14:49:16 +0000 [thread overview]
Message-ID: <87bmxgpzmc.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8d77a285e16cdd9f3b79c9e8d8800d72@vittgam.net> (Vittorio Gambaletta's message of "Fri, 14 Oct 2016 11:49:40 +0200")
"Vittorio Gambaletta (VittGam)" <linux-wireless@vittgam.net> writes:
> Hello,
>
> On 12/10/2016 17:01:08 CEST, Valo, Kalle wrote:
>
>> So to tell the full story I'll change the commit log to something like
>> below. Does it look ok to you?
>
> Yes; but I'd change "So" to "This turned out to be wrong", and add a note
> about changing the order for 0x002A too:
>
> ----------------------------------------------------------------------
> ath9k: Really fix LED polarity for some Mini PCI AR9220 MB92 cards.
>
> The active_high LED of my Wistron DNMA-92 is still being recognized as
> active_low on 4.7.6 mainline. When I was preparing my former commit
> 0f9edcdd88a9 ("ath9k: Fix LED polarity for some Mini PCI AR9220 MB92
> cards.") to fix that I must have somehow messed up with testing, because
> I tested the final version of that patch before sending it, and it was
> apparently working; but now it is not working on 4.7.6 mainline.
>
> I initially added the PCI_DEVICE_SUB section for 0x0029/0x2096 above the
> PCI_VDEVICE section for 0x0029; but then I moved the former below the
> latter after seeing how 0x002A sections were sorted in the file.
>
> This turned out to be wrong: if a generic PCI_VDEVICE entry (that has
> both subvendor and subdevice IDs set to PCI_ANY_ID) is put before a more
> specific one (PCI_DEVICE_SUB), then the generic PCI_VDEVICE entry will
> match first and will be used.
>
> With this patch, 0x0029/0x2096 has finally got active_high LED on 4.7.6.
>
> While I'm at it, let's fix 0x002A too by also moving its generic definition
> below its specific ones.
>
> Fixes: 0f9edcdd88a9 ("ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.")
> Cc: <stable@vger.kernel.org> #4.7+
> Signed-off-by: Vittorio Gambaletta <linuxbugs@vittgam.net>
> [kvalo at qca.qualcomm.com: improve the commit log based on email discussions]
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
> ----------------------------------------------------------------------
Thanks, I updated the commit with your changes.
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Vittorio Gambaletta (VittGam)" <linux-wireless@vittgam.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath9k-devel <ath9k-devel@qca.qualcomm.com>,
"ath9k-devel@venema.h4ckr.net" <ath9k-devel@venema.h4ckr.net>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] ath9k: Move generic entries below specific ones in ath_pci_id_table.
Date: Tue, 15 Nov 2016 14:49:16 +0000 [thread overview]
Message-ID: <87bmxgpzmc.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8d77a285e16cdd9f3b79c9e8d8800d72@vittgam.net> (Vittorio Gambaletta's message of "Fri, 14 Oct 2016 11:49:40 +0200")
"Vittorio Gambaletta (VittGam)" <linux-wireless@vittgam.net> writes:
> Hello,
>
> On 12/10/2016 17:01:08 CEST, Valo, Kalle wrote:
>
>> So to tell the full story I'll change the commit log to something like
>> below. Does it look ok to you?
>
> Yes; but I'd change "So" to "This turned out to be wrong", and add a note
> about changing the order for 0x002A too:
>
> ----------------------------------------------------------------------
> ath9k: Really fix LED polarity for some Mini PCI AR9220 MB92 cards.
>
> The active_high LED of my Wistron DNMA-92 is still being recognized as
> active_low on 4.7.6 mainline. When I was preparing my former commit
> 0f9edcdd88a9 ("ath9k: Fix LED polarity for some Mini PCI AR9220 MB92
> cards.") to fix that I must have somehow messed up with testing, because
> I tested the final version of that patch before sending it, and it was
> apparently working; but now it is not working on 4.7.6 mainline.
>
> I initially added the PCI_DEVICE_SUB section for 0x0029/0x2096 above the
> PCI_VDEVICE section for 0x0029; but then I moved the former below the
> latter after seeing how 0x002A sections were sorted in the file.
>
> This turned out to be wrong: if a generic PCI_VDEVICE entry (that has
> both subvendor and subdevice IDs set to PCI_ANY_ID) is put before a more
> specific one (PCI_DEVICE_SUB), then the generic PCI_VDEVICE entry will
> match first and will be used.
>
> With this patch, 0x0029/0x2096 has finally got active_high LED on 4.7.6.
>
> While I'm at it, let's fix 0x002A too by also moving its generic definiti=
on
> below its specific ones.
>
> Fixes: 0f9edcdd88a9 ("ath9k: Fix LED polarity for some Mini PCI AR9220 MB=
92 cards.")
> Cc: <stable@vger.kernel.org> #4.7+
> Signed-off-by: Vittorio Gambaletta <linuxbugs@vittgam.net>
> [kvalo@qca.qualcomm.com: improve the commit log based on email discussion=
s]
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
> ----------------------------------------------------------------------
Thanks, I updated the commit with your changes.
--=20
Kalle Valo=
WARNING: multiple messages have this Message-ID (diff)
From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Vittorio Gambaletta (VittGam)" <linux-wireless@vittgam.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath9k-devel <ath9k-devel@qca.qualcomm.com>,
"ath9k-devel@venema.h4ckr.net" <ath9k-devel@venema.h4ckr.net>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] ath9k: Move generic entries below specific ones in ath_pci_id_table.
Date: Tue, 15 Nov 2016 14:49:16 +0000 [thread overview]
Message-ID: <87bmxgpzmc.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8d77a285e16cdd9f3b79c9e8d8800d72@vittgam.net> (Vittorio Gambaletta's message of "Fri, 14 Oct 2016 11:49:40 +0200")
"Vittorio Gambaletta (VittGam)" <linux-wireless@vittgam.net> writes:
> Hello,
>
> On 12/10/2016 17:01:08 CEST, Valo, Kalle wrote:
>
>> So to tell the full story I'll change the commit log to something like
>> below. Does it look ok to you?
>
> Yes; but I'd change "So" to "This turned out to be wrong", and add a note
> about changing the order for 0x002A too:
>
> ----------------------------------------------------------------------
> ath9k: Really fix LED polarity for some Mini PCI AR9220 MB92 cards.
>
> The active_high LED of my Wistron DNMA-92 is still being recognized as
> active_low on 4.7.6 mainline. When I was preparing my former commit
> 0f9edcdd88a9 ("ath9k: Fix LED polarity for some Mini PCI AR9220 MB92
> cards.") to fix that I must have somehow messed up with testing, because
> I tested the final version of that patch before sending it, and it was
> apparently working; but now it is not working on 4.7.6 mainline.
>
> I initially added the PCI_DEVICE_SUB section for 0x0029/0x2096 above the
> PCI_VDEVICE section for 0x0029; but then I moved the former below the
> latter after seeing how 0x002A sections were sorted in the file.
>
> This turned out to be wrong: if a generic PCI_VDEVICE entry (that has
> both subvendor and subdevice IDs set to PCI_ANY_ID) is put before a more
> specific one (PCI_DEVICE_SUB), then the generic PCI_VDEVICE entry will
> match first and will be used.
>
> With this patch, 0x0029/0x2096 has finally got active_high LED on 4.7.6.
>
> While I'm at it, let's fix 0x002A too by also moving its generic definition
> below its specific ones.
>
> Fixes: 0f9edcdd88a9 ("ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.")
> Cc: <stable@vger.kernel.org> #4.7+
> Signed-off-by: Vittorio Gambaletta <linuxbugs@vittgam.net>
> [kvalo@qca.qualcomm.com: improve the commit log based on email discussions]
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
> ----------------------------------------------------------------------
Thanks, I updated the commit with your changes.
--
Kalle Valo
next prev parent reply other threads:[~2016-11-15 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 10:00 [ath9k-devel] [PATCH] ath9k: Move generic entries below specific ones in ath_pci_id_table Vittorio Gambaletta
2016-10-03 10:00 ` Vittorio Gambaletta (VittGam)
2016-10-04 15:46 ` [ath9k-devel] " Kalle Valo
2016-10-04 15:46 ` Kalle Valo
2016-10-04 18:14 ` [ath9k-devel] " Vittorio Gambaletta
2016-10-04 18:14 ` Vittorio Gambaletta (VittGam)
2016-10-12 13:34 ` [ath9k-devel] " Kalle Valo
2016-10-12 13:34 ` Kalle Valo
2016-10-12 14:13 ` [ath9k-devel] " Vittorio Gambaletta
2016-10-12 14:13 ` Vittorio Gambaletta (VittGam)
2016-10-12 15:01 ` [ath9k-devel] " Valo, Kalle
2016-10-12 15:01 ` Valo, Kalle
2016-10-12 15:01 ` Valo, Kalle
2016-10-14 9:49 ` [ath9k-devel] " Vittorio Gambaletta
2016-10-14 9:49 ` Vittorio Gambaletta (VittGam)
2016-11-15 14:49 ` Valo, Kalle [this message]
2016-11-15 14:49 ` Valo, Kalle
2016-11-15 14:49 ` Valo, Kalle
2016-11-15 14:53 ` 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=87bmxgpzmc.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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.