From: Bjorn Helgaas <bhelgaas@google.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/10] PCI: clip firmware assigned resources
Date: Thu, 15 Jan 2015 16:24:22 -0600 [thread overview]
Message-ID: <20150115222422.GB29776@google.com> (raw)
In-Reply-To: <1421296297-6371-1-git-send-email-yinghai@kernel.org>
On Wed, Jan 14, 2015 at 08:31:27PM -0800, Yinghai Lu wrote:
> During the fix https://bugzilla.kernel.org/show_bug.cgi?id=85491,
> Bjorn suggest that we should clip the resources instead of just
> reject them.
>
> We should only need first two for x86. others for related arches
> to keep them consistent.
>
> -v2: only handle bridge resource, and add pci_claim_bridge_resource
> in pci core code.
>
> Thanks
>
> Yinghai
>
> Yinghai Lu (10):
> PCI: clip firmware assigned resource under parent bridge's
> PCI, x86: clip firmware assigned resource under parent bridge's
> PCI, alpha: clip firmware assigned resource under parent bridge's
> PCI, frv: clip firmware assigned resource under parent bridge's
> PCI, ia64: clip firmware assigned resource under parent bridge's
> PCI, microblaze: clip firmware assigned resource under parent bridge's
> PCI, mn10300: clip firmware assigned resource under parent bridge's
> PCI, parisc: clip firmware assigned resource under parent bridge's
> PCI, powerpc: clip firmware assigned resource under parent bridge's
> PCI, sparc: clip firmware assigned resource under parent bridge's
>
> arch/alpha/kernel/pci.c | 8 +++--
> arch/frv/mb93090-mb00/pci-frv.c | 2 +-
> arch/ia64/pci/pci.c | 48 +++++++++++++---------------
> arch/microblaze/pci/pci-common.c | 13 +++++++-
> arch/mn10300/unit-asb2305/pci-asb2305.c | 2 +-
> arch/mn10300/unit-asb2305/pci.c | 47 +++++++++++++--------------
> arch/powerpc/kernel/pci-common.c | 12 ++++++-
> arch/sparc/kernel/pci.c | 5 ++-
> arch/x86/pci/i386.c | 2 +-
> drivers/parisc/lba_pci.c | 5 ++-
> drivers/pci/bus.c | 39 +++++++++++++++++++++++
> drivers/pci/pci.h | 1 +
> drivers/pci/setup-bus.c | 56 ++++++++++++++++++++++++++-------
> include/linux/pci.h | 1 +
> 14 files changed, 165 insertions(+), 76 deletions(-)
Applied to for-linus for v3.19, thanks. This is significantly different
from v1, so I didn't add acks and testing info from Helge and Wei.
Bjorn
prev parent reply other threads:[~2015-01-15 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 4:31 [PATCH v2 00/10] PCI: clip firmware assigned resources Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 01/10] PCI: clip firmware assigned resource under parent bridge's Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 02/10] PCI, x86: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 03/10] PCI, alpha: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 04/10] PCI, frv: " Yinghai Lu
2015-01-15 4:51 ` Yinghai Lu
2015-01-15 16:19 ` Bjorn Helgaas
2015-01-15 4:31 ` [PATCH v2 05/10] PCI, ia64: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 06/10] PCI, microblaze: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 07/10] PCI, mn10300: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 08/10] PCI, parisc: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 09/10] PCI, powerpc: " Yinghai Lu
2015-01-15 4:31 ` [PATCH v2 10/10] PCI, sparc: " Yinghai Lu
2015-01-16 0:14 ` David Miller
2015-01-15 22:24 ` Bjorn Helgaas [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=20150115222422.GB29776@google.com \
--to=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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