From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: cached PCS
Date: Wed, 09 Aug 2006 18:48:51 +0900 [thread overview]
Message-ID: <44D9AF83.80507@gmail.com> (raw)
In-Reply-To: <44D97F07.9000301@garzik.org>
Jeff Garzik wrote:
> can you resurrect your cached PCS patch?
>
> 2.6.18-rc didn't fix the ghost device and long boot delay problems for
> everybody.
The cached PCS patch was to fix device detection failure on some ICH5s
where PCS is cleared while probing the first port. Remaining ghost
device and long boot delay are fixed by honor-PCS patch. Do you want me
to resurrect both?
--
tejun
next prev parent reply other threads:[~2006-08-09 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 6:21 cached PCS Jeff Garzik
2006-08-09 9:48 ` Tejun Heo [this message]
2006-08-09 10:08 ` Jeff Garzik
2006-08-09 10:11 ` Tejun Heo
2006-08-09 10:27 ` Jeff Garzik
2006-08-09 10:39 ` Tejun Heo
2006-08-09 10:46 ` Jeff Garzik
2006-08-09 11:12 ` Tejun Heo
2006-08-10 4:50 ` Tejun Heo
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=44D9AF83.80507@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).