From: Bjorn Helgaas <helgaas@kernel.org>
To: 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>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Logan Gunthorpe <logang@deltatee.com>
Subject: Re: [PATCH v12 0/4] PCI: Patch series to improve Thunderbolt enumeration
Date: Tue, 17 Dec 2019 09:12:48 -0600 [thread overview]
Message-ID: <20191217151248.GA165530@google.com> (raw)
In-Reply-To: <PSXP216MB043892C04178AB333F7AF08C80580@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM>
On Mon, Dec 09, 2019 at 12:59:29PM +0000, Nicholas Johnson wrote:
> Hi all,
>
> Since last time:
> Reverse Christmas tree for a couple of variables
>
> Changed while to whilst (sounds more formal, and so that
> grepping for "while" only brings up code)
>
> Made sure they still apply to latest Linux v5.5-rc1
>
> Kind regards,
> Nicholas
>
> Nicholas Johnson (4):
> 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
I have tentatively applied these to pci/resource for v5.6, but I need
some kind of high-level description for why we want these changes.
The commit logs describe what the code does, and that's good, but we
really need a little more of the *why* and what the user-visible
benefit is. I know some of this was in earlier postings, but it seems
to have gotten lost along the way.
Bjorn
next prev parent reply other threads:[~2019-12-17 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:59 [PATCH v12 0/4] PCI: Patch series to improve Thunderbolt enumeration Nicholas Johnson
2019-12-10 21:38 ` Bjorn Helgaas
2019-12-12 10:23 ` Nicholas Johnson
2019-12-13 18:04 ` Bjorn Helgaas
2019-12-17 15:12 ` Bjorn Helgaas [this message]
2019-12-18 0:54 ` Nicholas Johnson
2019-12-20 0:03 ` Bjorn Helgaas
2019-12-20 8:50 ` Nicholas Johnson
2019-12-20 10:18 ` Mika Westerberg
2019-12-20 14:38 ` Bjorn Helgaas
2019-12-21 5:48 ` Nicholas Johnson
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=20191217151248.GA165530@google.com \
--to=helgaas@kernel.org \
--cc=benh@kernel.crashing.org \
--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.