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 -- take 2
Date: Wed, 21 Jun 2006 08:32:18 -0700 [thread overview]
Message-ID: <44996682.7060003@goop.org> (raw)
In-Reply-To: <1149588926.29552.53.camel@forrest26.sh.intel.com>
zhao, forrest wrote:
> This is the take 2 of AHCI suspend/resume patches.
>
This no longer applies against 2.6.17-mm1. Do you have an updated
version, or has the equivalent behaviour been merged into libata -> -mm
now? Or should I just try and merge it?
Thanks,
J
next prev parent reply other threads:[~2006-06-21 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 10:15 [PATCH 0/6] AHCI suspend/resume support -- take 2 zhao, forrest
2006-06-21 15:32 ` Jeremy Fitzhardinge [this message]
2006-06-22 1:10 ` zhao, forrest
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=44996682.7060003@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).