linux-kernel - Re: [PATCH 2/2] staging: unisys: remove unused variable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150508075413.GA7663@sudip-PC>
Date:	Fri, 8 May 2015 13:24:32 +0530
From:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	devel@...verdev.osuosl.org,
	Benjamin Romer <benjamin.romer@...sys.com>,
	linux-kernel@...r.kernel.org, sparmaintainer@...sys.com
Subject: Re: [PATCH 2/2] staging: unisys: remove unused variable

On Fri, May 08, 2015 at 10:34:49AM +0300, Dan Carpenter wrote:
> On Fri, May 08, 2015 at 09:54:44AM +0530, Sudip Mukherjee wrote:
> > On Thu, May 07, 2015 at 10:04:32PM +0200, Greg Kroah-Hartman wrote:
> > > On Thu, May 07, 2015 at 03:06:52PM +0530, Sudip Mukherjee wrote:
> > > > the previous patch of the series made this variable unused.
> > > 
> > > What do you mean?  There was only one other patch in this series, never
> > > send a patch that causes a build warning.
> > This patch is 2/2 , the 1/2 patch when applied will cause a build
> > warning about unused variable.
> > 
> > should i then send a v2 mentioning that "1/2 will cause a build warning
> > which is fixed in 2/2" ?
> > 
> 
> Gar...  No.  Fold them together into one patch...
> 
> The one thing per patch rule means that you shouldn't do half a thing
> per patch.

already sent that one combined patch.

but this rule is really confusing me now .. :(
if i can understand the devicemodel then this rule should not be tough
to understand.
so, what i understood till now:
1) any patch of the series should not break the build.
	(you told me that in my parport patch series :) )

2) any patch of the series should not introduce build warning.

3) when i am modifying some line, i can make simple changes in style.
	but if its big change in style then that should be a separate
	patch.

regards
sudip

> 
> regards,
> dan carpenter
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/