All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: linux-media@vger.kernel.org, mchehab@redhat.com,
	Stefan Ringel <linuxtv@stefanringel.de>
Subject: Re: [PATCH 2/2] [media] tm6000: Fix bad indentation.
Date: Tue, 06 Dec 2011 15:58:49 +0200	[thread overview]
Message-ID: <4EDE1F99.6080200@iki.fi> (raw)
In-Reply-To: <1323178776-12305-2-git-send-email-thierry.reding@avionic-design.de>

That question is related to that kind of indentation generally, not only 
that patch.

On 12/06/2011 03:39 PM, Thierry Reding wrote:
> Function parameters on subsequent lines should never be aligned with the
> function name but rather be indented.
[...]
>   			usb_set_interface(dev->udev,
> -			dev->isoc_in.bInterfaceNumber,
> -			0);
> +					dev->isoc_in.bInterfaceNumber, 0);

Which kind of indentation should be used when function params are 
slitted to multiple lines?

In that case two tabs are used (related to function indentation).
example:
	ret= function(param1,
			param2);

Other generally used is only one tab (related to function indentation).
example:
	ret= function(param1,
		param2);

And last generally used is multiple tabs + spaces until same location 
where first param is meet (related to function indentation). I see that 
bad since use of tabs, with only spaces I see it fine. And this many 
times leads situation param level are actually different whilst 
originally idea was to put those same level.
example:
	ret= function(param1,
		      param2);


regards
Antti
-- 
http://palosaari.fi/

  reply	other threads:[~2011-12-06 13:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1322509580-14460-1-git-send-email-linuxtv@stefanringel.de>
2011-11-28 19:46 ` [PATCH 2/5] tm6000: bugfix register setting linuxtv
2011-11-28 19:46 ` [PATCH 3/5] tm6000: bugfix interrupt reset linuxtv
2011-12-05  7:21   ` Thierry Reding
2011-12-05 12:04     ` Mauro Carvalho Chehab
2011-12-05 15:38       ` Thierry Reding
2011-12-05 18:21         ` Mauro Carvalho Chehab
2011-12-05 20:02           ` Stefan Ringel
2011-12-05 20:16             ` Mauro Carvalho Chehab
2011-12-06  6:51               ` Thierry Reding
2011-12-06  8:12                 ` Thierry Reding
2011-12-06 12:25                   ` Mauro Carvalho Chehab
2011-12-06 13:05                     ` [PATCH] [media] tm6000: Fix fast USB access quirk Thierry Reding
2011-12-06 12:22                 ` [PATCH 3/5] tm6000: bugfix interrupt reset Mauro Carvalho Chehab
2011-11-28 19:46 ` [PATCH 4/5] tm6000: bugfix bulk transfer linuxtv
2011-11-28 19:46 ` [PATCH 5/5] tm6000: bugfix data check linuxtv
2011-11-30 17:21   ` Mauro Carvalho Chehab
2011-12-06 13:39 ` [PATCH 1/2] [media] tm6000: Fix check for interrupt endpoint Thierry Reding
2011-12-06 13:39   ` [PATCH 2/2] [media] tm6000: Fix bad indentation Thierry Reding
2011-12-06 13:58     ` Antti Palosaari [this message]
2011-12-06 14:13       ` Thierry Reding
2011-12-06 20:58         ` Mauro Carvalho Chehab
2011-12-06 21:03           ` Antti Palosaari
2011-12-07 13:24             ` Mauro Carvalho Chehab

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=4EDE1F99.6080200@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=linuxtv@stefanringel.de \
    --cc=mchehab@redhat.com \
    --cc=thierry.reding@avionic-design.de \
    /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.