netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Christoph Hellwig <hch@infradead.org>,
	netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-2.6.22 1/3] [TCP]: Sed magic converts func(sk, tp, ...) -> func(sk, ...)
Date: Mon, 16 Apr 2007 17:32:05 +0200	[thread overview]
Message-ID: <462396F5.9030907@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0704161758020.28337@kivilampi-30.cs.helsinki.fi>

Ilpo Järvinen wrote:
> On Mon, 16 Apr 2007, Patrick McHardy wrote:
> 
>>[...]
> 
> ...in the other (original) patch description that is not copied fully here 
> I had a sort of disclaimer for these missing ones but in case they should 
> all be changed so that if the added tcp_sock is the only local variable I 
> can do that of course... It's not clear to me what is really the preferred 
> style considering all the variants... E.g., tcp_check_probe_timer (below) 
> does not have the newline before this patch either?!? :-) ...tried to look 
> from CodingStyle too but it didn't give any light to this thing...


The preferred style is a newline after variable declarations. Some
(mostly old) code doesn't consistently do that, but in cases where
you add the first local variable you should really add them.

>>> 	const struct inet_connection_sock *icsk = inet_csk(sk);
> 
> 
> ...No newline should be place here, since it's being followed by 
> another local variable defination.


Yes, this one was a mistake. In this case I would probably leave it
as it was before to avoid bloating the patch, but I guess nobody
would mind if you'd add newlines here as well, the patch is not very
large or hard to understand anyway.


  reply	other threads:[~2007-04-16 15:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16 12:48 [PATCH net-2.6.22 1/3] [TCP]: Sed magic converts func(sk, tp, ...) -> func(sk, ...) Ilpo Järvinen
2007-04-16 12:48 ` [PATCH 2/3] [TCP]: Fix unused variable warnings (tcp_sock *tp no longer needed) Ilpo Järvinen
2007-04-16 12:48   ` [PATCH 3/3] [TCP]: Added emptylines after the new tcp_sock *tp initialization Ilpo Järvinen
2007-04-16 13:48 ` [PATCH net-2.6.22 1/3] [TCP]: Sed magic converts func(sk, tp, ...) -> func(sk, ...) Christoph Hellwig
2007-04-16 14:08   ` Ilpo Järvinen
2007-04-16 14:41     ` Patrick McHardy
2007-04-16 15:15       ` Ilpo Järvinen
2007-04-16 15:32         ` Patrick McHardy [this message]
2007-04-16 15:52           ` Ilpo Järvinen
2007-04-16 16:19           ` Ilpo Järvinen
2007-04-17  0:16             ` David Miller
2007-04-17  7:45               ` Ilpo Järvinen
2007-04-17 11:54               ` Ilpo Järvinen
2007-04-21  5:18             ` 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=462396F5.9030907@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=ilpo.jarvinen@helsinki.fi \
    --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).