Need advice on planning patches for staging/vme_user

Need advice on planning patches for staging/vme_user

[Soumya Negi]

Hi,

There are printk's in the staging driver vme_user(all in 1 file) which triggers
checkpatch warnings all over. To replace printk() with appropriate logging 
mechanisms(a mix of dev_err/warn & pr_err/warn), if I go by a patch for each 
function that calls printk, the patchset will be too big(~33 patches). 

Or, if I split up patches this way: printk() to pr_*() & 
printk() to dev_*(), there would be fewer patches(atleast 4) but perhaps
it will be harder to review? (There are ~78 call sites)

What would be a good way to structure the patchset?

Plus there are some other changes, like  using __func__ instead of func
name in printk error messages, that can be done. Is it okay to make this
change in the error string while replacing the printk() or does it need to be
in a separate patch( after the printk's are replaced)?

Thanks,
Soumya