Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: andersen@codepoet.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] prevent module unloading for legacy IDE chipset drivers
Date: Mon, 26 Apr 2004 15:50:58 +0200	[thread overview]
Message-ID: <20040426135058.GC14074@harddisk-recovery.com> (raw)
In-Reply-To: <200404221635.12490.bzolnier@elka.pw.edu.pl>

On Thu, Apr 22, 2004 at 04:35:12PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Thursday 22 of April 2004 12:33, Erik Mouw wrote:
> > What makes IDE sufficiently different from SCSI that we can't unload
> > IDE host drivers?
> 
> - no reference counting
> - lack of release() method
> - insufficient locking

Do you plan to fix the module unloading in the current code, or is it
easier to write a new driver based on libata (assuming it has been
fixed in libata)? If I understood Jeff's latest libata update
correctly, it should be possible Real Soon Now [tm], right?


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2004-04-26 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 20:19 [PATCH] prevent module unloading for legacy IDE chipset drivers Bartlomiej Zolnierkiewicz
2004-04-22  0:41 ` Erik Andersen
2004-04-22  0:50   ` Bartlomiej Zolnierkiewicz
2004-04-22 10:33     ` Erik Mouw
2004-04-22 14:35       ` Bartlomiej Zolnierkiewicz
2004-04-26 13:50         ` Erik Mouw [this message]
2004-04-26 14:50           ` Bartlomiej Zolnierkiewicz
2004-04-26 15:02             ` Bartlomiej Zolnierkiewicz
2004-04-26 15:23             ` Erik Mouw
2004-04-26 15:54               ` Bartlomiej Zolnierkiewicz
2004-04-26  6:31       ` Rogier Wolff

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=20040426135058.GC14074@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=andersen@codepoet.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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