Re: [v6, 1/2] cxl: Add mechanism for delivering AFU driver specific events

On Jun 21, 2016, at 5:34 AM, Vaibhav Jain [off-list ref] =

wrote:

=20
Hi Ian,
=20
Ian Munsie [off-list ref] writes:
=20

quoted

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

quoted

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.