From: Jeff Garzik <jeff@garzik.org>
To: Greg KH <greg@kroah.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org, kay.sievers@suse.de
Subject: Re: [PATCH] remove duplicate ids from ata_piix
Date: Fri, 23 Feb 2007 05:49:41 -0500 [thread overview]
Message-ID: <45DEC6C5.6040901@garzik.org> (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>
manually applied the proper fix, this for spotting this
prev parent reply other threads:[~2007-02-23 10:49 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
2007-02-23 10:49 ` Jeff Garzik [this message]
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=45DEC6C5.6040901@garzik.org \
--to=jeff@garzik.org \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=kay.sievers@suse.de \
--cc=linux-ide@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).