archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <>
To: Richard Purdie <>
Cc: Linux Kernel Mailing List <>
Subject: Re: Flaw in ide_unregister()
Date: Mon, 10 Jan 2005 19:23:53 +0000	[thread overview]
Message-ID: <1105382277.12054.94.camel@localhost.localdomain> (raw)
In-Reply-To: <019201c4f711$67237c20$0f01a8c0@max>

On Llu, 2005-01-10 at 12:39, Richard Purdie wrote:
> Offloading this responsibility onto each and every driver seems rather 
> rather unwise and will result in a lot of code duplication. Are there any 
> circumstances where we need ide_unregister to abort on busy? Even if there 
> are would a flag to indicate what it should do with a busy drive be better?

Currently there are four things in the -ac tree that use this feature

1.	ISA PnP, where we don't support hotplug (and anyway the only maker of
consumer hotpluggable ISA docking stations I know of - IBM - wont
provide docs on them)
2.	ide-cs
3.	delkin (cardbus IDE)
4.	PCI layer

Of those the PCI one is a common shared function so I put the supporting
logic in the IDE PCI helper function, The others need different handling
at the PCMCIA or Cardbus level in order to free up resources and clean

  reply	other threads:[~2005-01-10 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-31 12:04 Flaw in ide_unregister() Richard Purdie
2005-01-02 14:36 ` Alan Cox
2005-01-09 22:37   ` Richard Purdie
2005-01-10 11:09     ` Alan Cox
2005-01-10 12:39       ` Richard Purdie
2005-01-10 19:23         ` Alan Cox [this message]
2005-01-10 21:17           ` Richard Purdie

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1105382277.12054.94.camel@localhost.localdomain \ \ \ \

* 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).