From: Alan Cox <alan@redhat.com>
To: dledford@redhat.com (Doug Ledford)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
Matt_Domsch@dell.com, andmike@us.ibm.com, cliffw@osdl.org,
linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
linux-megaraid-devel@dell.com
Subject: Re: 2.5.44 compile problem: MegaRAID driver
Date: Mon, 21 Oct 2002 18:33:10 -0400 (EDT) [thread overview]
Message-ID: <200210212233.g9LMXAG14311@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021021222500.GK28914@redhat.com> from "Doug Ledford" at Oct 21, 2002 06:25:00 PM
> This is, umm, a non-elegant way of handling things once you switch your
> driver to the new PCI driver probe model :-(
Someone has to fix all the problems with the new probe model first. Like
the fact we don't have any meaningful address space locking or
sane refcounting for the scsi objects. Until that happens its not a relevant
discussion IMHO
When you can answer "what lock prevents my address space being reissued
before all memory/I/O has provably completely" and "at what point can I
free my scsi structures on a hot unplug safely for all situations" then
its worth discussion
next prev parent reply other threads:[~2002-10-21 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 22:10 2.5.44 compile problem: MegaRAID driver Matt_Domsch
2002-10-21 22:31 ` Alan Cox
2002-10-21 22:25 ` Doug Ledford
2002-10-21 22:29 ` Matt Domsch
2002-10-21 22:33 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-21 20:31 Cliff White
2002-10-21 21:28 ` Mike Anderson
2002-10-21 22:32 ` Cliff White
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=200210212233.g9LMXAG14311@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=Matt_Domsch@dell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andmike@us.ibm.com \
--cc=cliffw@osdl.org \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-megaraid-devel@dell.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