From: Jon Masters <jcm@redhat.com>
To: Robin Murphy <robin.murphy@arm.com>,
Jayachandran C <jnair@caviumnetworks.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 2/2] PCI: quirks: Fix ThunderX2 dma alias handling
Date: Thu, 13 Apr 2017 02:43:07 -0400 [thread overview]
Message-ID: <1567687b-ef10-bd87-c1cd-6838de6cce13@redhat.com> (raw)
In-Reply-To: <2f6b5c29-c985-dbfc-8738-cbc9bd85e408@arm.com>
On 04/04/2017 10:28 AM, Robin Murphy wrote:
> So (at the risk of Jon mooing at me)
moooooooooooo
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2017-04-13 6:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 13:15 [PATCH v4 0/2] Handle Cavium ThunderX2 PCI topology quirk Jayachandran C
2017-04-03 13:15 ` [PATCH v4 1/2] PCI: Add device flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT Jayachandran C
2017-04-03 14:59 ` Robin Murphy
2017-04-03 13:15 ` [PATCH v4 2/2] PCI: quirks: Fix ThunderX2 dma alias handling Jayachandran C
2017-04-03 15:07 ` Robin Murphy
2017-04-04 11:50 ` Jayachandran C
2017-04-04 14:28 ` Robin Murphy
2017-04-10 11:38 ` Jayachandran C
2017-04-13 6:43 ` Jon Masters [this message]
2017-04-11 1:28 ` Bjorn Helgaas
2017-04-11 7:10 ` Jayachandran C
2017-04-11 13:41 ` Bjorn Helgaas
2017-04-11 15:27 ` Jayachandran C
2017-04-11 15:43 ` Jon Masters
2017-04-12 16:21 ` Bjorn Helgaas
2017-04-12 18:10 ` Jayachandran C
2017-04-12 19:11 ` Bjorn Helgaas
2017-04-12 20:41 ` Jayachandran C
2017-04-12 23:18 ` Bjorn Helgaas
2017-04-11 15:34 ` Robin Murphy
2017-04-11 13:44 ` [PATCH v4 0/2] Handle Cavium ThunderX2 PCI topology quirk Bjorn Helgaas
[not found] ` <CABhMZUXNhKSQALAHP1CBNfWMuw0J0XQ2rzusP4WR_HHH9ox5Yw@mail.gmail.com>
[not found] ` <CABhMZUXh=X5k1DQhUcaXD4t9GWfXms80xWV7sAh0ZXD8YK794g@mail.gmail.com>
2017-04-11 14:23 ` Bjorn Helgaas
2017-04-11 16:01 ` David Daney
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=1567687b-ef10-bd87-c1cd-6838de6cce13@redhat.com \
--to=jcm@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jnair@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=robin.murphy@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;
as well as URLs for NNTP newsgroup(s).