From: John Rose <johnrose@austin.ibm.com>
To: colpatch@us.ibm.com
Cc: greg KH <gregkh@us.ibm.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6 probe.c "pcibus_class" Device Class, release function
Date: Wed, 04 Feb 2004 11:22:08 -0600 [thread overview]
Message-ID: <1075915328.3026.16.camel@verve> (raw)
In-Reply-To: <1075910719.3026.2.camel@verve>
After testing, it would appear that it does. Perfect! Thanks.
John
On Wed, 2004-02-04 at 10:05, John Rose wrote:
> Oops - quick question. Does unregistering blow away the cpuaffinity
> attr and the bridge symlink?
>
> Thanks-
> John
>
> On Wed, 2004-02-04 at 10:00, John Rose wrote:
> > > put() does need to be
> > > called twice because the bridge device is get()'d twice: once when the
> > > device is registered and once when it's bus device grabs a reference to it.
> >
> > Looks great, thanks Matt.
> >
> > John
next prev parent reply other threads:[~2004-02-04 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 22:33 2.6 probe.c "pcibus_class" Device Class, release function John Rose
2004-02-04 1:31 ` Matthew Dobson
2004-02-04 16:00 ` John Rose
2004-02-04 16:05 ` John Rose
2004-02-04 17:22 ` John Rose [this message]
2004-02-04 18:01 ` 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=1075915328.3026.16.camel@verve \
--to=johnrose@austin.ibm.com \
--cc=colpatch@us.ibm.com \
--cc=gregkh@us.ibm.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