From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Martin Kepplinger <martink@posteo.de>
Cc: khoroshilov@ispras.ru, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: (gtco) use sign_extend32() for sign extension
Date: Fri, 23 Jan 2015 16:47:24 -0800 [thread overview]
Message-ID: <20150124004724.GA16356@dtor-ws> (raw)
In-Reply-To: <1422016176-6299-1-git-send-email-martink@posteo.de>
On Fri, Jan 23, 2015 at 01:29:36PM +0100, Martin Kepplinger wrote:
> Signed-off-by: Martin Kepplinger <martink@posteo.de>
> ---
> Despite it's name, sign_extend32() is safe to use for 8 and 16 bit types too.
Applied, thank you, but I am sure it can be cleaned up even more.
>
>
> drivers/input/tablet/gtco.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/input/tablet/gtco.c b/drivers/input/tablet/gtco.c
> index 8580456..272a838 100644
> --- a/drivers/input/tablet/gtco.c
> +++ b/drivers/input/tablet/gtco.c
> @@ -59,7 +59,7 @@ Scott Hill shill@gtcocalcomp.com
> #include <asm/uaccess.h>
> #include <asm/unaligned.h>
> #include <asm/byteorder.h>
> -
> +#include <linux/bitops.h>
>
> #include <linux/usb/input.h>
>
> @@ -666,13 +666,8 @@ static void gtco_urb_callback(struct urb *urbinfo)
> case 4:
> /* Tilt */
>
> - /* Sign extend these 7 bit numbers. */
> - if (device->buffer[6] & 0x40)
> - device->buffer[6] |= 0x80;
> -
> - if (device->buffer[7] & 0x40)
> - device->buffer[7] |= 0x80;
> -
> + device->buffer[6] = sign_extend32(device->buffer[6], 6);
> + device->buffer[7] = sign_extend32(device->buffer[7], 6);
>
> valsigned = (device->buffer[6]);
> input_report_abs(inputdev, ABS_TILT_X, (s32)valsigned);
> --
> 2.1.4
>
--
Dmitry
prev parent reply other threads:[~2015-01-24 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 12:29 [PATCH] input: (gtco) use sign_extend32() for sign extension Martin Kepplinger
2015-01-24 0:47 ` Dmitry Torokhov [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=20150124004724.GA16356@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=khoroshilov@ispras.ru \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
/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.