On Tue, Jun 5, 2018 at 7:57 PM Vinod <vkoul@xxxxxxxxxx> wrote: > > On 02-06-18, 01:15, Stanimir Varbanov wrote: > > Hi Vikash, > > > > On 1.06.2018 23:26, Vikash Garodia wrote: > > > Add a new routine to reset the ARM9 and brings it > > > out of reset. This is in preparation to add PIL > > > functionality in venus driver. > > > > please squash this patch with 4/5. I don't see a reason to add a function > > which is not used. Shouldn't this produce gcc warnings? > > Yes this would but in a multi patch series that is okay as subsequent > patches would use that and end result in no warning. Except during bisect. > > Splitting logically is good and typical practice in kernel to add the > routine followed by usages.. Is it in this case though? If this code was shared across multiple users I could understand but this function is only used locally (and only in one place IIUC). Also the patch is not so big that the code would become confusing if this was squashed into 4/5. I don't see any reason to keep this separate. -- To unsubscribe from this list: send the line "unsubscribe linux-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
