Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752439AbbHRGPF (ORCPT ); Tue, 18 Aug 2015 02:15:05 -0400 Received: from mail-pa0-f44.google.com ([209.85.220.44]:36348 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751229AbbHRGPD (ORCPT ); Tue, 18 Aug 2015 02:15:03 -0400 Date: Tue, 18 Aug 2015 11:44:54 +0530 From: Sudip Mukherjee To: =?iso-8859-1?Q?Rapha=EBl?= Beamonte Cc: Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, Greg Donald , Cristina Opriceana Subject: Re: [PATCH 02/20] staging: rtl8192u: r8192U_core: fix consistent spacing code style error Message-ID: <20150818061454.GH2941@sudip-pc> References: <20150818050222.GB2941@sudip-pc> <20150818054415.GF2941@sudip-pc> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1390 Lines: 30 On Tue, Aug 18, 2015 at 02:02:49AM -0400, Rapha?l Beamonte wrote: > 2015-08-18 1:44 GMT-04:00 Sudip Mukherjee : > > I think that will be better, since you are sending the patch for > > consistent spacing. > > Actually, going through the bunch of patches, it seems that the > whitespace neatening one is taking care of that. That one patch was > mostly about taking care of the checkpatch "consistent spacing" > warning. > Two solutions here: > (1) I can merge both patches and make a general whitespace neatening > one, taking care of that too. > (2) I can clarify the commit messages of each patches to explain the > aim of each. > Of course, in (1) too I'd take care of explaining the whole point of > the commit. What do you think would be the best approach at this > point? If both the patches are doing the same change then it will be better to combine them in one. Just remember two things while sending patches: 1) your commit message should describe the change you are doing and incase of big changes mention why you are doing it. 2) You should not do more than one type of change in a patch. regards sudip -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/