[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1487831066.14159.17.camel@perches.com>
Date: Wed, 22 Feb 2017 22:24:26 -0800
From: Joe Perches <joe@...ches.com>
To: Arend Van Spriel <arend.vanspriel@...adcom.com>,
Tahia Khan <tahia.khan@...il.com>,
outreachy-kernel@...glegroups.com, aditya.shankar@...rochip.com,
ganesh.krishna@...rochip.com, gregkh@...uxfoundation.org,
linux-wireless@...r.kernel.org, devel@...verdev.osuosl.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] staging: wilc1000: renames struct tstrRSSI and its
members u8Index, u8Full
On Wed, 2017-02-22 at 20:50 +0100, Arend Van Spriel wrote:
> On 22-2-2017 18:14, Tahia Khan wrote:
> > Fixes multiple camel case checks on struct tstrRSSI from checkpatch.pl:
[]
> Just a generic remark that may help you with other changes you will be
> making in the linux kernel. Warnings from checkpatch.pl and other tools
> are useful, but try to look further than just fixing a warning.
> Understand what the code is doing is just as important.
I'd assert understanding what the code is doing is
_more_ important. Style consistency simply helps
improve the speed of a new reader's understanding.
Powered by blists - more mailing lists