From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, Tejun Heo <htejun@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Deepak Saxena <dsaxena@plexity.net>, Dan Faerch <dan@hacker.dk>,
Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: ata and netdev (was Re: -mm merge plans for 2.6.23)
Date: Tue, 10 Jul 2007 14:55:02 -0400 [thread overview]
Message-ID: <1184093702.3401.83.camel@localhost.localdomain> (raw)
In-Reply-To: <20070710112458.e9dbb55e.akpm@linux-foundation.org>
On Tue, 2007-07-10 at 11:24 -0700, Andrew Morton wrote:
> > > ata-ahci-alpm-store-interrupt-value.patch
> > > ata-ahci-alpm-expose-power-management-policy-option-to-users.patch
> > > ata-ahci-alpm-enable-link-power-management-for-ata-drivers.patch
> > > ata-ahci-alpm-enable-aggressive-link-power-management-for-ahci-controllers.patch
> > >
> > > These appear to need some work.
> >
> > seemed mostly OK to me. what comments did I miss?
>
> Oh, I thought these were the patches which affected scsi and which James
> had issues with. I guess I got confused.
Well ... my concern was really how to make them more generic ... ahci
isn't the only controller that can do phy power management, and it also
seemed to me that the most generic entity for power management was the
transport rather than the SCSI mid-layer, but that debate is still
ongoing.
James
next prev parent reply other threads:[~2007-07-10 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070710013152.ef2cd200.akpm@linux-foundation.org>
2007-07-10 17:42 ` ata and netdev (was Re: -mm merge plans for 2.6.23) Jeff Garzik
2007-07-10 18:24 ` Andrew Morton
2007-07-10 18:55 ` James Bottomley [this message]
2007-07-10 18:57 ` Jeff Garzik
2007-07-10 20:31 ` Sergei Shtylyov
2007-07-10 20:35 ` Andrew Morton
2007-07-11 16:47 ` Dan Faerch
2007-07-10 19:56 ` Sergei Shtylyov
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=1184093702.3401.83.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@kvack.org \
--cc=dan@hacker.dk \
--cc=dsaxena@plexity.net \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).