linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Mason <jon.mason@broadcom.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,
	BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
	open list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] PCI: iproc: MPS fix and quirks
Date: Wed, 8 Feb 2017 17:33:46 -0500	[thread overview]
Message-ID: <CAC3K-4o2czeCdtATwZCLzN9H-PaPUgm5GaUXqBsAFD2ueuUDCw@mail.gmail.com> (raw)
In-Reply-To: <20170208215508.GA4800@bhelgaas-glaptop.roam.corp.google.com>

On Wed, Feb 8, 2017 at 4:55 PM, Bjorn Helgaas <helgaas@kernel.org> wrote:
> On Fri, Jan 27, 2017 at 04:44:07PM -0500, Jon Mason wrote:
>> A patch that corrects an issue where the MPS could not be set, and
>> another that fixes some quirks in the PAXC
>>
>> Jon Mason (2):
>>   PCI: iproc: allow the MPS to be set
>>   PCI: Add quirk entry for NS2 PAXC PCI
>>
>>  drivers/pci/host/pcie-iproc.c |  5 ++++-
>>  drivers/pci/quirks.c          | 21 +++++++++++++++++++++
>>  2 files changed, 25 insertions(+), 1 deletion(-)
>
> Applied with Ray's ack to pci/host-iproc for v4.11, thanks!
>
> It looks to me like several other drivers need a similar MPS fix.
> I'll CC you on the patches.

I'm happy to look at whatever you want to CC me on, but this is an SoC
thing that I do not believe is applicable to the standard PCI device
(if that is what you are referring to).

Thanks,
Jon

>
> Bjorn

      reply	other threads:[~2017-02-08 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 21:44 [PATCH 0/2] PCI: iproc: MPS fix and quirks Jon Mason
2017-01-27 21:44 ` [PATCH 1/2] PCI: iproc: allow the MPS to be set Jon Mason
2017-01-27 21:44 ` [PATCH 2/2] PCI: Add quirk entry for NS2 PAXC PCI Jon Mason
2017-01-27 21:46 ` [PATCH 0/2] PCI: iproc: MPS fix and quirks Ray Jui
2017-02-08 21:55 ` Bjorn Helgaas
2017-02-08 22:33   ` Jon Mason [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=CAC3K-4o2czeCdtATwZCLzN9H-PaPUgm5GaUXqBsAFD2ueuUDCw@mail.gmail.com \
    --to=jon.mason@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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).