From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Logan Gunthorpe <logang@deltatee.com>
Subject: Re: [PATCH v1 4/4] PCI: Allow extend_bridge_window() to shrink resource if necessary
Date: Wed, 15 Jan 2020 16:59:34 +0200 [thread overview]
Message-ID: <20200115145934.GJ2838@lahna.fi.intel.com> (raw)
In-Reply-To: <PSXP216MB043899E598E11CF7D4D9214380370@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM>
On Wed, Jan 15, 2020 at 02:51:02PM +0000, Nicholas Johnson wrote:
> Sorry, I was not meant to say you were not interested in getting it as
> good as possible. At the time, you had a goal to achieve (which you did)
> and at that point in time, it would not have been feasible to use
> pci=hpmemsize or similar before my patches were applied:
>
> c13704f5685d ("PCI: Avoid double hpmemsize MMIO window assignment")
> d7b8a217521c ("PCI: Add "pci=hpmmiosize" and "pci=hpmmioprefsize" parameters")
>
> What I was trying to say was not that you were not interested, but more
> that it was not a primary motivation for you at the time. Does this
> sound more accurate? Poor wording on my behalf.
Yes, it does and no worries :-) Just wanted to clarify that one.
prev parent reply other threads:[~2020-01-15 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 15:48 [PATCH v1 4/4] PCI: Allow extend_bridge_window() to shrink resource if necessary Nicholas Johnson
2020-01-07 20:34 ` Bjorn Helgaas
2020-01-08 1:36 ` Nicholas Johnson
2020-01-13 16:21 ` Mika Westerberg
2020-01-15 14:51 ` Nicholas Johnson
2020-01-15 14:59 ` 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=20200115145934.GJ2838@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=benh@kernel.crashing.org \
--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