public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "mika.westerberg@linux.intel.com" <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
	"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: Fri, 4 Oct 2019 18:00:32 +0300	[thread overview]
Message-ID: <20191004150032.GK2819@lahna.fi.intel.com> (raw)
In-Reply-To: <20191004130803.GA41961@google.com>

On Fri, Oct 04, 2019 at 08:08:03AM -0500, Bjorn Helgaas wrote:
> On Thu, Oct 03, 2019 at 03:19:46PM +0300, mika.westerberg@linux.intel.com wrote:
> > 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.
> 
> They're still on my to-do list but are currently languishing because
> they touch critical but complicated code that I don't understand and
> nobody else has chimed in to help review them.  Testing reports would
> also be helpful.

I will test this next week as it solves one issue I reported some time ago.

I can also help you to review this, at least parts touching
extend_bridge_window() and pci_bus_distribute_available_resources(),
because those functions were added by me ;-)

      reply	other threads:[~2019-10-04 15:00 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
2019-10-04 13:08   ` Bjorn Helgaas
2019-10-04 15:00     ` mika.westerberg [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=20191004150032.GK2819@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=corbet@lwn.net \
    --cc=helgaas@kernel.org \
    --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