From: Patrick Mochel <mochel@osdl.org>
To: Matt Domsch <Matt_Domsch@Dell.com>
Cc: Greg KH <greg@kroah.com>, <alan@redhat.com>,
<linux-kernel@vger.kernel.org>, <jgarzik@redhat.com>
Subject: Re: [RFC][PATCH] Dynamic PCI Device IDs
Date: Tue, 13 May 2003 14:33:25 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0305131432410.9816-100000@cherise> (raw)
In-Reply-To: <Pine.LNX.4.44.0305131428050.9816-100000@cherise>
On Tue, 13 May 2003, Patrick Mochel wrote:
>
> On Tue, 6 May 2003, Matt Domsch wrote:
>
> > > You can't just call driver_attach(), as the bus semaphore needs to be
> > > locked before doing so. In short, you almost need to duplicate
> > > bus_add_driver(), but not quite :)
> >
> > Right, and it seems to work. I made driver_attach non-static, declared
> > it extern in pci.h, and call it in pci-driver.c while holding the bus
> > semaphore and references to the driver and the bus. This also let me
> > delete my probe_each_pci_dev() function and let the driver core
> > handle it.
> >
> > Pat, can you ack the changes to bus.c and device.h please?
>
> ACK. I'll add them to my tree.
I take that back, since it's already checked into your BK tree. Go forth
and merge.
-pat
next prev parent reply other threads:[~2003-05-13 21:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 2:04 [RFC][PATCH] Dynamic PCI Device IDs Matt_Domsch
2003-05-06 3:56 ` Greg KH
2003-05-06 16:35 ` Matt Domsch
2003-05-10 0:11 ` Greg KH
2003-05-13 21:28 ` Patrick Mochel
2003-05-13 21:33 ` Patrick Mochel [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 0:39 Matt_Domsch
2003-05-02 23:15 ` Greg KH
2003-05-05 5:37 ` Jeff Garzik
2003-05-06 0:17 ` Greg KH
2003-05-05 22:51 ` Matt Domsch
2003-05-06 0:15 ` Greg KH
2003-04-30 21:45 Matt Domsch
2003-04-30 21:53 ` Jeff Garzik
2003-04-30 22:24 ` Greg KH
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=Pine.LNX.4.44.0305131432410.9816-100000@cherise \
--to=mochel@osdl.org \
--cc=Matt_Domsch@Dell.com \
--cc=alan@redhat.com \
--cc=greg@kroah.com \
--cc=jgarzik@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).