mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Hansjoerg Lipp <hjlipp@web.de>, Tilman Schmidt <tilman@imap.cc>,
	gigaset307x-common@lists.sourceforge.net,
	Jiri Slaby <jirislaby@gmail.com>
Subject: Re: "whitespace coding style cleanup" broke coding style
Date: Mon, 27 Feb 2012 08:52:29 -0800	[thread overview]
Message-ID: <1330361549.9942.7.camel@joe2Laptop> (raw)
In-Reply-To: <4F4B45F6.4090706@suse.cz>

On Mon, 2012-02-27 at 09:59 +0100, Jiri Slaby wrote:
> commit 475be4d85a274d0961593db41cf85689db1d583c
> Author: Joe Perches <joe@perches.com>
> Date:   Sun Feb 19 19:52:38 2012 -0800
> 
>      isdn: whitespace coding style cleanup
> 
>      isdn source code uses a not-current coding style.
> ...
>      Done with emacs and some scripts and some typing.
> ...
> --- a/drivers/isdn/gigaset/interface.c
> +++ b/drivers/isdn/gigaset/interface.c
> ...
> @@ -680,9 +680,9 @@ void gigaset_if_initdriver(struct gigaset_driver 
> *drv, const
>   char *procname,
>                  goto enomem;
> 
>          tty->magic =            TTY_DRIVER_MAGIC,
> -       tty->type =             TTY_DRIVER_TYPE_SERIAL,
> -       tty->subtype =          SERIAL_TYPE_NORMAL,
> -       tty->flags =            TTY_DRIVER_REAL_RAW | 
> TTY_DRIVER_DYNAMIC_DEV;
> +               tty->type =             TTY_DRIVER_TYPE_SERIAL,
> +               tty->subtype =          SERIAL_TYPE_NORMAL,
> +               tty->flags =            TTY_DRIVER_REAL_RAW | 
> TTY_DRIVER_DYNAMIC_DEV;
> 
> Hmm, please, fix your scripts or emacs!

Hi Jiri.

I'm not fixing emacs.

Notice that the code improperly uses commas and
not semicolons for line terminations like the
lines immediately above and below it.

btw:  Your copy/paste lost the tab indents.

The emacs pass was not perfect, nor was it
intended to be perfect.  There are _way_
too many coding style defects in isdn for
that.

It was a first pass and an overall improvement.

"It's quite a bit more like what passes
for the current kernel coding style though."

> Through which tree did this get in?

net-next

> thanks,

I'm working on improving the logging style
in isdn and will submit more patches soonish.

cheers, Joe


  parent reply	other threads:[~2012-02-27 16:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  8:59 Jiri Slaby
2012-02-27 11:19 ` Tilman Schmidt
2012-02-27 11:34   ` Jiri Slaby
2012-02-27 16:52 ` Joe Perches [this message]
2012-02-27 17:12   ` Jiri Slaby
2012-02-27 17:27     ` Joe Perches
2012-02-27 17:39       ` [PATCH net-next] gigaset: Use semicolons to terminate statements Joe Perches
2012-02-27 19:12         ` David Miller
2012-02-27 18:58       ` "whitespace coding style cleanup" broke coding style Jiri Slaby
2012-02-28 17:58   ` Tilman Schmidt
2012-02-28 22:05     ` Joe Perches
2012-02-28 23:08       ` Tilman Schmidt
2012-02-28 23:28         ` Joe Perches
2012-02-28 23:42           ` David Miller
2012-02-29  0:41             ` Alan Cox
2012-02-29  8:27           ` Armin Schindler
2012-02-29 19:32             ` Joe Perches
2012-02-29 11:05           ` Tilman Schmidt

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=1330361549.9942.7.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=gigaset307x-common@lists.sourceforge.net \
    --cc=hjlipp@web.de \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tilman@imap.cc \
    /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

Powered by JetHome