[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <581C6A7D.8030704@marvell.com>
Date: Fri, 4 Nov 2016 12:01:17 +0100
From: Lino Sanfilippo <lsanfil@...vell.com>
To: Joe Perches <joe@...ches.com>, David Miller <davem@...emloft.net>,
<madalin.bucur@....com>, Andrew Morton <akpm@...ux-foundation.org>,
"Jonathan Corbet" <corbet@....net>
CC: <netdev@...r.kernel.org>, <linuxppc-dev@...ts.ozlabs.org>,
<linux-kernel@...r.kernel.org>, <oss@...error.net>,
<ppc@...dchasers.com>, <pebolle@...cali.nl>,
<joakim.tjernlund@...nsmode.se>
Subject: Re: Coding Style: Reverse XMAS tree declarations ? (was Re: [PATCH
net-next v6 02/10] dpaa_eth: add support for DPAA Ethernet)
Hi,
On 04.11.2016 07:53, Joe Perches wrote:
>
> CHECK:REVERSE_XMAS_TREE: Prefer ordering declarations longest to shortest
> #446: FILE: drivers/net/ethernet/ethoc.c:446:
> + int size = bd.stat >> 16;
> + struct sk_buff *skb;
>
should not this case be valid? Optically the longer line is already before the shorter.
I think that the whole point in using this reverse xmas tree ordering is to have
the code optically tidied up and not to enforce ordering between variable name lengths.
Regards,
Lino
Powered by blists - more mailing lists