> From: Alex Williamson <alex.williamson@xxxxxxxxxx> > Sent: Tuesday, March 8, 2022 3:53 AM > > > > > I think we still require acks from Bjorn and Zaibo for select patches > > > in this series. > > > > I checked with Ziabo. He moved projects and is no longer looking into > crypto stuff. > > Wangzhou and LiuLongfang now take care of this. Received acks from > Wangzhou > > already and I will request Longfang to provide his. Hope that's ok. > > Maybe a good time to have them update MAINTAINERS as well. Thanks, > I have one question here (similar to what we discussed for mdev before). Now we are adding vendor specific drivers under /drivers/vfio. Two drivers on radar and more will come. Then what would be the criteria for accepting such a driver? Do we prefer to a model in which the author should provide enough background for vfio community to understand how it works or as done here just rely on the PF driver owner to cover device specific code? If the former we may need document some process for what information is necessary and also need secure increased review bandwidth from key reviewers in vfio community. If the latter then how can we guarantee no corner case overlooked by both sides (i.e. how to know the coverage of total reviews)? Another open is who from the PF driver sub-system should be considered as the one to give the green signal. If the sub-system maintainer trusts the PF driver owner and just pulls commits from him then having the r-b from the PF driver owner is sufficient. But if the sub-system maintainer wants to review detail change in every underlying driver then we probably also want to get the ack from the maintainer. Overall I didn't mean to slow down the progress of this series. But above does be some puzzle occurred in my review. 😊 Thanks Kevin
