linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Yijing Wang <wangyijing@huawei.com>, Tony Luck <tony.luck@intel.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
	linux-pci@vger.kernel.org, linux-ia64@vger.kernel.org,
	Fenghua Yu <fenghua.yu@intel.com>,
	Hanjun Guo <guohanjun@huawei.com>,
	jiang.liu@huawei.com
Subject: Re: [PATCH -v5 0/8] Add hostbridge resource release to support root bus hotplug in IA64
Date: Fri, 14 Jun 2013 18:22:24 -0600	[thread overview]
Message-ID: <20130615002224.GA21643@google.com> (raw)
In-Reply-To: <1370504093-14908-1-git-send-email-wangyijing@huawei.com>

On Thu, Jun 06, 2013 at 03:34:45PM +0800, Yijing Wang wrote:
> ...
> Jiang Liu (1):
>   PCI/IA64: fix memleak for create pci root bus fail
> 
> Yijing Wang (7):
>   PCI/IA64: SN: remove sn_pci_window_fixup()
>   PCI/IA64: SN: use normal resource instead of pci_window
>   PCI/IA64: embed pci hostbridge resources into pci_root_info
>   PCI/IA64: Allocate pci_root_info instead of using stack
>   PCI/IA64: add host bridge resource release for _CRS path
>   PCI/IA64: introduce probe_pci_root_info() to manage  _CRS resource
>   PCI: Replace printks with appropriate pr_*()
> 
>  arch/ia64/include/asm/pci.h   |   10 +-
>  arch/ia64/pci/pci.c           |  236 ++++++++++++++++++++++++++++-------------
>  arch/ia64/sn/kernel/io_init.c |  109 +++++--------------
>  3 files changed, 192 insertions(+), 163 deletions(-)

Tony, what do you think about this?  It only touches ia64, and I
have no way to build or test it.  So maybe you should handle this?

I haven't reviewed it, but I think it's the right general direction,
at least.

Bjorn

  parent reply	other threads:[~2013-06-15  0:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  7:34 [PATCH -v5 0/8] Add hostbridge resource release to support root bus hotplug in IA64 Yijing Wang
2013-06-06  7:34 ` [PATCH -v5 1/8] PCI/IA64: SN: remove sn_pci_window_fixup() Yijing Wang
2013-06-14  8:42   ` Yijing Wang
2013-06-15  0:48     ` Bjorn Helgaas
2013-06-17  3:01       ` Yijing Wang
2013-06-06  7:34 ` [PATCH -v5 2/8] PCI/IA64: SN: use normal resource instead of pci_window Yijing Wang
2013-06-06  7:34 ` [PATCH -v5 3/8] PCI/IA64: embed pci hostbridge resources into pci_root_info Yijing Wang
2013-06-06  7:34 ` [PATCH -v5 4/8] PCI/IA64: Allocate pci_root_info instead of using stack Yijing Wang
2013-06-06  7:34 ` [PATCH -v5 5/8] PCI/IA64: fix memleak for create pci root bus fail Yijing Wang
2013-06-06  7:34 ` [PATCH -v5 6/8] PCI/IA64: add host bridge resource release for _CRS path Yijing Wang
2013-06-06  7:34 ` [PATCH -v5 7/8] PCI/IA64: introduce probe_pci_root_info() to manage _CRS resource Yijing Wang
2013-06-06  7:34 ` [PATCH -v5 8/8] PCI: Replace printks with appropriate pr_*() Yijing Wang
2013-06-15  0:22 ` Bjorn Helgaas [this message]
2013-06-17  2:56   ` [PATCH -v5 0/8] Add hostbridge resource release to support root bus hotplug in IA64 Yijing Wang
2013-06-17 22:57     ` Tony Luck
2013-06-17 23:10       ` Bjorn Helgaas
2013-06-18  1:03         ` Yijing Wang
2013-06-18  1:01       ` Yijing Wang

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=20130615002224.GA21643@google.com \
    --to=bhelgaas@google.com \
    --cc=fenghua.yu@intel.com \
    --cc=guohanjun@huawei.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=wangyijing@huawei.com \
    --cc=yinghai@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).