From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Andrew Chew <achew@nvidia.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.7] new NVIDIA libata SATA driver
Date: Wed, 16 Jun 2004 21:20:10 -0400 [thread overview]
Message-ID: <20040617012009.GA10879@havoc.gtf.org> (raw)
In-Reply-To: <200406170312.42324.bzolnier@elka.pw.edu.pl>
On Thu, Jun 17, 2004 at 03:12:42AM +0200, Bartlomiej Zolnierkiewicz wrote:
> Removing IDs from amd74xx.c is a bad idea,
> it breaks boot on systems already using these IDs.
(FWIW for Andrew)
I'm going to apply Andrew's patch, but without the PCI id removals.
Then, I'll apply a patch that adds Kconfig questions
Include hardware that conflicts with libata SATA driver?
(in drivers/ide)
and
Include hardware that conflicts with IDE driver?
(in libata, drivers/scsi)
and apply the associated ifdefs to the low-level drivers.
This is necessary to both enable conflict prevention, and also make sure
we don't break existing setups in the move to libata for SATA stuff.
Jeff
next prev parent reply other threads:[~2004-06-17 1:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 0:17 [PATCH 2.6.7] new NVIDIA libata SATA driver Andrew Chew
2004-06-17 1:12 ` Bartlomiej Zolnierkiewicz
2004-06-17 1:20 ` Jeff Garzik [this message]
2004-06-17 2:49 ` Markus Kossmann
2004-06-17 3:13 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-06-17 1:19 Andrew Chew
2004-06-17 1:22 ` Jeff Garzik
2004-06-17 1:28 Andrew Chew
2004-06-17 1:35 Andrew Chew
2004-06-17 1:47 ` 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=20040617012009.GA10879@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=achew@nvidia.com \
--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