All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Tejun Heo <htejun@gmail.com>,
	Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	james.bottomley@steeleye.com, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Pavel Machek <pavel@ucw.cz>, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [patch 0/3] AHCI Link Power Management
Date: Tue, 12 Jun 2007 00:43:12 -0400	[thread overview]
Message-ID: <466E2460.3050703@garzik.org> (raw)
In-Reply-To: <466E1EC6.90509@linux.intel.com>

We will do AHCI link PM -- presuming that I can be convinced that it 
does not repeatedly park the hard drive heads, or something similarly 
annoying on PATA<->SATA bridges and similar setups.

IF it works as advertised -- a big if considering all the AHCI silicon 
implementations out there -- we definitely want to use it.

	Jeff




  parent reply	other threads:[~2007-06-12  4:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 18:46 [patch 0/3] AHCI Link Power Management Kristen Carlson Accardi
2007-06-12  1:58 ` Tejun Heo
2007-06-12  2:33   ` Jeff Garzik
2007-06-12  2:34   ` Arjan van de Ven
2007-06-12  3:12     ` Jeff Garzik
2007-06-12  3:12       ` Arjan van de Ven
2007-06-12  3:18         ` Jeff Garzik
2007-06-12  4:13     ` Tejun Heo
2007-06-12  4:19       ` Arjan van de Ven
2007-06-12  4:40         ` Tejun Heo
2007-06-12 15:56           ` Kristen Carlson Accardi
2007-06-12  4:43         ` Jeff Garzik [this message]
2007-06-12 15:43           ` Kristen Carlson Accardi
2007-06-13 14:51         ` Pavel Machek
2007-06-13  9:04       ` Pavel Machek
2007-06-13 16:26         ` Kristen Carlson Accardi
2007-06-14  7:56           ` Tejun Heo
2007-06-13 14:56       ` Pavel Machek
2007-06-14 11:56       ` Jens Axboe
2007-06-14 12:30         ` Tejun Heo

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=466E2460.3050703@garzik.org \
    --to=jeff@garzik.org \
    --cc=arjan@linux.intel.com \
    --cc=htejun@gmail.com \
    --cc=james.bottomley@steeleye.com \
    --cc=jens.axboe@oracle.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.