From: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>
To: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
Cc: Ian Munsie <imunsie@au1.ibm.com>,
Philippe Bergheaud <felix@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
mikey <mikey@neuling.org>, manoj <manoj@linux.vnet.ibm.com>
Subject: Re: [v6, 1/2] cxl: Add mechanism for delivering AFU driver specific events
Date: Tue, 21 Jun 2016 08:27:34 -0500 [thread overview]
Message-ID: <2686A514-2808-4F08-8514-5E08B5D3608A@linux.vnet.ibm.com> (raw)
In-Reply-To: <87eg7qg79t.fsf@vajain21.in.ibm.com>
> On Jun 21, 2016, at 5:34 AM, Vaibhav Jain <vaibhav@linux.vnet.ibm.com> =
wrote:
>=20
> Hi Ian,
>=20
> Ian Munsie <imunsie@au1.ibm.com> writes:
>=20
>> Excerpts from Vaibhav Jain's message of 2016-06-20 14:20:16 +0530:
>>=20
>> What exactly is the use case for this API? I'd vote to drop it if we =
can
>> do without it.
> Agree with this. Functionality of this API can be merged with
> cxl_set_driver_ops when called with NULL arg for cxl_afu_driver_ops.
Passing a NULL arg instead of calling an 'unset' API is fine with us.
I'll add that for cxlflash, I can't envision a scenario where we'll =
unset the
driver ops for a context.
next prev parent reply other threads:[~2016-06-21 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 14:13 [v6, 1/2] cxl: Add mechanism for delivering AFU driver specific events Philippe Bergheaud
2016-06-16 14:13 ` [v6,2/2] cxl: Add set and get private data to context struct Philippe Bergheaud
2016-06-17 16:21 ` [v6, 1/2] cxl: Add mechanism for delivering AFU driver specific events Matthew R. Ochs
2016-06-20 8:50 ` Vaibhav Jain
2016-06-21 4:49 ` Ian Munsie
2016-06-21 10:34 ` Vaibhav Jain
2016-06-21 13:27 ` Matthew R. Ochs [this message]
2016-06-22 14:02 ` Philippe Bergheaud
2016-06-22 14:02 ` Philippe Bergheaud
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=2686A514-2808-4F08-8514-5E08B5D3608A@linux.vnet.ibm.com \
--to=mrochs@linux.vnet.ibm.com \
--cc=felix@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manoj@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--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).