From: Jonathan Cameron <jic23@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bill Pemberton <wfp5p@virginia.edu>,
Joe Perches <joe@perches.com>,
Jonathan Cameron <jic23@kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Sonic Zhang <sonic.zhang@analog.com>
Subject: Re: [PATCH] staging/adt7316 Fix some 'interesting' string operations
Date: Tue, 09 Apr 2013 18:11:11 +0100 [thread overview]
Message-ID: <51644BAF.7080202@kernel.org> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F1EA4089E@ORSMSX104.amr.corp.intel.com>
On 04/08/2013 06:54 PM, Luck, Tony wrote:
>> I think it is a good idea to switch directly to strtobool. But anyway, if you
>> don't want to respin the patch it is fine as it is.
> I didn't know that strtobool() existed ... but now that I do I agree that it would
> be better to use it here. But ... I'm less comfortable updating the patch to use
> it. User visible behavior would change (currently just "1" is considered "true",
> but strtobool would also accept "y" and "Y"). I'd also have to think hard about
> what to do if strtobool() said the input was not a valid boolean.
>
> Thanks for the review.
>
> -Tony
I'll take the patch as is. If anyone wants to do the strtobool conversion
as a follow up that would be great as well. As a staging driver which doesn't
terribly closely correspond to any standard abi's I'd be inclined to not worry
to much about breaking userspace code that relies on the exact comparison
currently used as long as the obvious case still works.
Patch applied to togreg branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
Thanks,
Jonathan
prev parent reply other threads:[~2013-04-09 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 21:37 [PATCH] staging/adt7316 Fix some 'interesting' string operations Luck, Tony
2013-04-05 22:03 ` Greg Kroah-Hartman
2013-04-06 10:08 ` Lars-Peter Clausen
2013-04-08 17:54 ` Luck, Tony
2013-04-09 17:11 ` Jonathan Cameron [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=51644BAF.7080202@kernel.org \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=sonic.zhang@analog.com \
--cc=tony.luck@intel.com \
--cc=wfp5p@virginia.edu \
/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