netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: gustavo@padovan.org, johan.hedberg@gmail.com,
	linville@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2012-03-01
Date: Thu, 01 Mar 2012 20:13:22 -0800	[thread overview]
Message-ID: <1330661602.1939.13.camel@joe2Laptop> (raw)
In-Reply-To: <20120301.222604.1508242694024394849.davem@davemloft.net>

On Thu, 2012-03-01 at 22:26 -0500, David Miller wrote:
> You know what really pisses me off?  This is the one issue I made a huge
> stink about last week, arguments to function calls and prototypes lining
> up properl.  And it's in ever 2nd or 3rd commit in this pull request.
[]
> Come back when you've audited this whole thing properly and honestly.

I submitted a patch to checkpatch for a --strict rule for
this argument alignment.  https://lkml.org/lkml/2012/2/29/644

Are there any other tests you think should be added with
--strict?

Some I think possible are:

o no space after cast
	struct foo *bar = (struct foo *) baz;
sb:
	struct foo *bar = (struct foo *)baz;

o don't start comments with /*$
  (perhaps only if a blank line proceeds the comment)
	/*
	 * multiline comment
	 * ...
	 */
sb:
	/* multiline comment
	 * ...
	 */

o coalesce formats
	pr_<level>("format part 1 "
		   "format part 2\n", ...)
sb:
	pr_<level>("format part 1 format part 2\n",
		   ...);

o symmetric brace standardization
	if (foo) {
		bar;
		baz;
	} else
		bar;
sb:
	if (foo) {
		bar;
		baz;
	} else {
		bar;
	}

Any others?

  reply	other threads:[~2012-03-02  4:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  2:55 pull request: bluetooth-next 2012-03-01 Gustavo Padovan
2012-03-02  3:16 ` David Miller
2012-03-02  3:23   ` David Miller
2012-03-02  3:26     ` David Miller
2012-03-02  4:13       ` Joe Perches [this message]
2012-03-02  5:35         ` [PATCH] checkpatch: Add --strict tests for braces, comments and casts Joe Perches
2012-03-02  5:54           ` [PATCH] checkpatch: Add --strict test for strings split across multiple lines Joe Perches
2012-03-02 16:37       ` pull request: bluetooth-next 2012-03-01 Gustavo Padovan
2012-03-02 21:15         ` David Miller
2012-03-03 16:46           ` Gustavo Padovan
2012-03-03 19:46             ` David Miller
2012-03-03 19:47             ` David Miller
2012-03-03 20:04               ` Joe Perches
2012-03-03 20:06                 ` David Miller

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=1330661602.1939.13.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).