public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Arlott <simon@fire.lp0.eu>
To: Denis Cheng <crquan@gmail.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] run scripts/Lindent on it to match Documentation/CodingStyle
Date: Sun, 15 Jul 2007 10:53:45 +0100	[thread overview]
Message-ID: <4699EEA9.6070709@simon.arlott.org.uk> (raw)
In-Reply-To: <1184489571313-git-send-email-crquan@gmail.com>

On 15/07/07 09:52, Denis Cheng wrote:
> Signed-off-by: Denis Cheng <crquan@gmail.com>
> ---
>  drivers/net/wireless/wavelan.c |  806 ++++++++++++++++++----------------------
>  1 files changed, 369 insertions(+), 437 deletions(-)

Do people ever check what Lindent does?

> -	} else if (base_addr > 0x100) { /* Check a single specified location. */
> +	} else if (base_addr > 0x100) {	/* Check a single specified location. */

What is Lit doing here?! It's changed "{<space>/*" to "{<tab>/*"...


> -	} else { /* Scan all possible addresses of the WaveLAN hardware. */
> +	} else {		/* Scan all possible addresses of the WaveLAN hardware. */

And again... with two tabs for maximum unreadability. That line is now
90 characters long instead of 75.


> -				       "%s: <-wavelan_probe()\n",
> -				       dev->name);
> +				       "%s: <-wavelan_probe()\n", dev->name);

There are spaces in that line after the tabs...


> -out1:
> +      out1:

NAK: A perfectly valid non-indented label is now indented by 6 spaces.


> -out:
> +      out:

And again.


> -		       dev->name, (unsigned int) dev);
> +		       dev->name, (unsigned int)dev);

Those spaces after the tabs have been ignored...

-- 
Simon Arlott

  parent reply	other threads:[~2007-07-15  9:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15  8:52 [PATCH 1/2] run scripts/Lindent on it to match Documentation/CodingStyle Denis Cheng
2007-07-15  8:52 ` [PATCH 2/2] add static delaration and init_module fixes Denis Cheng
2007-07-15  9:20 ` [PATCH 1/2] run scripts/Lindent on it to match Documentation/CodingStyle Christoph Hellwig
2007-07-15  9:53 ` Simon Arlott [this message]
2007-07-20 17:07   ` Matthew Wilcox
2007-07-20 17:36     ` Simon Arlott
2007-07-20 18:00       ` Matthew Wilcox
2007-07-21  6:11         ` Simon Arlott
2007-07-21 13:47           ` rae l
2007-07-21 13:52           ` Matthew Wilcox
2007-07-21 19:17             ` diffutils: C labels misdetected as functions (Was: [PATCH 1/2] run scripts/Lindent on it to match Documentation/CodingStyle) Simon Arlott
2007-07-22 18:38               ` diffutils: C labels misdetected as functions Paul Eggert
2007-07-22 19:16                 ` Simon Arlott
2007-07-22 21:30                   ` Junio C Hamano
2007-07-21  6:12         ` [PATCH 1/2] run scripts/Lindent on it to match Documentation/CodingStyle Simon Arlott
2007-07-20 20:50     ` Oleg Verych
2007-07-20 20:54       ` Matthew Wilcox
2007-07-21  4:32         ` Fixing lables after GNU indent (Re: [PATCH 1/2] run scripts/Lindent on it to match Documentation/CodingStyle) Oleg Verych
2007-07-21 16:17     ` [PATCH 1/2] run scripts/Lindent on it to match Documentation/CodingStyle Jan Engelhardt
2007-07-20 17:33   ` Matthew Wilcox

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=4699EEA9.6070709@simon.arlott.org.uk \
    --to=simon@fire.lp0.eu \
    --cc=crquan@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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