> > .map = mbochs_kmap_dmabuf, > > + .unmap = mbochs_kunmap_dmabuf, > > .mmap = mbochs_mmap_dmabuf, > > }; > > > > Is this a fix for v4.18? Yes. > AFAICT, the kmap_atomic removal is only in > next, not yet upstream and hopefully includes this sample driver before > hitting mainline. Should we therefore have a v4.18-rc based patch for > this to include before v4.18 to resolve this? The kmap_atomic interface will be removed in 4.19 because nobody uses it, so dropping the mbochs implementation already in 4.18 should not cause any issues. So just queue both for 4.18 would be the easiest way do deal with the dependency I think. cheers, Gerd -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
