From: Dan Carpenter <dan.carpenter@oracle.com>
To: David Fries <David@Fries.net>
Cc: Evgeniy Polyakov <zbr@ioremap.net>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] w1: small type cleanup in sysfs
Date: Wed, 12 Feb 2014 00:12:28 +0300 [thread overview]
Message-ID: <20140211211228.GY26722@mwanda> (raw)
In-Reply-To: <20140211164513.GF5530@spacedout.fries.net>
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
prev parent reply other threads:[~2014-02-11 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 16:08 [patch] w1: small type cleanup in sysfs Dan Carpenter
2014-02-11 16:45 ` David Fries
2014-02-11 21:07 ` [patch v2] " Dan Carpenter
2014-02-14 15:42 ` Evgeniy Polyakov
2014-02-19 7:19 ` [PATCH] w1: bundle reply if the request was bundled David Fries
2014-02-20 21:07 ` Evgeniy Polyakov
2014-02-11 21:12 ` Dan Carpenter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140211211228.GY26722@mwanda \
--to=dan.carpenter@oracle.com \
--cc=David@Fries.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zbr@ioremap.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox