From: Ray Jui <ray.jui@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH INTERNAL 0/3] Add Broadcom PAXC related quirks
Date: Thu, 17 May 2018 10:23:46 -0700 [thread overview]
Message-ID: <025a6e7e-a6dc-c1ee-77cd-a78439bd17d9@broadcom.com> (raw)
In-Reply-To: <1526577692-21104-1-git-send-email-ray.jui@broadcom.com>
Hi Bjorn/Lorenzo,
My bad for having this "INTERNAL" tag in the subject. Please let me know
if you need me to send out another set with that removed.
Thanks,
Ray
On 5/17/2018 10:21 AM, Ray Jui wrote:
> This patch series adds quirks to work around a few issues related to
> certain revisions of Broadcom PAXC based PCIe root complexes
>
> This patch series is based off v4.17-rc5 and is available on GIHUB:
> repo: https://github.com/Broadcom/arm64-linux.git
> branch: sr-paxc-quirk-v1
>
> Ray Jui (3):
> PCI: iproc: Activate PAXC bridge quirk for more devices
> PCI: iproc: Fix up corrupted PAXC root complex config registers
> PCI: iproc: Disable MSI parsing in certain PAXC blocks
>
> drivers/pci/host/pcie-iproc.c | 34 ++++++++++++++-
> drivers/pci/quirks.c | 98 +++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 130 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2018-05-17 17:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 17:21 Ray Jui
2018-05-17 17:21 ` [PATCH INTERNAL 1/3] PCI: iproc: Activate PAXC bridge quirk for more devices Ray Jui
2018-05-17 17:21 ` [PATCH INTERNAL 2/3] PCI: iproc: Fix up corrupted PAXC root complex config registers Ray Jui
2018-05-18 9:19 ` poza
2018-05-30 17:27 ` Bjorn Helgaas
2018-05-30 17:43 ` Ray Jui
2018-06-12 0:18 ` Ray Jui
2018-05-17 17:21 ` [PATCH INTERNAL 3/3] PCI: iproc: Disable MSI parsing in certain PAXC blocks Ray Jui
2018-05-18 9:23 ` poza
2018-05-18 13:56 ` Lorenzo Pieralisi
2018-05-18 19:48 ` Ray Jui
2018-05-21 13:33 ` Lorenzo Pieralisi
2018-05-21 14:26 ` Robin Murphy
2018-05-22 16:48 ` Ray Jui
2018-05-22 16:52 ` Ray Jui
2018-07-04 15:13 ` Lorenzo Pieralisi
2018-07-04 15:44 ` Ray Jui
2018-05-17 17:23 ` Ray Jui [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=025a6e7e-a6dc-c1ee-77cd-a78439bd17d9@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
/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
Powered by JetHome