From: "Bryan O'Sullivan" <bos@pathscale.com>
To: Greg KH <gregkh@suse.de>
Cc: Roland Dreier <rdreier@cisco.com>,
rolandd@cisco.com, akpm@osdl.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH 9 of 20] ipath - char devices for diagnostics and lightweight subnet management
Date: Thu, 09 Mar 2006 20:41:36 -0800 [thread overview]
Message-ID: <1141965696.14517.4.camel@camp4.serpentine.com> (raw)
In-Reply-To: <20060310010403.GC9945@suse.de>
On Thu, 2006-03-09 at 17:04 -0800, Greg KH wrote:
> > I don't expect this to be a practical problem. We're planning to add
> > hotplug support to the driver once we have some cycles free.
>
> Ugh, that means it's never going to be there.
>
> All new PCI drivers have the requirement that they work properly in
> hotplug systems, as they should follow the PCI core api. If not, odds
> are they will not be accepted into the tree :(
Okay, maybe we're talking at cross purposes here. We do follow the PCI
core API. We have a __devinit probe and __devexit remove routine, a
MODULE_DEVICE_TABLE, the kernel generates hotplug events when a device
is detected or the driver is unloaded, and so on.
I *assumed* that there was something more that we would need to do in
order to support real hotplug of actual physical cards, but now that I
look more closely, it doesn't appear that there is. At least, there's
nothing in Documentation/pci.txt or LDD3 that indicates to me that we
ought to be doing more.
Am I missing something?
<b
next prev parent reply other threads:[~2006-03-10 4:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eac2ad3017b5f160d24c.1141922822@localhost.localdomain>
2006-03-09 23:20 ` Roland Dreier
2006-03-09 23:39 ` Bryan O'Sullivan
2006-03-09 23:47 ` Roland Dreier
2006-03-09 23:50 ` Bryan O'Sullivan
2006-03-09 23:52 ` Roland Dreier
2006-03-10 15:54 ` Michael S. Tsirkin
2006-03-10 16:05 ` Bryan O'Sullivan
2006-03-09 23:24 ` Roland Dreier
2006-03-09 23:49 ` Bryan O'Sullivan
2006-03-09 23:51 ` Roland Dreier
2006-03-09 23:26 ` Roland Dreier
2006-03-09 23:52 ` Bryan O'Sullivan
2006-03-10 0:00 ` Roland Dreier
2006-03-10 0:04 ` Bryan O'Sullivan
2006-03-10 0:45 ` Greg KH
2006-03-10 0:48 ` Bryan O'Sullivan
2006-03-10 1:04 ` Greg KH
2006-03-10 4:41 ` Bryan O'Sullivan [this message]
2006-03-10 5:48 ` Greg KH
2006-03-10 13:40 ` Bryan O'Sullivan
2006-03-10 5:55 ` Roland Dreier
2006-03-10 13:43 ` Bryan O'Sullivan
2006-03-10 16:58 ` Greg KH
2006-03-10 17:05 ` Bryan O'Sullivan
2006-03-10 17:08 ` Roland Dreier
2006-03-10 17:32 ` Bryan O'Sullivan
2006-03-10 22:20 ` Roland Dreier
2006-03-10 0:35 [PATCH 0 of 20] [RFC] ipath driver - another round for review Bryan O'Sullivan
2006-03-10 0:35 ` [PATCH 9 of 20] ipath - char devices for diagnostics and lightweight subnet management Bryan O'Sullivan
2006-03-10 0:45 ` Roland Dreier
2006-03-10 0:47 ` Bryan O'Sullivan
2006-03-10 0:52 ` Roland Dreier
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=1141965696.14517.4.camel@camp4.serpentine.com \
--to=bos@pathscale.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
--cc=rolandd@cisco.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
Powered by JetHome