mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Subject: [PATCH v5 0/5] PCI: Patch series to support Thunderbolt without any BIOS support
Date: Sun, 5 May 2019 14:40:20 +0000	[thread overview]
Message-ID: <PS2P216MB064229018EE9B0CE03EE274380370@PS2P216MB0642.KORP216.PROD.OUTLOOK.COM> (raw)

Since PATCH v4:

I have added some of the evidence and bug reports into the applicable
patches.

Users of pci=hpmemsize should not notice any changes in functionality
with this patch series when upgrading the kernel. I realised I could
make the variable to achieve this reside in pci_setup, rather than
globally.

Please let me know if anything else needs changing.

Nicholas Johnson (5):
  PCI: Consider alignment of hot-added bridges when distributing
    resources
  PCI: Modify extend_bridge_window() to set resource size directly
  PCI: Fix bug resulting in double hpmemsize being assigned to MMIO
    window
  PCI: Add pci=hpmemprefsize parameter to set MMIO_PREF size
    independently
  PCI: Cleanup block comments in setup-bus.c to match kernel style

 .../admin-guide/kernel-parameters.txt         |   7 +-
 drivers/pci/pci.c                             |  18 +-
 drivers/pci/setup-bus.c                       | 568 +++++++++---------
 include/linux/pci.h                           |   3 +-
 4 files changed, 317 insertions(+), 279 deletions(-)

-- 
2.19.1


             reply	other threads:[~2019-05-05 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 14:40 Nicholas Johnson [this message]
2019-05-07 23:32 ` Bjorn Helgaas

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=PS2P216MB064229018EE9B0CE03EE274380370@PS2P216MB0642.KORP216.PROD.OUTLOOK.COM \
    --to=nicholas.johnson-opensource@outlook.com.au \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®