linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
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>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Logan Gunthorpe <logang@deltatee.com>
Subject: Re: [PATCH v1 0/3] PCI: Fix failure to assign BARs with alignment >1M with Thunderbolt
Date: Mon, 13 Jan 2020 16:12:12 +0200	[thread overview]
Message-ID: <20200113141212.GH2838@lahna.fi.intel.com> (raw)
In-Reply-To: <PSXP216MB0438243F9C310CC98AF402F3803C0@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM>

Hi,

On Mon, Jan 06, 2020 at 03:45:09PM +0000, Nicholas Johnson wrote:
> This patch series is split from from [0] to make sign-off easier.
> 
> I have found a way to change the arguments of 
> pci_bus_distribute_available_resources() without making any functional 
> changes. I think it turned out very well. I hope everybody agrees.
> 
> I have tested and looked over for mistakes for several days, but there 
> could still be mistakes. I have also changed the commit messages and 
> might not be clear enough yet.
> 
> Best to get it out there and get feedback or it will never happen.
> 
> Removed Reviewed-by tags from Mika Westerberg because some things have 
> changed.

In future it would be nice to spell out what exactly was changed since
the previous version so I don't have to dig that out and figure it out
myself.

This time it's fine :)

      reply	other threads:[~2020-01-13 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 15:45 [PATCH v1 0/3] PCI: Fix failure to assign BARs with alignment >1M with Thunderbolt Nicholas Johnson
2020-01-13 14:12 ` 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=20200113141212.GH2838@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --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;
as well as URLs for NNTP newsgroup(s).