From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, Lawrence Steeger <vendor@russte.com>
Subject: Re: [PATCH] Input: add i8042.noloop quirk for MS Virtual Machine
Date: Wed, 21 Nov 2007 14:24:08 -0500 [thread overview]
Message-ID: <d120d5000711211124r5f97a79eh12e75ea4bec19499@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711171045390.12807@jikos.suse.cz>
Hi Jiri,
On Nov 17, 2007 4:46 AM, Jiri Kosina <jkosina@suse.cz> wrote:
> From: Jiri Kosina <jkosina@suse.cz>
>
> Input: add i8042.noloop quirk for MS Virtual Machine
>
> When booted under Microsoft Virtual Machine, the noloop quirk is needed,
> otherwise PS/2 mouse is not properly detected.
>
> Reported-by: Lawrence Steeger <vendor@russte.com>
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
>
Applied to my "for-linus" branch for .24.
--
Dmitry
prev parent reply other threads:[~2007-11-21 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 9:46 [PATCH] Input: add i8042.noloop quirk for MS Virtual Machine Jiri Kosina
2007-11-21 19:24 ` 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=d120d5000711211124r5f97a79eh12e75ea4bec19499@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=vendor@russte.com \
/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).