From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: Ian Munsie <imunsie@au1.ibm.com>,
Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
Cc: Michael Neuling <mikey@neuling.org>,
Michael Ellerman <michaele@au1.ibm.com>,
Matt Ochs <mrochs@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
Manoj Kumar <kumarmn@us.ibm.com>
Subject: Re: [PATCH v3 1/2] cxl: Add mechanism for delivering AFU driver specific events
Date: Fri, 11 Mar 2016 12:48:55 +1100 [thread overview]
Message-ID: <56E22407.6080609@au1.ibm.com> (raw)
In-Reply-To: <1457570763-sup-7740@delenn.ozlabs.ibm.com>
On 10/03/16 12:18, Ian Munsie wrote:
> On a related matter, we should send a patch to remove some of the
> leftover config options that were added to smooth the merging of
> cxlflash in the first place (CXL_KERNEL_API, CXL_EEH).
I'm happy to do that after this series is merged.
--
Andrew Donnellan Software Engineer, OzLabs
andrew.donnellan@au1.ibm.com Australia Development Lab, Canberra
+61 2 6201 8874 (work) IBM Australia Limited
next prev parent reply other threads:[~2016-03-11 1:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 1:48 [PATCH v3 1/2] cxl: Add mechanism for delivering AFU driver specific events Ian Munsie
2016-03-08 1:48 ` [PATCH v3 2/2] cxl: add set/get private data to context struct Ian Munsie
2016-03-08 7:59 ` Andrew Donnellan
2016-03-08 4:06 ` [PATCH v3 1/2] cxl: Add mechanism for delivering AFU driver specific events Matt Ochs
2016-03-08 7:59 ` Andrew Donnellan
2016-03-09 9:27 ` Frederic Barrat
2016-03-10 0:46 ` Ian Munsie
2016-03-10 1:26 ` Ian Munsie
2016-03-09 14:37 ` Vaibhav Jain
2016-03-09 16:41 ` Matt Ochs
2016-03-09 17:08 ` Frederic Barrat
2016-03-10 17:19 ` Vaibhav Jain
2016-03-10 1:18 ` Ian Munsie
2016-03-10 17:39 ` Vaibhav Jain
2016-03-11 1:48 ` Andrew Donnellan [this message]
2016-03-10 3:24 ` Michael Neuling
2016-03-10 17:23 ` Vaibhav Jain
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=56E22407.6080609@au1.ibm.com \
--to=andrew.donnellan@au1.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=kumarmn@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michaele@au1.ibm.com \
--cc=mikey@neuling.org \
--cc=mrochs@us.ibm.com \
--cc=vaibhav@linux.vnet.ibm.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).