From: Jiri Slaby <jirislaby@gmail.com>
To: Jianjun Kong <kongjianjun@gmail.com>
Cc: torvalds@linux-foundation.org, xiyou.wangcong@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Standard indentation of arguments
Date: Wed, 21 May 2008 09:19:52 +0200 [thread overview]
Message-ID: <4833CD18.9030402@gmail.com> (raw)
In-Reply-To: <12113495282137-git-send-email-kongjianjun@gmail.com>
On 05/21/2008 07:58 AM, Jianjun Kong wrote:
> Standard indentation of arguments.
> I use right blank space to displace the last table, in order to make the arguments alining. For example:
>
> old:
> extern void test_fun(struct list_head *new,
> struct list_head *prev,
> struct list_head *next);
> new:
> extern void test_fun(struct list_head *new,
> struct list_head *prev,
> struct list_head *next);
I think, there is no "standard" on this. I personally do prefer indentation by tabs.
next prev parent reply other threads:[~2008-05-21 7:20 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 5:58 [PATCH] Standard indentation of arguments Jianjun Kong
2008-05-21 7:19 ` Jiri Slaby [this message]
2008-05-21 11:35 ` David Newall
2008-05-21 8:34 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Al Viro
2008-05-21 8:50 ` Andrew Morton
2008-05-21 9:19 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 9:41 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Al Viro
2008-05-21 17:44 ` Andrew Morton
2008-05-21 19:45 ` Theodore Tso
2008-05-21 20:38 ` Rene Herman
2008-05-21 20:50 ` Andrew Morton
2008-05-21 21:08 ` Rene Herman
2008-05-21 21:12 ` Andrew Morton
2008-05-21 21:32 ` Rene Herman
2008-05-22 19:40 ` Jaya Kumar
2008-05-21 10:32 ` Christoph Hellwig
2008-05-21 12:09 ` Theodore Tso
2008-05-21 17:46 ` Andrew Morton
2008-05-21 18:57 ` Cyrill Gorcunov
2008-05-21 19:31 ` Andrew Morton
2008-05-21 20:10 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 21:25 ` Willy Tarreau
2008-05-21 21:44 ` Stefan Richter
2008-05-21 21:56 ` Willy Tarreau
2008-05-21 21:08 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Valdis.Kletnieks
2008-05-21 23:01 ` Adrian Bunk
2008-05-21 23:17 ` Rene Herman
2008-05-21 23:55 ` Adrian Bunk
2008-05-22 0:10 ` Rene Herman
2008-05-22 14:31 ` Adrian Bunk
2008-05-21 23:35 ` Al Viro
2008-05-22 0:38 ` Adrian Bunk
2008-05-22 1:05 ` Alan Cox
2008-05-22 16:08 ` Stefan Richter
2008-05-21 19:33 ` Randy Dunlap
2008-05-21 19:45 ` Cyrill Gorcunov
2008-05-21 19:54 ` Andrew Morton
2008-05-21 20:06 ` Jesper Juhl
2008-05-21 20:27 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments), " Jonathan Corbet
2008-05-21 20:37 ` Jesper Juhl
2008-05-21 23:46 ` Jesper Juhl
2008-05-22 0:12 ` Adrian Bunk
2008-05-22 0:32 ` Jesper Juhl
2008-05-22 1:03 ` Alan Cox
2008-05-22 14:56 ` Pavel Machek
2008-05-22 15:29 ` Arjan van de Ven
2008-05-22 0:14 ` Al Viro
2008-05-22 0:34 ` Jesper Juhl
2008-05-22 1:07 ` Johannes Weiner
2008-05-22 4:51 ` Cyrill Gorcunov
2008-05-22 5:34 ` david
2008-05-31 16:23 ` Nick Andrew
2008-05-21 19:42 ` Johannes Weiner
2008-05-21 19:47 ` Cyrill Gorcunov
2008-05-21 19:49 ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 22:03 ` Al Viro
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=4833CD18.9030402@gmail.com \
--to=jirislaby@gmail.com \
--cc=kongjianjun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
/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.