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>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"logang@deltatee.com" <logang@deltatee.com>
Subject: [PATCH v9 0/4] PCI: Patch series to support Thunderbolt without any BIOS support
Date: Tue, 29 Oct 2019 15:27:59 +0000 [thread overview]
Message-ID: <SL2P216MB01877B771222A6E1699D14F480610@SL2P216MB0187.KORP216.PROD.OUTLOOK.COM> (raw)
Since last time:
Broken off two patches from the series to be dealt with separately.
Adding const like Mika suggested gives compile warning due to
pci_resource_alignment() function.
Does it matter that the dates on my patches might be out of date? I do
not normally re-create them.
I do "git am patchfile" and then do "git commit --amend ."
It is late and I am tired, so apologies if I have forgotten to fix some
things or made mistakes. If I do not get it done, I will keep putting it
off.
Thanks to all reviewers.
Nicholas Johnson (4):
PCI: Consider alignment of hot-added bridges when distributing
available resources
PCI: In extend_bridge_window() change available to new_size
PCI: Change extend_bridge_window() to set resource size directly
PCI: Allow extend_bridge_window() to shrink resource if necessary
drivers/pci/setup-bus.c | 182 +++++++++++++++++++---------------------
1 file changed, 88 insertions(+), 94 deletions(-)
--
2.23.0
reply other threads:[~2019-10-29 15:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=SL2P216MB01877B771222A6E1699D14F480610@SL2P216MB0187.KORP216.PROD.OUTLOOK.COM \
--to=nicholas.johnson-opensource@outlook.com.au \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--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).