From: Hans Schillstrom <hans@schillstrom.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: Simon Horman <horms@verge.net.au>,
Hans Schillstrom <hans.schillstrom@ericsson.com>,
lvs-devel@vger.kernel.org, wensong@linux-vs.org,
daniel.lezcano@free.fr
Subject: Re: [v2 PATCH 3/4] IPVS: Backup, Adding Version 1 receive capability
Date: Sat, 30 Oct 2010 13:56:09 +0200 [thread overview]
Message-ID: <201010301356.09501.hans@schillstrom.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010301338210.1610@ja.ssi.bg>
On Saturday, October 30, 2010 12:59:34 Julian Anastasov wrote:
>
> Hello,
>
> On Sat, 30 Oct 2010, Simon Horman wrote:
>
> > I realise that the commenting syntax used throughout IPVS
> > is a) inconsistent and b) for the most part does not comply with
> > any variant of the style guidelines. However, for the record
> > I believe that the preferred commenting style for code in net/
> > and thus IPVS is:
> >
> > /* This is a one line comment */
> >
> > /* This is a
> > * multi-line comment
> > */
>
> Documentation/CodingStyle has rule for multi-line:
>
> /*
> * This is a
> * multi-line comment
> */
>
> >> + ip_vs_conn_fill_param(af, sc->v6.protocol,
> >> + (const union nf_inet_addr *)&sc->v6.caddr,
> >> + sc->v6.cport,
> >> + (const union nf_inet_addr *)&sc->v6.vaddr,
> >> + sc->v6.vport, p);
> >
> > I'm ok with not aligning to the opening ( in order to avoid
> > going over 80 columns here. Though I suspect others would disagree.
>
> Agreed, in such cases I prefer one tab after parent,
> especially, if there is no other code around and when not
> part of some complex 'if' expression.
>
> I'm now sure Hans will read Documentation/CodingStyle again :)
>
I will have it as my night reading ;-)
> Regards
>
> --
> Julian Anastasov <ja@ssi.bg>
next prev parent reply other threads:[~2010-10-30 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 12:16 [v2 PATCH 3/4] IPVS: Backup, Adding Version 1 receive capability Hans Schillstrom
2010-10-30 6:47 ` Simon Horman
2010-10-30 10:59 ` Julian Anastasov
2010-10-30 11:23 ` Simon Horman
2010-10-30 11:56 ` Hans Schillstrom [this message]
2010-10-30 11:49 ` Hans Schillstrom
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=201010301356.09501.hans@schillstrom.com \
--to=hans@schillstrom.com \
--cc=daniel.lezcano@free.fr \
--cc=hans.schillstrom@ericsson.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=wensong@linux-vs.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 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.