From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Hannes Reinecke <hare@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] Fixup ahci suspend / resume
Date: Tue, 28 Feb 2006 16:28:47 +0100 [thread overview]
Message-ID: <20060228152847.GE24981@suse.de> (raw)
In-Reply-To: <44046AC2.1060002@pobox.com>
On Tue, Feb 28 2006, Jeff Garzik wrote:
> Jens Axboe wrote:
> >Upstream 2.6.x certainly _does_ care about suspend/resume! To me, this
> >patch seems simple enough to be included. It's little more than
> >splitting the register init out form the port_stop/start functions and
> >calling them on resume/suspend appropriately.
>
> Upstream _libata_ doesn't care much about suspend/resume. Officially,
> its a work in progress with major pieces -- your patch and ACPI -- still
> missing.
Eh my patch is not missing, it's been merged since the start of
2.6.16-rc. The acpi patch is still missing, however that's not required
on all machines. So SATA suspend should work now, at least on ata_piix
which is the only driver that currently enables it.
For 2.6.15 I agree, we don't care about suspend since it basically
cannot work. That's not the case for 2.6.16 though.
> Further, good improvements covering some of the changes in Hannes' patch
> are already in #upstream.
>
> Thus, it's more work than its worth to care about the patch as-is. It
> should be redone against #upstream, which is where all suspend/resume
> development is occurring.
I'm sure Hannes will regenerate against upstream as well if necessary,
however that depends on when this should be applied.
--
Jens Axboe
next prev parent reply other threads:[~2006-02-28 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 14:35 [PATCH] Fixup ahci suspend / resume Hannes Reinecke
2006-02-28 14:45 ` Mark Lord
2006-02-28 14:59 ` Hannes Reinecke
2006-02-28 15:14 ` Jeff Garzik
2006-02-28 15:19 ` Jens Axboe
2006-02-28 15:22 ` Jeff Garzik
2006-02-28 15:28 ` Jens Axboe [this message]
2006-02-28 15:35 ` Jeff Garzik
2006-02-28 15:57 ` Hannes Reinecke
2006-02-28 17:25 ` Jens Axboe
2006-03-04 7:37 ` Randy.Dunlap
2006-03-06 8:36 ` Hannes Reinecke
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=20060228152847.GE24981@suse.de \
--to=axboe@suse.de \
--cc=hare@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).