From: "Indan Zupancic" <indan@nul.nu>
To: "Dmitry Torokhov" <dtor@insightbb.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [RFC/RFT 0/5] Input locking patches
Date: Sun, 29 Jul 2007 14:15:45 +0200 (CEST) [thread overview]
Message-ID: <49425.81.207.0.53.1185711345.squirrel@secure.samage.net> (raw)
In-Reply-To: <200707282338.48346.dtor@insightbb.com>
On Sun, July 29, 2007 05:38, Dmitry Torokhov wrote:
> Hi Indan,
>
> On Friday 27 July 2007 18:25, Indan Zupancic wrote:
>> Sorry for the babbling, just wanted to say that I've tested these
>> patches and that they seem to fix real problems.
>>
>
> Thank you for testing the patches.
Unfortunately I spoke too soon and some mouse warps occurred
yesterday. I suspect faulty hardware, so I'll try with my old
non-optical mouse. If it still happens then it's either the mobo
or the kernel. In the meantime I'll plug this one in another pc
and see if the warps happen there. After that it's running old
kernels to see if the warps happen there too. Any other ideas
to check whether it's a software or hardware problem?
The more annoying sticking key problem is gone for good though.
Greetings,
Indan
next prev parent reply other threads:[~2007-07-29 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 4:45 Dmitry Torokhov
2007-07-24 4:45 ` [RFC/RFT 1/5] Input: implement proper locking in input core Dmitry Torokhov
2007-07-24 5:35 ` Jeff Garzik
2007-07-24 5:52 ` Dmitry Torokhov
2007-07-27 23:28 ` Indan Zupancic
2007-07-29 3:50 ` Dmitry Torokhov
2007-07-29 12:50 ` Indan Zupancic
2007-07-24 4:45 ` [RFC/RFT 2/5] evdev - implement proper locking Dmitry Torokhov
2007-07-24 4:45 ` [RFC/RFT 3/5] Input: tsdev " Dmitry Torokhov
2007-07-24 4:45 ` [RFC/RFT 4/5] Input: mousedev " Dmitry Torokhov
2007-07-24 4:45 ` [RFC/RFT 5/5] Input: joydev " Dmitry Torokhov
2007-07-27 22:25 ` [RFC/RFT 0/5] Input locking patches Indan Zupancic
2007-07-29 3:38 ` Dmitry Torokhov
2007-07-29 12:15 ` Indan Zupancic [this message]
2007-07-28 4:41 Al Boldi
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=49425.81.207.0.53.1185711345.squirrel@secure.samage.net \
--to=indan@nul.nu \
--cc=dtor@insightbb.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--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 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®