public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: John Rose <johnrose@austin.ibm.com>, 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, 4 Feb 2004 10:01:07 -0800	[thread overview]
Message-ID: <20040204180107.GB11614@kroah.com> (raw)
In-Reply-To: <40204B7E.6030408@us.ibm.com>

On Tue, Feb 03, 2004 at 05:31:42PM -0800, Matthew Dobson wrote:
> John Rose wrote:
> >The function release_pcibus_dev() in probe.c defines the release procedure 
> >for
> >device class pcibus_class.  I want to suggest that this function be 
> >scrapped :)
> >
> >This release function is called in the code path of 
> >class_device_unregister().
> >The pcibus_class devices aren't currently unregistered anywhere, from what 
> >I
> >can tell, so this release function is currently unused.  The runtime 
> >removal of
> >PCI buses from logical partitions on PPC64 requires the unregistration of 
> >these
> >class devices.  The natural place to do this IMHO is in 
> >pci_remove_bus_device()
> >in remove.c.  
> 
> You're right that the class device isn't currently unregistered, and 
> that was an oversight in the patch I originally sent.  Attatched is a 
> patch that remedies that situation.  pci_remove_bus_device() *is* the 
> natural place to unregister the class_dev, and that's just what the 
> patch does.

Thanks, I've applied this patch to my trees and will send off to Linus
in the next round of PCI patches.

greg k-h

      parent reply	other threads:[~2004-02-04 18:01 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
2004-02-04 18:01   ` Greg KH [this message]

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=20040204180107.GB11614@kroah.com \
    --to=greg@kroah.com \
    --cc=colpatch@us.ibm.com \
    --cc=gregkh@us.ibm.com \
    --cc=johnrose@austin.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