From: James M Leddy <james.leddy@canonical.com>
To: linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com
Cc: haitao.zhang@canonical.com
Subject: [PATCH 0/1][RESUBMIT] input: fix weird issue of synaptics psmouse sync lost
Date: Tue, 9 Apr 2013 20:30:42 -0400 [thread overview]
Message-ID: <1365553843-11951-1-git-send-email-james.leddy@canonical.com> (raw)
We have been using this patch in Ubuntu kernels for 5 months now
without issue. Since patch author Eric Miao no longer works for us,
I'm sending to the list so that other distros can take advantage of
this.
Last we left off, the suggestion was to make this generic across the
entire range of protocols, not just synaptics. I'm against this for
two reasons. The first is that I don't want to have to ask for
additional testing (I don't have access to the machine). The second
and far more important reason is that I am afraid that this will break
other non-synaptics touchpads, and even though we have a wide range of
hardware, it is impossible to guarantee that it'll work on everything
out there. I will do it however if it's the way we need to go with
this.
Please let me know what you think, or if you need any additional
information or testing.
James M Leddy (1):
input: fix weird issue of synaptics psmouse sync lost
after resume
drivers/input/mouse/synaptics.c | 2 ++
1 file changed, 2 insertions(+)
--
1.7.9.5
next reply other threads:[~2013-04-10 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 0:30 James M Leddy [this message]
2013-04-10 0:30 ` [PATCH 1/1][RESUBMIT] input: fix weird issue of synaptics psmouse sync lost after resume James M Leddy
2013-04-10 1:14 ` [PATCH 0/1][RESUBMIT] input: fix weird issue of synaptics psmouse sync lost James M Leddy
2013-04-10 1:18 ` [PATCH 1/1][RESUBMIT] input: fix weird issue of synaptics psmouse sync lost after resume James M Leddy
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=1365553843-11951-1-git-send-email-james.leddy@canonical.com \
--to=james.leddy@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=haitao.zhang@canonical.com \
--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;
as well as URLs for NNTP newsgroup(s).