From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: linux-kernel@vger.kernel.org,
"Randy.Dunlap" <rdunlap@xenotime.net>,
Ed Sweetman <safemode@comcast.net>,
akpm@osdl.org
Subject: Re: 2.6.16-rc1-mm2 pata driver confusion
Date: Mon, 06 Feb 2006 19:56:40 +0000 [thread overview]
Message-ID: <1139255800.10437.51.camel@localhost.localdomain> (raw)
In-Reply-To: <43E7A4C0.4020209@t-online.de>
On Llu, 2006-02-06 at 20:34 +0100, Harald Dunkel wrote:
> how it is _supposed_ to work? Is there a conflict between
> ata_piix and piix/mpiix? A short summary could be very helpfull
> to identify problems, and to reduce confusion.
MPIIX is totally different PCI identifiers so a different driver. It is
unrelated to any goings on here.
next prev parent reply other threads:[~2006-02-06 19:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 16:53 2.6.16-rc1-mm2 pata driver confusion Randy.Dunlap
2006-01-26 11:09 ` Ed Sweetman
2006-01-30 11:43 ` Alan Cox
2006-01-30 15:36 ` Randy.Dunlap
2006-02-03 21:54 ` Ed Sweetman
2006-02-06 16:39 ` Randy.Dunlap
2006-02-06 19:34 ` Harald Dunkel
2006-02-06 19:56 ` Alan Cox [this message]
2006-02-07 2:28 ` Ed Sweetman
2006-02-07 1:26 ` 2.6.16-rc1-mm2 pata driver confusion + tsc sync issues Ed Sweetman
2006-02-07 1:35 ` Andrew Morton
2006-02-07 1:53 ` Matthew Garrett
2006-02-07 3:33 ` Ed Sweetman
2006-02-07 11:10 ` Alan Cox
2006-02-07 3:43 ` Ed Sweetman
-- strict thread matches above, loose matches on Subject: below --
2006-01-24 6:43 2.6.16-rc1-mm2 pata driver confusion Ed Sweetman
2006-01-24 14:51 ` Jeff Garzik
2006-01-24 15:29 ` Alan Cox
2006-01-24 17:05 ` Randy.Dunlap
2006-01-24 17:08 ` Randy.Dunlap
2006-01-24 21:13 ` Alan Cox
2006-01-24 17:13 ` Alan Cox
2006-01-24 22:17 ` Ed Sweetman
2006-01-24 22:27 ` Randy.Dunlap
2006-01-24 23:01 ` Ed Sweetman
2006-01-24 23:07 ` Randy.Dunlap
2006-01-25 1:56 ` Ed Sweetman
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=1139255800.10437.51.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=safemode@comcast.net \
/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).