From: JJ Ding <jj_ding@emc.com.tw>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
JJ Ding <dgdunix@gmail.com>
Subject: Re: [PATCH] Input: convert obsolete strict_strtox to kstrtox
Date: Mon, 07 Nov 2011 14:13:03 +0800 [thread overview]
Message-ID: <87d3d4fok0.fsf@emc.com.tw> (raw)
In-Reply-To: <20111107055540.GB21095@core.coreip.homeip.net>
Hi Dmitry,
Thanks for the hint. I will send a new patch.
Btw, there are still some simple_strtox uses floating around. Namely:
drivers/input/joystick/analog.c:735: analog_options[i] = simple_strtoul(js[i], &end, 0);
drivers/input/mouse/sentelic.c:415: reg = simple_strtoul(buf, &rest, 16);
drivers/input/touchscreen/gunze.c:71: input_report_abs(dev, ABS_X, simple_strtoul(gunze->data + 1, NULL, 10));
drivers/input/touchscreen/gunze.c:72: input_report_abs(dev, ABS_Y, 1024 - simple_strtoul(gunze->data + 6, NULL, 10));
But I am not quite sure if it's safe to convert along the way. Is it OK
to convert these?
Thanks,
jj
On Sun, 6 Nov 2011 21:55:40 -0800, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> Hi JJ,
>
> On Mon, Nov 07, 2011 at 11:12:50AM +0800, JJ Ding wrote:
> > From: JJ Ding <dgdunix@gmail.com>
> >
> > With commit 67d0a0754455f89ef3946946159d8ec9e45ce33a we mark strict_strtox
> > as obsolete. Convert all remaining such uses in drivers/input/.
>
> Most of these users do not want long data, they just want an int, but
> strict_strtouint was not available. Since we have kstrtouint now it
> would be nice to use it.
>
> Thanks.
>
> --
> Dmitry
next prev parent reply other threads:[~2011-11-07 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 3:12 [PATCH] Input: convert obsolete strict_strtox to kstrtox JJ Ding
2011-11-07 5:55 ` Dmitry Torokhov
2011-11-07 6:13 ` JJ Ding [this message]
2011-11-08 3:48 ` Dmitry Torokhov
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=87d3d4fok0.fsf@emc.com.tw \
--to=jj_ding@emc.com.tw \
--cc=dgdunix@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.