From: Paul Fulghum <paulkf@microgate.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Laurent Riffard <laurent.riffard@free.fr>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Kernel development list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.9-rc4-mm1 : oops when rmmod uhci_hcd [was: 2.6.9-rc3-mm2 : oops...]
Date: Fri, 15 Oct 2004 12:36:02 -0500 [thread overview]
Message-ID: <1097861761.2820.18.camel@deimos.microgate.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0410151318580.1052-100000@ida.rowland.org>
On Fri, 2004-10-15 at 12:21, Alan Stern wrote:
> As I understand it, the description field is just a human-readable string
> that indicates what sort of device the hcd is. It doesn't need to be
> unique. In fact, the kerneldoc for request_irq() (without the updates)
> says that the dev_id value must be unique but says nothing about the
> devname.
In the SyncLink drivers I've always passed a devname
that is unique to each device instance, using the
form printf(devname, "%s%d", basename, instance_num).
Ethernet device instances also seem to do this.
I see that the generic serial 8250 driver uses
a constant name, as does aic7xxx.
Unique device names are useful for identifying
which device instance is on a particular interrupt
(/proc/interrupts), but other drivers beside uhci_hcd
use a constant name so I guess that is legal :-)
Either way, the generic IRQ code should deal with
duplicates without generating an oops.
--
Paul Fulghum
paulkf@microgate.com
next prev parent reply other threads:[~2004-10-15 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 19:40 2.6.9-rc4-mm1 : oops when rmmod uhci_hcd [was: 2.6.9-rc3-mm2 : oops...] Laurent Riffard
2004-10-13 15:41 ` Alan Stern
2004-10-14 20:23 ` Laurent Riffard
2004-10-14 21:03 ` Alan Stern
2004-10-14 23:21 ` Laurent Riffard
2004-10-15 15:22 ` Paul Fulghum
2004-10-15 16:18 ` Alan Stern
2004-10-15 16:48 ` Paul Fulghum
2004-10-15 17:21 ` Alan Stern
2004-10-15 17:36 ` Paul Fulghum [this message]
2004-10-15 20:42 ` Lee Revell
2004-10-15 21:14 ` Paul Fulghum
2004-10-16 16:07 ` [patch, 2.6.9-rc4-mm1] fix rmmod uhci_hcd oops Ingo Molnar
2004-10-17 19:47 ` Laurent Riffard
2004-10-15 17:22 ` [linux-usb-devel] Re: 2.6.9-rc4-mm1 : oops when rmmod uhci_hcd [was: 2.6.9-rc3-mm2 : oops...] David Brownell
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=1097861761.2820.18.camel@deimos.microgate.com \
--to=paulkf@microgate.com \
--cc=greg@kroah.com \
--cc=laurent.riffard@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=stern@rowland.harvard.edu \
/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