<div dir="auto"><div><span style="font-family:sans-serif">So sir every Epn_ type variable should also be modified in seperate patches i.e each patch containing unique Epn_ type variables.</span><br><div class="gmail_extra"><br><div class="gmail_quote">On 3 Feb 2017 17:30, "Greg KH" <<a href="mailto:greg@kroah.com">greg@kroah.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">On Fri, Feb 03, 2017 at 11:17:55AM +0000, Amit Kumar wrote:<br>
> On Fri, Feb 03, 2017 at 01:34:11PM +0530, Deeksha varshney wrote:<br>
> > In the <a href="http://checkpatch.pl" rel="noreferrer" target="_blank">checkpatch.pl</a> for the file drivers/staging /emxx_udc/emxx_udc.c<br>
> > there are checks for Camel case naming . How should I send patches for<br>
> > them? I mean there are Epn_ type variables should I correct them all in one<br>
> > patch then there is iWriteLength variables ,correct them in another patch<br>
> > then there are pointer variables.<br>
> Yes, you can send all modifications in one patch.<br>
<br>
</div>If you do that, I will reject it, for the obvious reasons :)<br>
<br>
(hint iWriteLength probably comes from a hardware spec, be careful about<br>
that...)<br>
<br>
thanks,<br>
<br>
greg k-h<br>
</blockquote></div><br></div></div></div>