public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Berthold Cogel <cogel@uni-koeln.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, nigel@nigel.suspend2.net,
	dtor@mail.ru, jikos@jikos.cz, akpm@linux-foundation.org,
	linux-usb-owner@vger.kernel.org
Subject: Re: Oops in evdev_disconnect for kernel 2.6.23.12
Date: Mon, 07 Jan 2008 21:54:42 +0100	[thread overview]
Message-ID: <47829192.7030403@uni-koeln.de> (raw)
In-Reply-To: <20080106234528.GV27894@ZenIV.linux.org.uk>

Al Viro schrieb:
> On Sun, Jan 06, 2008 at 10:15:16PM +0100, Berthold Cogel wrote:
>> I did that and got this in 'make modules':
>>
>>   CC [M]  drivers/input/joydev.o
>>   CC [M]  drivers/input/evdev.o
>> drivers/input/evdev.c: In function 'evdev_do_ioctl':
>> drivers/input/evdev.c:749: error: 'struct input_dev' has no member named 
>> 'event_lock'
>> drivers/input/evdev.c:757: error: 'struct input_dev' has no member named 
>> 'event_lock'
>> make[2]: *** [drivers/input/evdev.o] Fehler 1
>> make[1]: *** [drivers/input] Fehler 2
>> make: *** [drivers] Fehler 2
>>
>>
>> The next piece of the puzzle:
>>
>> No oops with 2.6.24-rc6 vanilla and the same kernel patched with 
>> TuxOnIce 3.0-rc3 for kernel 2.6.24-rc3. A minor nit was that I had to 
>> rebuild the xorg driver for the tablet to get it working.
> 
> No puzzle at all - the changeset in question is present in -rc3.  As for
> the errors - looks like it does indeed depend on the previous changeset.
> After poking a bit in the archived thread, http://lkml.org/lkml/2007/7/24/19
> appears to contain the previous one.

Bingo!

Those two patches solved the oops. I can remove and reconnnect the 
tablet without problems.

Regards,
Berthold

  reply	other threads:[~2008-01-07 20:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 19:26 Oops in evdev_disconnect for kernel 2.6.23.12 Berthold Cogel
2008-01-01 20:35 ` Berthold Cogel
2008-01-01 21:17 ` Nigel Cunningham
2008-01-05  9:30   ` Andrew Morton
2008-01-05  6:52 ` Al Viro
2008-01-06  0:14   ` Berthold Cogel
2008-01-06  0:17     ` Al Viro
2008-01-06 19:39       ` Berthold Cogel
2008-01-06 20:15         ` Al Viro
2008-01-06 21:15           ` Berthold Cogel
2008-01-06 23:45             ` Al Viro
2008-01-07 20:54               ` Berthold Cogel [this message]
2008-02-02  2:58                 ` Martin Bauer
2008-02-03  9:33                   ` Martin Bauer
2008-01-06  1:50     ` Nigel Cunningham

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=47829192.7030403@uni-koeln.de \
    --to=cogel@uni-koeln.de \
    --cc=akpm@linux-foundation.org \
    --cc=dtor@mail.ru \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-owner@vger.kernel.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=viro@ZenIV.linux.org.uk \
    /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