public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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@linux.intel.com"
	<mika.westerberg@linux.intel.com>,
	"corbet@lwn.net" <corbet@lwn.net>
Subject: Re: [PATCH v3 0/5] PCI: Patch series to support Thunderbolt without any BIOS support
Date: Mon, 15 Apr 2019 17:20:01 -0500	[thread overview]
Message-ID: <20190415222001.GN126710@google.com> (raw)
In-Reply-To: <PS2P216MB06429DB03193EF6635554275802B0@PS2P216MB0642.KORP216.PROD.OUTLOOK.COM>

On Mon, Apr 15, 2019 at 05:08:41PM +0000, Nicholas Johnson wrote:
> I have split the last patch into the two patches as suggested. One to 
> add the new parameter and another to rename them nicely.
> 
> There is no longer depreciation of the old kernel parameters - they are 
> simply dropped, as suggested.

I did not actually suggest dropping the old parameters.  I said I
wasn't sure the user confusion of deprecating the old names in favor
of new names was worth the trouble.  I suspect we should just *add*
one new parameter and leave the old ones unchanged.

> I would find it cleaner to just do a single patch without the 
> depreciation, as both patches change the same things, doubling up on the 
> number of patch lines. I can still do this if requested.
> 
> Bjorn has fixed a trivial problem with the second patch in the series 
> not applying cleanly due to changes since I first sent it. He said not 
> to bother fixing it.

What I actually meant was "you correctly posted v2 based on my master
branch at the time, and since my master branch has moved from v5.0-rc1
to v5.1-rc1 since your v2 post, I'll do trivial fixes for that."

But since you're posting v3 *today*, and my master branch has been at
v5.1-rc1 since March 18, you should rebase your patches on top of that
branch first.

> Nicholas Johnson (5):
>   PCI: Consider alignment of hot-added bridges when distributing
>     available resources
>   PCI: Cleanup comments in setup-bus.c to meet kernel coding style
>     guidelines

We also talked about moving trivial cleanups to be at the end.  The
important things should be first in the series, with cleanups at the
end.  That way backporting is easier, since people may want to
backport only the real fixes, ignoring things like typo fixes.

>   PCI: Fix serious bug when sizing bridges with additional size
>   PCI: modify kernel parameters to differentiate between MMIO and
>     MMIO_PREF sizes
>   PCI: Rename pci=hpiosize,hpmemsize,hpmemprefsize to be more readable
> 
>  .../admin-guide/kernel-parameters.txt         |   7 +-
>  drivers/pci/pci.c                             |  18 +-
>  drivers/pci/setup-bus.c                       | 512 +++++++++---------
>  include/linux/pci.h                           |   3 +-
>  4 files changed, 287 insertions(+), 253 deletions(-)
> 
> -- 
> 2.20.1
> 

      reply	other threads:[~2019-04-15 22:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 17:08 [PATCH v3 0/5] PCI: Patch series to support Thunderbolt without any BIOS support Nicholas Johnson
2019-04-15 22:20 ` 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=20190415222001.GN126710@google.com \
    --to=helgaas@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox