linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: fthain@telegraphics.com.au
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] pmac-zilog: add platform driver
Date: Sat, 9 Jan 2010 14:14:28 +1100 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1001091331560.17571@nippy.intranet> (raw)
In-Reply-To: <10f740e81001081117s54c5dd9by4cc0490e0c57d67b@mail.gmail.com>



On Fri, 8 Jan 2010, Geert Uytterhoeven wrote:

> On Sat, Jan 2, 2010 at 17:39, Finn Thain <fthain@telegraphics.com.au> 
> wrote:
> > On Sat, 2 Jan 2010, Geert Uytterhoeven wrote:
> >> On Tue, Nov 17, 2009 at 10:04, Finn Thain 
> >> <fthain@telegraphics.com.au> wrote: BTW, there are a few other minor 
> >> checkpatch issues with some of the other patches in the series, too.
> >
> > I ran checkpatch on all those patches before I submitted them. I 
> > ignored some of the complaints about whitespace where I felt that 
> > checkpatch got it wrong (space character following tab character, 
> > IIRC).
> >
> > checkpatch found lots of mistakes that I did fix, but it can't 
> > determine the most human readable style in all cases, especially where 
> > consistency with the surrounding code is actually more conducive to 
> > readability than strict but sporadic conformance to simple rules would 
> > be.
> 
> It seems your editor adds spaces to lines that are continuations of the 
> previous statement.

I put in spaces after tabs for hard wrapped lines so that code always 
renders properly regardless of the tab settings that might to be applied 
by any editor, browser, word processor, mailer, tty discipline, publisher, 
etc. that might stand between the human reader and the code.

Documentation/CodingStyle says that those indented lines should be 
"substantially to the right", but checkpatch doesn't conform and nor does 
most kernel code. Some code does follow my preference, which is more 
readable, and also happens to follow the example of the lisp code found in 
the same style guide.

But if you prefer no spaces after tabs, I can do that instead. I'm not 
fussed.

> I fixes them up and applied all your patches to linux-m68k.git.

Thanks. I'll resend the patch to address your comments earlier in the 
thread.

Finn

> The other warnings were indeed false positives or complains about
> keeping consistency
> with the surrounding code.
> 
> Gr{oetje,eeting}s,
> 
> 						Geert

  reply	other threads:[~2010-01-09  3:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17  9:04 [PATCH 1/2] pmac-zilog: add platform driver Finn Thain
2009-12-23 20:16 ` Geert Uytterhoeven
2010-01-02 12:43 ` Geert Uytterhoeven
2010-01-02 16:39   ` Finn Thain
2010-01-07 21:05     ` Geert Uytterhoeven
2010-01-08 19:17     ` Geert Uytterhoeven
2010-01-09  3:14       ` fthain [this message]
2010-01-07 21:12 ` Geert Uytterhoeven
2010-01-10 12:48   ` [PATCH 1/2] pmac-zilog: add platform driver, version 2 fthain
2010-01-10 16:29     ` [PATCH 1/2] pmac-zilog: add platform driver, version 3 Finn Thain
2010-01-14 13:38       ` Geert Uytterhoeven
2010-01-31  7:25         ` ping, was " fthain
2010-01-31  9:03           ` Geert Uytterhoeven

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=alpine.LNX.2.00.1001091331560.17571@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).