Greg KH
2022-May-16 06:13 UTC
[PATCH v2 2/3] vdpa: Add a device object for vdpa management device
On Mon, May 16, 2022 at 02:03:41PM +0800, Xie Yongji wrote:> Introduce a device object for vdpa management device to control > its lifecycle. And the device name will be used to match > VDPA_ATTR_MGMTDEV_DEV_NAME field of netlink message rather than > using parent device name. > > With this patch applied, drivers should use vdpa_mgmtdev_alloc() > or _vdpa_mgmtdev_alloc() to allocate a vDPA management device > before calling vdpa_mgmtdev_register(). And some buggy empty > release function can also be removed from the driver codes. > > Signed-off-by: Xie Yongji <xieyongji at bytedance.com> > --- > drivers/vdpa/ifcvf/ifcvf_main.c | 11 ++-- > drivers/vdpa/mlx5/net/mlx5_vnet.c | 11 ++-- > drivers/vdpa/vdpa.c | 92 ++++++++++++++++++++++++---- > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c | 39 ++++-------- > drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 46 +++++--------- > drivers/vdpa/vdpa_user/vduse_dev.c | 38 ++++-------- > include/linux/vdpa.h | 38 +++++++++++- > 7 files changed, 168 insertions(+), 107 deletions(-) >Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - This looks like a new version of a previously submitted patch, but you did not list below the --- line any changes from the previous version. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what needs to be done here to properly describe this. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot