linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Cc: nfont@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
	paulus@samba.org
Subject: Re: [PATCH] powerpc/pci: reorder pci bus/bridge unregistration during PHB removal
Date: Tue, 29 Jul 2014 11:44:16 +1000	[thread overview]
Message-ID: <1406598256.11977.1.camel@concordia> (raw)
In-Reply-To: <1406594911-7097-1-git-send-email-tyreld@linux.vnet.ibm.com>

On Mon, 2014-07-28 at 20:48 -0400, Tyrel Datwyler wrote:
> Commit bcdde7e made __sysfs_remove_dir() recursive and introduced a BUG_ON
> during PHB removal while attempting to delete the power managment attribute
> group of the bus. This is a result of tearing the bridge and bus devices down
> out of order in remove_phb_dynamic. Since, the the bus resides below the bridge
> in the sysfs device tree it should be torn down first.
> 
> This patch simply moves the device_unregister call for the PHB bridge device
> after the device_unregister call for the PHB bus.
> 
> Signed-off-by: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>

That commit went into 3.13, so shouldn't this be CC to stable?

And also:

  Fixes: bcdde7e221a8 ("sysfs: make __sysfs_remove_dir() recursive")

cheers

  reply	other threads:[~2014-07-29  1:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  0:48 [PATCH] powerpc/pci: reorder pci bus/bridge unregistration during PHB removal Tyrel Datwyler
2014-07-29  1:44 ` Michael Ellerman [this message]
2014-07-29 17:54   ` Tyrel Datwyler
  -- strict thread matches above, loose matches on Subject: below --
2014-07-29 17:48 Tyrel Datwyler

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=1406598256.11977.1.camel@concordia \
    --to=mpe@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=tyreld@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).