<html><head></head><body dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="ApplePlainTextBody"><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="ApplePlainTextBody"><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="ApplePlainTextBody"><div class="ApplePlainTextBody"><br><blockquote type="cite">On Feb 22, 2018, at 10:13 PM, Andrew Donnellan <andrew.donnellan@au1.ibm.com> wrote:<br><br>On 23/02/18 09:20, Uma Krishnan wrote:<br><blockquote type="cite">This patch series adds OpenCXL support to the cxlflash driver. With<br>this support, new devices using the OpenCXL transport will be supported<br>by the cxlflash driver along with the existing CXL devices. An effort is<br>made to keep this transport specific function independent of the existing<br>core driver that communicates with the AFU.<br></blockquote><br>It's "OpenCAPI" for the standard, and "ocxl" for the driver - I'd rather not add "OpenCXL" to our already somewhat confusing proliferation of names :)<br><br></blockquote><br>I agree. I will fix it in V2. Thanks for the feedback.<br><br><blockquote type="cite">I'll try to review as much of the ocxl-specific stuff as I can get to, though I'm a bit busy with the OpenCAPI skiboot work and reviewing the libocxl userspace library at the moment.<br><br><br>Andrew<br><br>-- <br>Andrew Donnellan OzLabs, ADL Canberra<br>andrew.donnellan@au1.ibm.com IBM Australia Limited<br></blockquote><br></div></div></div></body></html>