From: Jesper Juhl <juhl-lkml@dif.dk>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Johan Myreen <jem@iki.fi>, Vojtech Pavlik <vojtech@suse.cz>,
Andrew Morton <akm@osdl.org>
Subject: [PATCH] remove pointless <0 comparisons for unsigned vars, and avoid a few signed vs unsigned comparisons in drivers/char/keyboard.c
Date: Mon, 22 Nov 2004 00:21:55 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.61.0411220008030.3423@dragon.hygekrogen.localhost> (raw)
Hi,
Sorry about the possibly irrelevant CC list, but I couldn't find a
maintainer for drivers/char/keyboard.c listed anywhere, so I ended up
sending to lkml and CC'ing a few people who has worked on the file, and
akpm as a fallback person due to his 2.6 maintainer role.
Here's a patch that removes a few pointless comparisons; "scancode" is
unsigned so it can never be <0 which makes the test pointless.
Also, there are a few instances where signed and unsigned variables are
comared, and as far as I can tell they really should just all be unsigned.
Comments welcome (I must confess that I've only compile tested this so
far).
Signed-off-by: Jesper Juhl <juhl-lkml@dif.dk>
diff -up linux-2.6.10-rc2-bk6-orig/drivers/char/keyboard.c linux-2.6.10-rc2-bk6/drivers/char/keyboard.c
--- linux-2.6.10-rc2-bk6-orig/drivers/char/keyboard.c 2004-10-18 23:55:36.000000000 +0200
+++ linux-2.6.10-rc2-bk6/drivers/char/keyboard.c 2004-11-22 00:05:45.000000000 +0100
@@ -174,7 +174,7 @@ int getkeycode(unsigned int scancode)
if (!dev)
return -ENODEV;
- if (scancode < 0 || scancode >= dev->keycodemax)
+ if (scancode >= dev->keycodemax)
return -EINVAL;
return INPUT_KEYCODE(dev, scancode);
@@ -184,7 +184,7 @@ int setkeycode(unsigned int scancode, un
{
struct list_head * node;
struct input_dev *dev = NULL;
- int i, oldkey;
+ unsigned int i, oldkey;
list_for_each(node,&kbd_handler.h_list) {
struct input_handle *handle = to_handle_h(node);
@@ -197,7 +197,7 @@ int setkeycode(unsigned int scancode, un
if (!dev)
return -ENODEV;
- if (scancode < 0 || scancode >= dev->keycodemax)
+ if (scancode >= dev->keycodemax)
return -EINVAL;
oldkey = SET_INPUT_KEYCODE(dev, scancode, keycode);
@@ -354,7 +354,7 @@ void to_utf8(struct vc_data *vc, ushort
*/
void compute_shiftstate(void)
{
- int i, j, k, sym, val;
+ unsigned int i, j, k, sym, val;
shift_state = 0;
memset(shift_down, 0, sizeof(shift_down));
@@ -395,7 +395,7 @@ void compute_shiftstate(void)
unsigned char handle_diacr(struct vc_data *vc, unsigned char ch)
{
int d = diacr;
- int i;
+ unsigned int i;
diacr = 0;
next reply other threads:[~2004-11-21 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 23:21 Jesper Juhl [this message]
2004-11-21 23:44 ` Jesper Juhl
2005-02-06 19:47 ` Vojtech Pavlik
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=Pine.LNX.4.61.0411220008030.3423@dragon.hygekrogen.localhost \
--to=juhl-lkml@dif.dk \
--cc=akm@osdl.org \
--cc=jem@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®