Return-path: Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:31868 "EHLO mail2-relais-roc.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751017AbdBWHJH (ORCPT ); Thu, 23 Feb 2017 02:09:07 -0500 Date: Thu, 23 Feb 2017 08:08:14 +0100 (CET) From: Julia Lawall To: Tahia Khan cc: arend.vanspriel@broadcom.com, outreachy-kernel@googlegroups.com, aditya.shankar@microchip.com, ganesh.krishna@microchip.com, gregkh@linuxfoundation.org, linux-wireless@vger.kernel.org, devel@driverdev.osusl.org, linux-kernel@vger.kernel.org Subject: Re: [Outreachy kernel] Re: [PATCH v2] staging: wilc1000: renames struct tstrRSSI and its members u8Index, u8Full In-Reply-To: <20170223035400.GA9378@coolbox> Message-ID: (sfid-20170223_080950_034301_6141DC95) References: <20170222171403.GA20626@coolbox> <838d3e67-646d-b2d3-ef7d-5812675db6db@broadcom.com> <20170223035400.GA9378@coolbox> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: > Thanks for the feedback Arend, I really appreciate it. I've decided to go with > these changes in my follow-up patch request: > > - rename tstrRSSI to 'rssi_history_buffer' as Aren suggested since it makes the > purpose of the struct clear > - remove Hungarian notation from all tstrRSSI members' names > - change type of u8Full to bool since it's only ever 1 or 0 > - change name of as8RSSI to 'samples' since this buffer is only ever used to > compute an average, and the "rssi" prefix is implied by the struct's name > - rename str_rssi to rssi_history in the network_info struct for clarity > > Since my reasoning for these changes deviates from just "renaming to > avoid camel casing" (as in the original checkpatch.pl warning), would it still > make sense to submit all this in a single patch? I know my commit message > needs to change but I wonder if this is too much detail. I would strongly suggest not to do it all in a single patch. Even if these changes are not very complicated conceptually, there is always a chance of doing things wrong. Taking the problems one by one will improve the chance that the result is correct. Also, the results will be easier for you and others to review if each patch only does one thing. And easier to revert if needed later if something goes wrong. julia