From: Andrew Morton <akpm@osdl.org>
To: Ed Sweetman <safemode@comcast.net>
Cc: safemode@comcast.net, alan@lxorguk.ukuu.org.uk,
harald.dunkel@t-online.de, linux-kernel@vger.kernel.org,
rdunlap@xenotime.net
Subject: Re: 2.6.16-rc1-mm2 pata driver confusion + tsc sync issues
Date: Mon, 6 Feb 2006 17:35:20 -0800 [thread overview]
Message-ID: <20060206173520.43412664.akpm@osdl.org> (raw)
In-Reply-To: <43E7F73E.2070004@comcast.net>
Ed Sweetman <safemode@comcast.net> wrote:
>
(eek, top-posting!)
> 2.6.16-rc2 with the libata patch alan cox provided resulted in a system
> which correctly found my atapi drive on the pata bus.
>
> Also, moving from the mm kernels to 2.6.16-rc2 resulted in my pm timer
> working again.
I don't recall that. Even 2.6.16-rc1-mm5? What about rc1-mm4?
> So, it may have been all along that libata had supported my atapi
> device, but either the patch when it got merged with mm became broken or
> something else in mm broke it, and something else in mm caused my pm
> timer to stop being used.
>
> Hopefully more people chime in with issues like this so the bug can be
> tracked down in mm before the offending code makes it's way to a regular
> release.
>
>
> Also just to note, the patch to 2.6.16-rc2 alan cox made switches the
> load order of pata and sata from mm, resulting in device name changes.
That's bad.
next prev parent reply other threads:[~2006-02-07 1:35 UTC|newest]
Thread overview: 15+ 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
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 [this message]
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
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=20060206173520.43412664.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®