From: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Logan Gunthorpe <logang@deltatee.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Subject: [PATCH v1 0/3] PCI: Fix failure to assign BARs with alignment >1M with Thunderbolt
Date: Mon, 6 Jan 2020 15:45:09 +0000 [thread overview]
Message-ID: <PSXP216MB0438243F9C310CC98AF402F3803C0@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM> (raw)
This patch series is split from from [0] to make sign-off easier.
I have found a way to change the arguments of
pci_bus_distribute_available_resources() without making any functional
changes. I think it turned out very well. I hope everybody agrees.
I have tested and looked over for mistakes for several days, but there
could still be mistakes. I have also changed the commit messages and
might not be clear enough yet.
Best to get it out there and get feedback or it will never happen.
Removed Reviewed-by tags from Mika Westerberg because some things have
changed.
[0]
https://lore.kernel.org/lkml/PSXP216MB043892C04178AB333F7AF08C80580@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM/
Nicholas Johnson (3):
PCI: Remove redundant brackets in
pci_bus_distribute_available_resources()
PCI: Change pci_bus_distribute_available_resources() args to struct
resource
PCI: Consider alignment of hot-added bridges when distributing
available resources
drivers/pci/setup-bus.c | 106 +++++++++++++++++++++++-----------------
1 file changed, 61 insertions(+), 45 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-06 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 15:45 Nicholas Johnson [this message]
2020-01-13 14:12 ` [PATCH v1 0/3] PCI: Fix failure to assign BARs with alignment >1M with Thunderbolt Mika Westerberg
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=PSXP216MB0438243F9C310CC98AF402F3803C0@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM \
--to=nicholas.johnson-opensource@outlook.com.au \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mika.westerberg@linux.intel.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).