From: Tejun Heo <htejun@gmail.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: jgarzik@pobox.com, forrest.zhao@gmail.com,
kristen.c.accardi@intel.com, linux-ide@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: sata driver fails to work after resume from S3
Date: Tue, 30 Jan 2007 12:09:51 +0900 [thread overview]
Message-ID: <45BEB6FF.7090504@gmail.com> (raw)
In-Reply-To: <1169797602.25758.85.camel@localhost.localdomain>
Zhang Rui wrote:
> But how to make SATA drive S3 work properly in 2.6.16.33?
There is no simple patch which can fix S3 support in 2.6.16. You need
to backport whole libata EH including PM support. If you absolutely
have to keep using 2.6.16.33, consider backporting libata as a whole
from 2.6.19 (it wouldn't be easy unless you're familiar with libata and
SCSI). Otherwise, just use kernel >= 2.6.18.
--
tejun
prev parent reply other threads:[~2007-01-30 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 7:46 sata driver fails to work after resume from S3 Zhang Rui
2007-01-30 3:09 ` Tejun Heo [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=45BEB6FF.7090504@gmail.com \
--to=htejun@gmail.com \
--cc=forrest.zhao@gmail.com \
--cc=jgarzik@pobox.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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).