From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jens Axboe <axboe@suse.de>
Cc: Erik Slagter <erik@slagter.name>, Jeff Garzik <jgarzik@pobox.com>,
Randy Dunlap <randy_d_dunlap@linux.intel.com>,
hch@infradead.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
acpi-devel@lists.sourceforge.net
Subject: Re: RFC: ACPI/scsi/libata integration and hotswap
Date: Fri, 9 Dec 2005 11:55:11 +0000 [thread overview]
Message-ID: <20051209115511.GA25842@srcf.ucam.org> (raw)
In-Reply-To: <20051209114641.GH26185@suse.de>
On Fri, Dec 09, 2005 at 12:46:42PM +0100, Jens Axboe wrote:
> On Fri, Dec 09 2005, Erik Slagter wrote:
> > I case this (still) isn't clear, I am addressing the attitude of "It's
> > ACPI so it's not going to be used, period".
>
> The problem seems to be that you are misunderstanding the 'attitude',
> which was mainly based on the initial patch sent out which stuffs acpi
> directly in everywhere. That seems to be a good trigger for curt/direct
> replies.
I was just following the example set by the ide acpi suspend/resume
patch, which people didn't seem to object to nearly as much. I guess
IDE's such a hack anyway that people aren't as worried :) I'll try
produce a patch that just inserts platform-independent code into scsi
around the start of next week.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2005-12-09 11:55 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 3:02 RFC: ACPI/scsi/libata integration and hotswap Matthew Garrett
2005-12-08 9:15 ` Christoph Hellwig
2005-12-08 13:26 ` Matthew Garrett
2005-12-08 13:33 ` Christoph Hellwig
2005-12-08 13:39 ` Matthew Garrett
2005-12-08 13:44 ` Christoph Hellwig
2005-12-08 17:18 ` Erik Slagter
2005-12-08 20:43 ` Jeff Garzik
2005-12-08 21:03 ` Dominic Ijichi
2005-12-08 21:09 ` Jeff Garzik
2005-12-08 21:34 ` Dominic Ijichi
2005-12-08 21:31 ` Randy Dunlap
2005-12-09 9:45 ` Erik Slagter
2005-12-09 10:39 ` Jens Axboe
2005-12-09 10:45 ` Erik Slagter
2005-12-09 11:27 ` Jeff Garzik
2005-12-09 11:35 ` Erik Slagter
2005-12-09 11:40 ` Christoph Hellwig
2005-12-09 11:46 ` Jens Axboe
2005-12-09 11:55 ` Matthew Garrett [this message]
2005-12-09 13:22 ` Bartlomiej Zolnierkiewicz
2005-12-09 12:01 ` Erik Slagter
2005-12-09 12:07 ` Jens Axboe
2005-12-10 2:19 ` Douglas Gilbert
2005-12-14 20:52 ` [ACPI] " Matthew Wilcox
2005-12-09 11:30 ` Jens Axboe
2005-12-09 3:28 ` Mark Lord
2005-12-09 11:29 ` Jeff Garzik
2005-12-10 4:01 ` Mark Lord
2005-12-08 13:52 ` Jeff Garzik
2005-12-08 14:07 ` [ACPI] " Alan Cox
2005-12-08 14:14 ` Jeff Garzik
2005-12-08 14:30 ` Alan Cox
2005-12-08 14:43 ` Matthew Garrett
2005-12-08 14:53 ` Alan Cox
2005-12-09 11:42 ` Jeff Garzik
2005-12-08 14:12 ` Matthew Garrett
2005-12-08 14:01 ` Alan Cox
2005-12-08 14:18 ` Matthew Garrett
2005-12-08 14:33 ` Alan Cox
2005-12-08 14:52 ` Matthew Garrett
2005-12-08 14:55 ` Alan Cox
2005-12-08 17:19 ` Matthew Garrett
2005-12-09 11:42 ` Christoph Hellwig
2005-12-09 11:49 ` Jeff Garzik
2005-12-09 11:52 ` Matthew Garrett
2005-12-09 11:58 ` Jeff Garzik
2005-12-09 12:11 ` Matthew Garrett
2005-12-09 12:16 ` Jeff Garzik
2005-12-09 12:24 ` Matthew Garrett
2005-12-10 0:40 ` Jeff Garzik
2005-12-10 2:34 ` Matthew Garrett
2005-12-10 2:39 ` Jeff Garzik
2005-12-10 2:47 ` Matthew Garrett
2005-12-10 2:41 ` Jeff Garzik
2005-12-10 2:50 ` Matthew Garrett
2005-12-10 2:57 ` Jeff Garzik
2005-12-10 3:47 ` [ACPI] " Andrew Grover
2005-12-12 0:38 ` Alan Cox
2005-12-09 11:50 ` Matthew Garrett
2005-12-09 11:55 ` Christoph Hellwig
2005-12-13 18:14 ` Randy Dunlap
2005-12-13 18:26 ` Matthew Garrett
2005-12-13 19:07 ` Randy Dunlap
2005-12-08 13:57 Salyzyn, Mark
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=20051209115511.GA25842@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=axboe@suse.de \
--cc=erik@slagter.name \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy_d_dunlap@linux.intel.com \
/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).