From: Brian King <brking@linux.vnet.ibm.com>
To: mpe@ellerman.id.au
Cc: Frederic Barrat <fbarrat@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, mikey@neuling.org,
benh@kernel.crashing.org, clsoto@linux.vnet.ibm.com
Subject: Re: [PATCH v3] powerpc/powernv: Enable PCI peer-to-peer
Date: Mon, 31 Jul 2017 14:24:43 -0500 [thread overview]
Message-ID: <28e653f1-77cc-f0f4-2355-d2ec582c338f@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170717235048.11974-1-fbarrat@linux.vnet.ibm.com>
Michael,
What do we need on this one before we can pull into your -next branch?
Thanks,
Brian
--
Brian King
Power Linux I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2017-07-31 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 23:50 [PATCH v3] powerpc/powernv: Enable PCI peer-to-peer Frederic Barrat
2017-07-31 19:24 ` Brian King [this message]
2017-08-01 6:43 ` Michael Ellerman
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=28e653f1-77cc-f0f4-2355-d2ec582c338f@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=clsoto@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.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).