All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch 1/2] fix USB initialisation procedure
Date: Thu, 9 Oct 2008 21:52:57 +0200	[thread overview]
Message-ID: <20081009195257.GA7333@lisa> (raw)
In-Reply-To: <20081009184521.5C191832E428@gemini.denx.de>

On Thu, Oct 09, 2008 at 08:45:21PM +0200, Wolfgang Denk wrote:
> In message <200810091659.55186.sr@denx.de> you wrote:
> >
> > > > >
> > > > > > -	else
> > > > > > +	else {
> > > > > > +		/* Let's wait a while for the timeout to elaps.
> > > > > > +		 * it has no real use, but it keeps the interface happy. */
> > > > > > +		wait_ms(timeout);
> > > > > >  		return -1;
> > > > > > +	}
> > > >
> > > > Good catch.
> > >
> > > Quite honest, I think this is *way* to pedantic. I'd really prefer to
> > > let people who are contributing significantly do their work instead of
> > > bugging them with such rare coding style violations.
> > 
> > ACK from me here. "Minor" coding style violations like these braces issue or 
> > too long lines should not delay patches.
> 
> NAK, and NAK again from me. Note that it's not only a single small
> violation, there is a whole list of it evenin this short code snippet:
> - incorrect brace style
> - unnecessary indentation
> - incorrect multi-line comment style
> 
> It is much easier to fix such code when it's being added, than to fix
> it later (which may or may not happen). See all the examples that got
> commited that way - and that haven't been fixed since.

True, you're technically right, of course, and I don't question
enforcing coding style in general. I just think that being too
critical has the potential of putting people off, and IMHO this list
can be very critical. Sometimes it's better to get a patch with a
couple of coding style violations than keeping the bug it would have
fixed.

Best regards
Markus

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de")

  reply	other threads:[~2008-10-09 19:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08  8:54 [U-Boot] [patch 0/2] Some more USB-OHCI bugfixes Remy Bohmer
2008-10-08  8:54 ` [U-Boot] [patch 1/2] fix USB initialisation procedure Remy Bohmer
2008-10-09 12:10   ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-09 13:19     ` Wolfgang Denk
2008-10-09 14:43       ` Markus Klotzbücher
2008-10-09 14:59         ` Stefan Roese
2008-10-09 15:09           ` Markus Klotzbücher
2008-10-09 15:22           ` Jerry Van Baren
2008-10-09 18:45           ` Wolfgang Denk
2008-10-09 19:52             ` Markus Klotzbücher [this message]
2008-10-10  7:30             ` Remy Bohmer
2008-10-09 18:42         ` Wolfgang Denk
2008-10-08  8:54 ` [U-Boot] [patch 2/2] The PIPE_INTERRUPT flag is used wrong Remy Bohmer
2008-10-08 10:12 ` [U-Boot] [patch 0/2] Some more USB-OHCI bugfixes Markus Klotzbücher
2008-10-08 10:41 ` Stelian Pop
2008-10-09  8:33 ` Stelian Pop
2008-10-09  9:51   ` Remy Bohmer
2008-10-09 15:01     ` Stelian Pop
2008-10-10  7:21       ` Remy Bohmer
2008-10-10  8:25         ` Stelian Pop
2008-10-10  8:33           ` Remy Bohmer

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=20081009195257.GA7333@lisa \
    --to=mk@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.