From: Joe Perches <joe@perches.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] MAINTAINERS: Add an entry for the input MT protocol
Date: Wed, 23 Jun 2010 15:46:26 -0700 [thread overview]
Message-ID: <1277333186.31591.102.camel@Joe-Laptop.home> (raw)
In-Reply-To: <4C228B49.5000408@euromail.se>
On Thu, 2010-06-24 at 00:31 +0200, Henrik Rydberg wrote:
> Joe Perches wrote:
> > On Thu, 2010-06-24 at 00:04 +0200, Henrik Rydberg wrote:
> >> This patch adds a maintainer for the input multitouch (MT) protocol,
> >> such that get_maintainer.pl selects it whenever an MT event is present
> >> in the patch.
> >> +MULTITOUCH INPUT MT PROTOCOL
> >> +M: Henrik Rydberg <rydberg@euromail.se>
> >> +L: linux-input@vger.kernel.org
> >> +S: Maintained
> >> +F: Documentation/input/multi-touch-protocol.txt
> >> +K: ABS_MT
> > That doesn't seem to match anything other than multitouch
> > stuff, but it's probably best to specify the pattern as
> > much as possible.
> > If you didn't know, K: entries can be entered as perl regex,
> > so maybe something like:
> > K: \b(ABS|SYN)_MT_
> Thanks for the info. However, since every application using the MT protocol by
> necessity uses at least one event called ABS_MT*, it should be fine as is,
> shouldn't it?
Maybe. The leading \b and trailing _ are just attempts to
avoid potential clashes with future stuff.
next prev parent reply other threads:[~2010-06-23 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 22:04 [PATCH] MAINTAINERS: Add an entry for the input MT protocol Henrik Rydberg
2010-06-23 22:27 ` Joe Perches
2010-06-23 22:31 ` Henrik Rydberg
2010-06-23 22:46 ` Joe Perches [this message]
2010-06-23 22:54 ` Dmitry Torokhov
2010-06-23 22:56 ` Henrik Rydberg
2010-06-24 10:12 Henrik Rydberg
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=1277333186.31591.102.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).