From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jens Axboe <axboe@suse.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Joshua Kwan <joshk@triplehelix.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: SATA suspend-to-ram patch - merge?
Date: Thu, 22 Sep 2005 15:17:59 +0100 [thread overview]
Message-ID: <1127398679.18840.84.camel@localhost.localdomain> (raw)
In-Reply-To: <20050922061849.GJ7929@suse.de>
On Iau, 2005-09-22 at 08:18 +0200, Jens Axboe wrote:
> > So currently we are in limbo...
>
> Which is a shame, since it means that software suspend on sata is
> basically impossible :)
Not really, everyone on the planet who cares is using the existing patch
and that just works. If the SCSI folks can't fix the SCSI layer to do
power management then the scsi drivers just need to not provide pm
methods until they catch up.
Blocking SATA suspend which people need for SCSI suspend which is
utterly obscure and weird is pointless, as pretty much ever vendor
except Red Hat has already decided.
Alan
next prev parent reply other threads:[~2005-09-22 13:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 6:59 SATA suspend-to-ram patch - merge? Joshua Kwan
2005-09-22 3:14 ` Jeff Garzik
2005-09-22 6:18 ` Jens Axboe
2005-09-22 13:04 ` Mark Lord
2005-09-22 13:08 ` Matthew Garrett
2005-09-22 13:24 ` Jens Axboe
2005-09-22 13:24 ` Jens Axboe
2005-09-22 14:28 ` Christoph Hellwig
2005-09-22 14:17 ` Alan Cox [this message]
2005-09-22 13:56 ` Jens Axboe
2005-09-22 14:30 ` Alan Cox
2005-09-22 14:20 ` Luben Tuikov
2005-09-22 17:57 ` Jeff Garzik
2005-09-22 18:04 ` Linus Torvalds
2005-09-22 18:08 ` Christoph Hellwig
2005-09-22 18:11 ` Jens Axboe
2005-09-22 15:01 ` Randy.Dunlap
2005-09-22 10:36 ` Pavel Machek
2005-09-24 10:18 ` Jeff Garzik
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=1127398679.18840.84.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=joshk@triplehelix.org \
--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).