From: Antonio Ospite <ospite@studenti.unina.it>
To: Rafi Rubin <rafi@seas.upenn.edu>
Cc: linux-input@vger.kernel.org, jkosina@suse.cz, chatty@enac.fr,
evilynux@gmail.com
Subject: Re: [PATCH] HID: Major update to N-Trig touchscreen
Date: Fri, 5 Feb 2010 10:40:35 +0100 [thread overview]
Message-ID: <20100205104035.dda70313.ospite@studenti.unina.it> (raw)
In-Reply-To: <1265341963-5315-1-git-send-email-rafi@seas.upenn.edu>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On Thu, 4 Feb 2010 22:52:43 -0500
Rafi Rubin <rafi@seas.upenn.edu> wrote:
> Improvements to multitouch handling:
> enabled mt input events were were masked off
> adjusted interpretation of some hid events
> added finger tracking
>
> Pen and touch sensors moved to separate event nodes (HID_QUIRK_MULTI_INPUT) and related changes removing unnecessary code and events that supported the multiplexed streams. Added names to represent the sensor associated with each event node. Split event handlers for the sensors to make the code a bit more readable.
>
Just a style-question, isn't the commit message supposed to be wrapped
at 72-80 chars as well? This is not stated explicitly in
Documentation/SubmittingPatches Section 15.
Thanks,
Antonio
--
Antonio Ospite
http://ao2.it
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-02-05 9:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 3:52 [PATCH] HID: Major update to N-Trig touchscreen Rafi Rubin
2010-02-05 4:16 ` Rafi Rubin
2010-02-05 5:53 ` Dmitry Torokhov
2010-02-05 7:27 ` Rafi Rubin
2010-02-05 10:39 ` Jiri Kosina
2010-02-06 0:50 ` Rafi Rubin
2010-02-05 9:40 ` Antonio Ospite [this message]
2010-02-06 0:44 Rafi Rubin
2010-02-06 0:57 ` Rafi Rubin
2010-02-06 0:56 Rafi Rubin
2010-02-06 1:01 Rafi Rubin
2010-02-06 1:03 ` Rafi Rubin
2010-02-08 15:49 ` Jiri Kosina
2010-02-08 16:45 ` Rafi Rubin
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=20100205104035.dda70313.ospite@studenti.unina.it \
--to=ospite@studenti.unina.it \
--cc=chatty@enac.fr \
--cc=evilynux@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=rafi@seas.upenn.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.