From: "mika.westerberg@linux.intel.com" <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"logang@deltatee.com" <logang@deltatee.com>
Subject: Re: [PATCH v8 0/6] Patch series to support Thunderbolt without any BIOS support
Date: Thu, 3 Oct 2019 15:19:46 +0300 [thread overview]
Message-ID: <20191003121946.GS2819@lahna.fi.intel.com> (raw)
In-Reply-To: <SL2P216MB01873757CFAE0E4B02F1BBE080C00@SL2P216MB0187.KORP216.PROD.OUTLOOK.COM>
On Fri, Jul 26, 2019 at 12:52:58PM +0000, Nicholas Johnson wrote:
> Patch series rebased to 5.3-rc1.
>
> If possible, please have a quick read over while I am away (2019-07-27
> to mid 2019-08-04), so I can fix any mistakes or make simple changes to
> get problems out of the way for a more thorough examination later.
>
> Thanks!
>
> Kind regards,
> Nicholas
>
> Nicholas Johnson (6):
> 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
> PCI: Add hp_mmio_size and hp_mmio_pref_size parameters
> PCI: Fix bug resulting in double hpmemsize being assigned to MMIO
> window
Hi Bjorn,
What's the status of this series? I don't see them in v5.4-rc1.
Thanks!
next prev parent reply other threads:[~2019-10-03 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 12:52 [PATCH v8 0/6] Patch series to support Thunderbolt without any BIOS support Nicholas Johnson
2019-10-03 12:19 ` mika.westerberg [this message]
2019-10-04 13:08 ` Bjorn Helgaas
2019-10-04 15:00 ` 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=20191003121946.GS2819@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--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=nicholas.johnson-opensource@outlook.com.au \
/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).