[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <FC41C24E35F18A40888AACA1A36F3E416C617400@FMSMSX102.amr.corp.intel.com>
Date: Tue, 27 Aug 2013 20:34:04 +0000
From: "Nelson, Shannon" <shannon.nelson@...el.com>
To: "Nelson, Shannon" <shannon.nelson@...el.com>,
David Miller <davem@...emloft.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC: "e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
"gospo@...hat.com" <gospo@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>
Subject: RE: [net-next v2 1/8] i40e: main driver core
> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Friday, August 23, 2013 12:28 AM
[...]
>
> > +{
> > + int i;
> > + struct i40e_pf *pf = vsi->back;
>
> Please order local variable declarations from longest line to shortest.
I understand the aesthetics as it does make the code look a little cleaner, and we can do this with a lot of our functions. However, there are several instances where one declaration initialization depends on a previous declaration, and trying to organize by line length breaks these relationships. Do you mind if we're not perfect on following this one?
Also, perhaps I haven't watched closely enough, but I don't remember seeing this comment on other code. Is this a new recommendation that will be going into the CodingStyle document?
Thanks,
sln
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists