linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: aik@au1.ibm.com, Wei Yang <weiyang@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/powernv: clear the refcount for pci_dev on powernv platform
Date: Wed, 23 Apr 2014 10:26:18 +1000	[thread overview]
Message-ID: <1398212778.19682.129.camel@pasglop> (raw)
In-Reply-To: <20140422230033.GA12208@shangw>

On Wed, 2014-04-23 at 09:00 +1000, Gavin Shan wrote:
> The side effect of holding pci_dev refcount is the pci_dev, eeh_dev,
> eeh_pe instance can't be free'ed during fully hotplug though EEH can
> survive. It's reasonable to remove it.

Allright. Can you guys refresh that patch with an updated cset
comment and shoot it upstream ?

Thanks !

Cheers,
Ben.

  reply	other threads:[~2014-04-23  0:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21  2:25 [PATCH 1/2] powerpc/powernv: clear the refcount for pci_dev on powernv platform Wei Yang
2014-04-21  2:25 ` [PATCH 2/2] powerpc/powernc: revert part of commit d905c5df(PPC: POWERNV: move iommu_add_device earlier) Wei Yang
2014-04-21  3:37   ` Benjamin Herrenschmidt
2014-04-21  5:22     ` Wei Yang
2014-04-21  6:11       ` Wei Yang
2014-04-21  3:35 ` [PATCH 1/2] powerpc/powernv: clear the refcount for pci_dev on powernv platform Benjamin Herrenschmidt
2014-04-21  6:03   ` Wei Yang
2014-04-21 23:34 ` Gavin Shan
2014-04-22  7:44   ` Wei Yang
2014-04-22  8:25     ` Benjamin Herrenschmidt
2014-04-22  9:44       ` Wei Yang
2014-04-22 23:00       ` Gavin Shan
2014-04-23  0:26         ` Benjamin Herrenschmidt [this message]
2014-04-23  1:56           ` Wei Yang

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=1398212778.19682.129.camel@pasglop \
    --to=benh@au1.ibm.com \
    --cc=aik@au1.ibm.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=weiyang@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).