linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Srihari Vijayaraghavan <linux.bug.reporting@gmail.com>
Cc: linux-input@vger.kernel.org,
	"Mateusz Jończyk" <mat.jonczyk@o2.pl>,
	"Zakariya Dehlawi" <zdehlawi@gmail.com>,
	"Guillaume Bouchard" <guillaum.bouchard@gmail.com>
Subject: Re: [PATCH 1/1] Elantech touchpad detection fix for laptops
Date: Wed, 7 Jan 2015 17:23:06 -0800	[thread overview]
Message-ID: <20150108012306.GC8570@dtor-ws> (raw)
In-Reply-To: <CAEK4c-_GTLu0jRLaX-na2-mou6qGX4A8p2rS7Q_QnM+DNKZWdg@mail.gmail.com>

On Wed, Jan 07, 2015 at 08:11:36PM +1100, Srihari Vijayaraghavan wrote:
> On 7 January 2015 at 19:23, Srihari Vijayaraghavan
> <linux.bug.reporting@gmail.com> wrote:
> > On 7 January 2015 at 18:44, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> >> Hi Srihari,
> >
> > Hello Dimitry,
> >
> > Thanks for your feedback. Much appreciated.
> >
> >> On Mon, Jan 05, 2015 at 07:45:39PM +1100, Srihari Vijayaraghavan wrote:
> >>> Hello Folks & Dmitry,
> >>>
> >>> Further to the previous patch, here is the current version (against
> >>> mainline) updated with the DMI info of another laptop model where this
> >>> fix had helped a user.
> >>>
> >>> Can you please review it & give some feedback? If it looks good as it
> >>> is, then on behalf of all affected users (including yours truly), may
> >>> I request for it to be merged upstream (and possibly stable too)?
> >>>
> >>> (If the patch gets spoiled by gmail, please ref to this bugzilla URL,
> >>> where this patch is there as a file attachment:
> >>> https://bugzilla.kernel.org/show_bug.cgi?id=81331)
> >>
> >> I am not terribly happy with having fiddling with keyboard from i8042
> >> core, but I guess that's what we have to do unless someone has better
> >> idea...
> >
> > Agreed 100%. Regrettably, seeing how psmouse_do_detect() doesn't even
> > get invoked, this heavy handed approach had to be taken at i8042 core.
> > However, as you've pointed out, if there is any better idea, we're all
> > ears.
> >
> >> I'll drop mention of Elantech from the option though as it may well be
> >> needed for other devices in the future.
> >
> > A version of the patch (against mainline) incorporating your ideas
> > (i.e., without too much Elantech bashing) is attached to this email
> > for your review.
> >
> >> Thanks!
> 
> [Sorry to respond to my own email.]
> 
> Here's a better version, removing Elantech ref from the table name.

Applied after massaging messages some more. Thank you.

-- 
Dmitry

  reply	other threads:[~2015-01-08  1:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  0:17 [PATCH 1/1] Elantech touchpad detection fix for laptops Srihari Vijayaraghavan
2015-01-05  8:45 ` Srihari Vijayaraghavan
2015-01-07  7:44   ` Dmitry Torokhov
2015-01-07  8:23     ` Srihari Vijayaraghavan
2015-01-07  9:11       ` Srihari Vijayaraghavan
2015-01-08  1:23         ` Dmitry Torokhov [this message]
2015-01-08  5:02           ` Srihari Vijayaraghavan
2015-01-08 22:09             ` Dmitry Torokhov

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=20150108012306.GC8570@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=guillaum.bouchard@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux.bug.reporting@gmail.com \
    --cc=mat.jonczyk@o2.pl \
    --cc=zdehlawi@gmail.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).