From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: jeff@garzik.org, hare@suse.de, axboe@suse.de, htejun@gmail.com,
lkml@rtr.ca, linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/6] AHCI suspend/resume support
Date: Fri, 02 Jun 2006 11:23:41 -0700 [thread overview]
Message-ID: <4480822D.6050300@goop.org> (raw)
In-Reply-To: <1149233973.13451.51.camel@forrest26.sh.intel.com>
zhao, forrest wrote:
> Your comments and bug report are welcome.
Thanks, these patches work well for me. Certainly I can do at least one
suspend-resume cycle, which is a big improvement. The second suspend
fails, but I think this is a separate issue unrelated to scsi/sata/ahci.
One other problem is a total machine lockup, which so far has only
happened while in X, so I couldn't see any console messages. Again,
this might have nothing to do with storage; I'll let you know if
anything relevant turns up.
In short: good work!
Thanks,
J
prev parent reply other threads:[~2006-06-02 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 7:39 [PATCH 0/6] AHCI suspend/resume support zhao, forrest
2006-06-02 18:23 ` Jeremy Fitzhardinge [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=4480822D.6050300@goop.org \
--to=jeremy@goop.org \
--cc=axboe@suse.de \
--cc=forrest.zhao@intel.com \
--cc=hare@suse.de \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=lkml@rtr.ca \
/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).