From: Jason Gunthorpe <jgg@ziepe.ca>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Felix Kuehling <Felix.Kuehling@amd.com>,
oded.gabbay@gmail.com, amd-gfx@lists.freedesktop.org,
Jay Cornwall <Jay.Cornwall@amd.com>,
linux-pci@vger.kernel.org, Ram Amrani <Ram.Amrani@cavium.com>,
Doug Ledford <dledford@redhat.com>,
Michal Kalderon <Michal.Kalderon@cavium.com>,
Ariel Elior <Ariel.Elior@cavium.com>
Subject: Re: [PATCH 29/37] PCI: Add pci_enable_atomic_ops_to_root
Date: Tue, 12 Dec 2017 16:42:43 -0700 [thread overview]
Message-ID: <20171212234243.GD16603@ziepe.ca> (raw)
In-Reply-To: <20171212232707.GF53955@bhelgaas-glaptop.roam.corp.google.com>
On Tue, Dec 12, 2017 at 05:27:07PM -0600, Bjorn Helgaas wrote:
> [+cc Ram, Michal, Ariel, Doug, Jason]
>
> The [29/37] in the subject makes it look like this is part of a larger
> series, but I can't find the rest of it on linux-pci or linux-kernel.
Didn't find the cover letter, but the AMD patchworks captured the series..
https://patchwork.freedesktop.org/project/amd-xorg-ddx/patches/
> I don't want to merge a new interface unless there's an in-tree user
> of it. I assume the rest of the series includes a user.
Looks like it.
I would also guess we will see users in drivers/infiniband emerge as
CPU coherent atomics are also a topic our hardware drivers will be
interested in. But I am not aware of any pending patches.
Jason
next prev parent reply other threads:[~2017-12-12 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1512792555-26042-1-git-send-email-Felix.Kuehling@amd.com>
2017-12-09 4:09 ` [PATCH 29/37] PCI: Add pci_enable_atomic_ops_to_root Felix Kuehling
2017-12-12 23:27 ` Bjorn Helgaas
2017-12-12 23:42 ` Jason Gunthorpe [this message]
2017-12-13 7:22 ` Oded Gabbay
2018-01-02 23:41 ` Felix Kuehling
2018-01-04 23:40 ` Bjorn Helgaas
2018-01-05 0:09 ` Felix Kuehling
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=20171212234243.GD16603@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Ariel.Elior@cavium.com \
--cc=Felix.Kuehling@amd.com \
--cc=Jay.Cornwall@amd.com \
--cc=Michal.Kalderon@cavium.com \
--cc=Ram.Amrani@cavium.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dledford@redhat.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=oded.gabbay@gmail.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