On Thu, 2009-10-01 at 18:43 -0700, James Bottomley wrote: > On Thu, 2009-10-01 at 17:47 -0700, Chris Wright wrote: > > * Alok Kataria (akataria@xxxxxxxxxx) wrote: > > > VMware PVSCSI driver - v5. > > > > Were you still planning on renaming the driver to something less generic > > (like vmw_pvscsi)? > Yeah I will rename it. Though, I will skip renaming all the function names, they have a pvscsi_ prefix right now. Since they are defined static it should be okay to keep them as is, I think. Yeah, I will make sure that the proc file name and other printk prefixes are modified with the new module name. > Actually it's not a paravirt driver either, so something like > vmwarevscsi would be fine. I would prefer keeping pvscsi in the module name just so that existing users are not confused, the adapter that the backend exports is named as pvscsi too. So something like vmw_pvscsi should be good enough to be non-generic at the same time being close to our existing module name. Thanks, Alok -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
