From: Matthew Garrett <mjg59@srcf.ucam.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/4] scsi: Allow hosts to be flagged as hotpluggable
Date: Thu, 16 Jul 2009 15:45:36 +0100 [thread overview]
Message-ID: <20090716144536.GB14345@srcf.ucam.org> (raw)
In-Reply-To: <1247755399.6606.4.camel@mulgrave.site>
On Thu, Jul 16, 2009 at 02:43:19PM +0000, James Bottomley wrote:
> On Thu, 2009-07-16 at 15:38 +0100, Matthew Garrett wrote:
> > Exactly.
>
> OK, so if this is only in relation to SATA power management, put it in
> libata and call it something like pm_capable. That way we don't have to
> work out what to do with it for the rest of SCSI.
I have vague memories of this coming up before and it being suggested
that it should be done at the SCSI layer instead, but I can't find that
now. Doing it entirely in libata certainly isn't a problem.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-07-16 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 23:43 [PATCH 1/4] scsi: Allow hosts to be flagged as hotpluggable Matthew Garrett
2009-07-15 23:43 ` [PATCH 2/4] libata: Flag most SATA ports " Matthew Garrett
2009-07-15 23:43 ` [PATCH 3/4] libata: Make it possible for host drivers to flag hotplug ports Matthew Garrett
2009-07-15 23:43 ` [PATCH 4/4] libata: Allow AHCI to flag ports as not hotpluggable Matthew Garrett
2009-07-16 1:12 ` [PATCH 1/4] scsi: Allow hosts to be flagged as hotpluggable James Bottomley
2009-07-16 1:26 ` Matthew Garrett
2009-07-16 7:59 ` Alan Cox
2009-07-16 11:59 ` Matthew Wilcox
2009-07-16 14:30 ` Stefan Richter
2009-07-16 14:36 ` Stefan Richter
2009-07-16 14:44 ` Matthew Garrett
2009-07-16 14:38 ` Matthew Garrett
2009-07-16 14:43 ` James Bottomley
2009-07-16 14:45 ` Matthew Garrett [this message]
2009-07-16 14:53 ` James Bottomley
2009-07-16 14:55 ` Matthew Garrett
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=20090716144536.GB14345@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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.