From: Bjorn Helgaas <helgaas@kernel.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Kit Chow <kchow@gigaio.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v5] PCI: Fix disabling of bridge BARs when assigning bus resources
Date: Tue, 14 Jan 2020 13:06:30 -0600 [thread overview]
Message-ID: <20200114190630.GA262043@google.com> (raw)
In-Reply-To: <f15334a9-6cac-803d-7e64-28c74c4d12af@deltatee.com>
On Tue, Jan 14, 2020 at 11:07:12AM -0700, Logan Gunthorpe wrote:
> On 2020-01-13 1:07 p.m., Bjorn Helgaas wrote:
> > Applied to pci/resource for v5.6, thanks!
> >
> > I added a check of pci_is_bridge() as another hint that this is really
> > a bridge-specific issue. Let me know if that breaks anything.
> >
> > commit 9db8dc6d0785 ("PCI: Don't disable bridge BARs when assigning bus resources")
> > Author: Logan Gunthorpe <logang@deltatee.com>
> > Date: Wed Jan 8 14:32:08 2020 -0700
>
> Thanks! I was going to test the pci/resource branch, but I haven't seen
> the patch in your repo yet... Current head is
>
> 86f98025a075 ("PCI: Allow extend_bridge_window() to shrink resource if
> necessary")
Pushed. I'm anticipating some tweaks to Nicholas' patches on that
branch, so I put yours at the base.
prev parent reply other threads:[~2020-01-14 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 21:32 [PATCH v5] PCI: Fix disabling of bridge BARs when assigning bus resources Logan Gunthorpe
2020-01-13 20:07 ` Bjorn Helgaas
2020-01-14 18:07 ` Logan Gunthorpe
2020-01-14 19:06 ` Bjorn Helgaas [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=20200114190630.GA262043@google.com \
--to=helgaas@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=kchow@gigaio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mika.westerberg@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.