Linux Input/HID development
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
To: Matt Walker <matt.g.d.walker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: backports-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Patch] Fix for so that recent Elantech touchpads are recognized as such
Date: Fri, 29 Nov 2013 22:26:45 +0100	[thread overview]
Message-ID: <52990695.5000203@hauke-m.de> (raw)
In-Reply-To: <CA+X2d=AuAm3ENDbrfk7L5fXoSiLwVU5xxKVo+MbbCf_aWu=cyg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 11/29/2013 01:00 AM, Matt Walker wrote:
> Hello,
> 
> Attached is a patch for drivers/input/mouse/elantech.c.  It allows
> recent Elantech touchpads to be detected.  I have tested it on the
> touchpad that comes with the Acer Aspire S7-392 (released ~August
> 2013)
> 
> I figure it could be backported with little effort and no danger,
> since all it does it add one to the number of values that were
> previously recognized as valid "firmware version numbers".
> 
> Begin Patch:
> 1315a1316
>>         case 8:
> End Patch
> 
> Best,
> Matt
> 
This is not a patch, I do not know what you want to do.

This is the documentation for hacking on backprts:
https://backports.wiki.kernel.org/index.php/Documentation/backports/hacking

This is the guideline for patch submission to the linux kernel which
mostly also applies for backports:
https://www.kernel.org/doc/Documentation/SubmittingPatches

Hauke

      parent reply	other threads:[~2013-11-29 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29  0:00 [Patch] Fix for so that recent Elantech touchpads are recognized as such Matt Walker
     [not found] ` <CA+X2d=AuAm3ENDbrfk7L5fXoSiLwVU5xxKVo+MbbCf_aWu=cyg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-29 21:26   ` Hauke Mehrtens [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=52990695.5000203@hauke-m.de \
    --to=hauke-5/s+jyg5szeelga04laivw@public.gmane.org \
    --cc=backports-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt.g.d.walker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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