From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Carpenter <dan.carpenter@oracle.com>
Date: Tue, 11 Feb 2014 21:12:28 +0000
Subject: Re: [patch] w1: small type cleanup in sysfs
Message-Id: <20140211211228.GY26722@mwanda>
List-Id: <kernel-janitors.vger.kernel.org>
References: <20140211160826.GD9406@elgon.mountain>
 <20140211164513.GF5530@spacedout.fries.net>
In-Reply-To: <20140211164513.GF5530@spacedout.fries.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: David Fries <David@Fries.net>
Cc: Evgeniy Polyakov <zbr@ioremap.net>, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org

On Tue, Feb 11, 2014 at 10:45:13AM -0600, David Fries wrote:
> Dan,
> 
> I have some other changes in work, how automated is your checkers?
> How much work is it for me to give a github repository and branch and
> find out if I introduced any problems before submitting them?
> 

This is a Smatch thing I'm working on but haven't pushed yet.
Eventually it will be a part of Fengguang Wu's automated kbuild zero
day testing process.

> 
> I didn't get how you could get a less than one after a check for less
> than one from the description or patch until I looked at the rest of
> the source code.  Looks good if the description mentions
> max_slave_count is an int.
> 
> How about wording it,
> 
> On 64 bit systems, a large value for "long tmp" is truncated when
> assigning to "int md->max_slave_count" so we still end up with a value
> less than one despite the "tmp < 1" check.
> 

Sure.  That's clearer.  I have resent it.

regards,
dan carpenter