netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: peter.p.waskiewicz.jr@intel.com
Cc: monis@voltaire.com, fubar@us.ibm.com, netdev@vger.kernel.org,
	olgas@voltaire.com, ogerlitz@voltaire.com
Subject: Re: [PATCH] net/bonding: Send more than one gratuitous ARP when slave takes over
Date: Mon, 14 Apr 2008 14:40:32 -0700 (PDT)	[thread overview]
Message-ID: <20080414.144032.39791824.davem@davemloft.net> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC32904E2B512@orsmsx414.amr.corp.intel.com>

From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Date: Mon, 14 Apr 2008 10:50:17 -0700

> Patch looks good to me, however I have a small nitpick below:
> 
> > +static ssize_t bonding_store_n_grat_arp(struct device *d,
> > +				    struct device_attribute *attr,
> > +				    const char *buf, size_t count)
> > +{
> > +	int new_value, ret = count;
> 
> Avoid declaring multiple variables on the same line when possible.
> Write it like this:
> 
> 	int new_value;
> 	int ret = count;
> 
> Here's a blurb from the Documentation/CodingStyle document (not gospel,
> but pretty darn close):
> 
> It's also important to comment data, whether they are basic types or
> derived
> types.  To this end, use just one data declaration per line (no commas
> for
> multiple data declarations).  This leaves you room for a small comment
> on each
> item, explaining its use.

You're telling this person to use more lines, but not telling them to
add comments, yet that is the reasoning behind the very CodingStyle
recommendation you are quoting.

I think you're recommendation is gratuitous and in my opinion wrong.
Splitting up the line adds no value, and makes the function take up
more lines on the terminal screen.

      reply	other threads:[~2008-04-14 21:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 15:07 [PATCH] net/bonding: Send more than one gratuitous ARP when slave takes over Moni Shoua
2008-04-10 19:51 ` Waskiewicz Jr, Peter P
2008-04-10 20:57   ` Jay Vosburgh
2008-04-13 14:13     ` Moni Shoua
2008-04-14 15:25 ` Moni Shoua
2008-04-14 17:50   ` Waskiewicz Jr, Peter P
2008-04-14 21:40     ` David Miller [this message]

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=20080414.144032.39791824.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=monis@voltaire.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@voltaire.com \
    --cc=olgas@voltaire.com \
    --cc=peter.p.waskiewicz.jr@intel.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 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).