Re: Fix style in s3c-hsotg.c

From: Pavel Machek
Date: Wed Sep 18 2013 - 05:20:34 EST


On Tue 2013-09-17 20:45:39, Felipe Balbi wrote:
> On Wed, Sep 18, 2013 at 12:04:27AM +0200, Pavel Machek wrote:
> > On Tue 2013-09-17 10:42:30, Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Mon, Sep 02, 2013 at 03:58:32PM +0200, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > checkpatch.pl has some valid complaints about style in s3c-hsotg.c :
> > > > macro with if should be really enclosed in do {} while, and puts is
> > > > going to be slightly faster.
> > > >
> > > > Here's suggested patch. I don't have the hardware, so it is completely
> > > > untested.
> > > >
> > > > Signed-off-by: Pavel Machek, <pavel@xxxxxxx>
> > >
> > > this is not how you send a patch, please read
> > > Documentation/SubmittingPatches
> >
> > Have you considered possibility that this is how you nudge maintainer
> > into fix their coding style?
>
> cute...
>
> Seriously though, read that file, you're commit log has garbage in it
> which shouldn't go to git history.

Run git log on SubmittingPatches.

Then, instead of telling me what to read, run checkpatch on your
files. You can either fix them yourself, or use my patch as a
basis. Note there's missing } or something, so it probably will not
compile, see the other mail. So you actually will have to modify that
patch. Stripping "Hi!" from it should not be that hard, neither should
be stripping note that patch is untested when you actually test
it. And as you are the maintainer, it is your job.

No, I'll not polish patch for hardware I don't have and have little
interest in. wanted to help you, but according to your first reply,
you do not really want help.

Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/