Re: [PATCH v3 00/41] cxlflash: OCXL transport support and miscellaneous fixes

2 messages, 2 authors, 2018-03-29 · open the first message on its own page

Re: [PATCH v3 00/41] cxlflash: OCXL transport support and miscellaneous fixes

From: Martin K. Petersen <hidden>
Date: 2018-03-28 21:34:31

Uma,
This patch series adds OCXL support to the cxlflash driver. With this
support, new devices using the OCXL transport will be supported by the
cxlflash driver along with the existing CXL devices. An effort is made
to keep this transport specific function independent of the existing
core driver that communicates with the AFU.

The first three patches contain a minor fix and staging improvements.

This series is intended for 4.17 and is bisectable.
Something this big really needs to be submitted around rc2/rc3. It's way
too late in the cycle to ensure proper zeroday coverage for all these
commits.

I have started a 4.18/scsi-queue branch to hold this series for now.
The 4.18 branch will be rebased once 4.17rc1 is out in a few weeks. Your
changes won't show up in for-next until then either.

Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

Re: [PATCH v3 00/41] cxlflash: OCXL transport support and miscellaneous fixes

From: Uma Krishnan <hidden>
Date: 2018-03-29 18:35:30

On Mar 28, 2018, at 4:34 PM, Martin K. Petersen =
[off-list ref] wrote:
=20
=20
Uma,
=20
quoted
This patch series adds OCXL support to the cxlflash driver. With this
support, new devices using the OCXL transport will be supported by =
the
quoted
cxlflash driver along with the existing CXL devices. An effort is =
made
quoted
to keep this transport specific function independent of the existing
core driver that communicates with the AFU.
=20
The first three patches contain a minor fix and staging improvements.
=20
This series is intended for 4.17 and is bisectable.
=20
Something this big really needs to be submitted around rc2/rc3. It's =
way
too late in the cycle to ensure proper zeroday coverage for all these
commits.
=20
I have started a 4.18/scsi-queue branch to hold this series for now.
The 4.18 branch will be rebased once 4.17rc1 is out in a few weeks. =
Your
changes won't show up in for-next until then either.
I did send the first version of this series just after 4.16rc2 but the =
reviews took a while and the V3 is cutting close unless we do have an =
rc8 for 4.16 :)

I understand what you are saying and agree with you. Thanks for keeping =
me posted.=
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help