From: Jeff Garzik <jgarzik@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: linux-ide@vger.kernel.org, kay.sievers@suse.de,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] remove duplicate ids from ata_piix
Date: Thu, 25 Jan 2007 21:21:58 -0500 [thread overview]
Message-ID: <45B965C6.5090604@pobox.com> (raw)
In-Reply-To: <20070126021228.GA3444@kroah.com>
Greg KH wrote:
> From: Greg Kroah-Hartman <gregkh@suse.de>
>
> It seems that the ata_piix driver has two duplicate ids, one of them
> with a different 'private' field in it, which was never being used due
> to the match for the device happening on an earlier entry.
>
> This patch removes the duplicates, if this is the correct thing to do in
> this case for the ICH5 device or not, I'll leave to you :)
>
> This duplication was pointed out to me by Kay Sievers <kay.sievers@suse.de>
>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> ---
> drivers/ata/ata_piix.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> --- gregkh-2.6.orig/drivers/ata/ata_piix.c
> +++ gregkh-2.6/drivers/ata/ata_piix.c
> @@ -191,12 +191,8 @@ static const struct pci_device_id piix_p
> /* Intel ICH4 (i845GV, i845E, i852, i855) UDMA 100 */
> { 0x8086, 0x24CA, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
> { 0x8086, 0x24CB, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
> - /* Intel ICH5 */
> - { 0x8086, 0x24DB, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_133 },
> /* C-ICH (i810E2) */
> { 0x8086, 0x245B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
> - /* ESB (855GME/875P + 6300ESB) UDMA 100 */
> - { 0x8086, 0x25A2, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
> /* ICH6 (and 6) (i915) UDMA 100 */
> { 0x8086, 0x266F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
> /* ICH7/7-R (i945, i975) UDMA 100*/
Both IDs are clearly dups, but ICH5 should support ich_pata_133, so
you're removing the wrong entry there.
I think the right thing to do is remove the entries that appear near the
top of the list, but I would like Alan (Mr. PATA) to confirm...
/* Also PIIX4E (fn3 rev 2) and PIIX4M (fn3 rev 3) */
{ 0x8086, 0x7111, PCI_ANY_ID, PCI_ANY_ID, 0, 0, piix_pata_33 },
- { 0x8086, 0x24db, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
- { 0x8086, 0x25a2, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
Regards,
Jeff
next prev parent reply other threads:[~2007-01-26 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 2:12 [PATCH] remove duplicate ids from ata_piix Greg KH
2007-01-26 2:21 ` Jeff Garzik [this message]
2007-02-23 10:49 ` Jeff Garzik
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=45B965C6.5090604@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=kay.sievers@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).