mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Steven Dake <sdake@mvista.com>
Cc: Greg KH <greg@kroah.com>, Scott Murray <scottm@somanetworks.com>,
	"Randy.Dunlap" <rddunlap@osdl.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RFC] Advanced TCA SCSI Disk Hotswap
Date: 25 Oct 2002 11:04:29 +0100	[thread overview]
Message-ID: <1035540269.13032.7.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3DB886B9.3060304@mvista.com>

On Fri, 2002-10-25 at 00:48, Steven Dake wrote:
> Surprise extraction is not a simple problem especially to ensure the 
> device drivers exit
> cleanly without dumping more data on the PCI bus to a PCI device that 
> may not
> exist.

Thats primarily about resource handling orders. Making sure we don't
release the claimed pci resources in the driver until the driver itself
is sure it has shut up.

I'm doing suprise removal ok with the thinkpad 600 (in 2.4 with some
limits due to the 2.4 pci layer). Network stuff seems to be fine. The
block layer has major issues.


  parent reply	other threads:[~2002-10-25  9:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200210242002.g9OK27W03864@localhost.localdomain>
2002-10-24 20:45 ` Steven Dake
2002-10-24 21:05   ` Randy.Dunlap
2002-10-24 21:48     ` Steven Dake
2002-10-24 23:00     ` Scott Murray
2002-10-24 23:22       ` Greg KH
2002-10-24 23:48         ` Steven Dake
2002-10-25  0:20           ` Jeff Garzik
2002-10-25 10:04           ` Alan Cox [this message]
2002-10-25  0:18         ` Scott Murray
2002-10-24 23:42   ` James Bottomley
2002-10-24 23:52     ` Jeff Garzik
2002-10-27 15:08       ` Rob Landley
2002-10-27 20:25         ` Randy.Dunlap

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=1035540269.13032.7.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=James.Bottomley@steeleye.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=scottm@somanetworks.com \
    --cc=sdake@mvista.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

all inboxes | Powered by JetHome®