The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: balbi@ti.com
Cc: Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org
Subject: Re: Fix style in s3c-hsotg.c
Date: Wed, 25 Sep 2013 17:39:39 +0200	[thread overview]
Message-ID: <2758936.kqHJ9YzqCC@amdc1032> (raw)
In-Reply-To: <20130918141106.GH21559@radagast>


Hi,

On Wednesday, September 18, 2013 09:11:06 AM Felipe Balbi wrote:
> Hi,
> 
> On Wed, Sep 18, 2013 at 11:20:27AM +0200, Pavel Machek wrote:
> > 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@denx.de>
> > > > > 
> > > > > 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.
> 
> you misunderstand the work of maintainers. Our work is not to fix you
> crappy patches. If we start allowing crappy patches, we'd be fixing your
> nonsense forever and linux wouldn't move.

Pavel, Felipe's remark was valid..

> > 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.
> 
> that's your call. Now how about you stop being such a baby and go fix
> your mistakes to start with ? Just because I'm the maintainer of the
> gadget framework, doesn't mean I'm the maintainer of s3c-hsotc.c file.
> Maintainer != author too, btw.
> 
> Anyway, I got much better stuff to do than babysitting grown ups.

..even if it could have been communicated in a gentler way.

Anyway s3c-hsotg.c is a driver for our hardware so I'm going to pick this
patch up, polish it and then re-submit it later. Thanks.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics


  reply	other threads:[~2013-09-25 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 13:58 Fix style in s3c-hsotg.c Pavel Machek
2013-09-02 17:25 ` Sergei Shtylyov
2013-09-17 15:42 ` Felipe Balbi
2013-09-17 22:04   ` Pavel Machek
2013-09-18  1:45     ` Felipe Balbi
2013-09-18  9:20       ` Pavel Machek
2013-09-18 14:11         ` Felipe Balbi
2013-09-25 15:39           ` Bartlomiej Zolnierkiewicz [this message]
2013-09-25 20:35             ` Felipe Balbi
2013-09-25 23:53               ` Pavel Machek
2013-09-25 21:15             ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2758936.kqHJ9YzqCC@amdc1032 \
    --to=b.zolnierkie@samsung.com \
    --cc=balbi@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox