[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160216.150813.617905734698506558.davem@davemloft.net>
Date: Tue, 16 Feb 2016 15:08:13 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: David.Laight@...LAB.COM
Cc: romieu@...zoreil.com, rshearma@...cade.com, netdev@...r.kernel.org,
roopa@...ulusnetworks.com, ebiederm@...ssion.com
Subject: Re: [PATCH net-next 1/2] mpls: packet stats
From: David Laight <David.Laight@...LAB.COM>
Date: Mon, 8 Feb 2016 11:51:34 +0000
> From: Francois Romieu
>> Sent: 06 February 2016 10:59
>> > +void mpls_stats_inc_outucastpkts(struct net_device *dev,
>> > + const struct sk_buff *skb)
>> > +{
>> > + struct mpls_dev *mdev;
>> > + struct inet6_dev *in6dev;
>>
>> Nit: the scope can be reduced for both variables.
>
> And hiding the definitions of variables in the middle of
> functions just makes them harder to find.
I completely disagree. You look up from the scope you are reading back
to the top-level scope to fine variable declarations.
If the variable declarations are closer to where you are looking you
don't even need to scroll back at all.
It also happens to help the compiler run more efficiently.
Powered by blists - more mailing lists