From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Stefan Assmann <sassmann@redhat.com>
Cc: linux-pci@vger.kernel.org, JBeulich@novell.com,
linux-acpi@vger.kernel.org, Olaf.Dabrunz@gmx.net, mingo@elte.hu,
bjorn.helgaas@hp.com, tglx@linutronix.de, lenb@kernel.org
Subject: Re: [PATCH 3/4] PCI: fix locking for pci_find_upstream_pcie_bridge and add declaration
Date: Thu, 18 Nov 2010 10:18:11 -0800 [thread overview]
Message-ID: <20101118101811.1fd1c3fd@jbarnes-desktop> (raw)
In-Reply-To: <20101118135237.2269.96220.sendpatchset@localhost6.localdomain6>
On Thu, 18 Nov 2010 08:52:28 -0500
Stefan Assmann <sassmann@redhat.com> wrote:
> From: Stefan Assmann <sassmann@redhat.com>
>
> Add header declaration of pci_find_upstream_pcie_bridge to pci.h. This will
> allow the boot interrupt reroute code, and others, to make use of this
> implementation. Also pci_find_upstream_pcie_bridge should take the pci_bus_sem
> semaphore while reading global PCI structures, so update the locking as well.
>
> Signed-off-by: Stefan Assmann <sassmann@redhat.com>
> ---
You should split this into two patches just to keep things separate,
but other than that it looks fine. I assume this set will go through
the ACPI tree, you can add my:
Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-11-18 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 13:51 [PATCH 0/4] x86: boot interrupt reroute fix Stefan Assmann
2010-11-18 13:52 ` [PATCH 1/4] ACPI: move struct acpi_prt_entry to actbl1.h Stefan Assmann
2010-11-18 13:52 ` [PATCH 2/4] ACPI: make acpi_pci_irq_find_prt_entry return a copy of a prt_entry Stefan Assmann
2010-11-18 13:52 ` [PATCH 3/4] PCI: fix locking for pci_find_upstream_pcie_bridge and add declaration Stefan Assmann
2010-11-18 18:18 ` Jesse Barnes [this message]
2010-11-18 13:52 ` [PATCH 4/4] PCI, ACPI: re-add boot interrupt reroute code in separate files Stefan Assmann
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=20101118101811.1fd1c3fd@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=JBeulich@novell.com \
--cc=Olaf.Dabrunz@gmx.net \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sassmann@redhat.com \
--cc=tglx@linutronix.de \
/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