linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jocelyn Mayer <jma@netgem.com>
To: Linux PPC <linuxppc-dev@lists.linuxppc.org>,
	linux-usb-devel@lists.sourceforge.net, vojtech@suse.cz
Subject: [PATCH] Fix compilation problem with 2.6.0-test2 on PPC
Date: 05 Aug 2003 22:11:36 +0200	[thread overview]
Message-ID: <1060114295.1914.6988.camel@jma1.dev.netgem.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 309 bytes --]

Hi,

There is a compilation issue in driver/input/evdev.c
due to the fact a "complex" expression is used as an argument
for an inline assembly construction (get_user)
The fix I done is to use a temporary variable to get the argument
and then use this variable for get_user.

--
Jocelyn Mayer <jma@netgem.com>

[-- Attachment #2: evdev.c.diff --]
[-- Type: text/plain, Size: 733 bytes --]

--- evdev.c.orig	Mon Jun 16 06:39:02 2003
+++ evdev.c	Thu Jul 31 02:41:35 2003
@@ -208,7 +208,7 @@
 	struct evdev *evdev = list->evdev;
 	struct input_dev *dev = evdev->handle.dev;
 	struct input_absinfo abs;
-	int i, t, u;
+	int i, t, u, v;

 	if (!evdev->exist) return -ENODEV;

@@ -240,7 +240,8 @@
 			if (get_user(t, ((int *) arg) + 0)) return -EFAULT;
 			if (t < 0 || t > dev->keycodemax || !dev->keycodesize) return -EINVAL;
 			u = INPUT_KEYCODE(dev, t);
-			if (get_user(INPUT_KEYCODE(dev, t), ((int *) arg) + 1)) return -EFAULT;
+                        v = INPUT_KEYCODE(dev, t);
+			if (get_user(v, ((int *) arg) + 1)) return -EFAULT;

 			for (i = 0; i < dev->keycodemax; i++)
 				if(INPUT_KEYCODE(dev, t) == u) break;

             reply	other threads:[~2003-08-05 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 20:11 Jocelyn Mayer [this message]
2003-08-24 19:44 ` [PATCH] Fix compilation problem with 2.6.0-test2 on PPC 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=1060114295.1914.6988.camel@jma1.dev.netgem.com \
    --to=jma@netgem.com \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).