[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100521172222.GB26439@core.coreip.homeip.net>
Date: Fri, 21 May 2010 10:22:22 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Henrik Rydberg <rydberg@...omail.se>
Cc: Ping Cheng <pinglinux@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
Mika Kuoppala <mika.kuoppala@...ia.com>,
Peter Hutterer <peter.hutterer@...-t.net>,
Benjamin Tissoires <tissoire@...a.fr>,
Stephane Chatty <chatty@...c.fr>,
Rafi Rubin <rafi@...s.upenn.edu>,
Michael Poole <mdpoole@...ilus.org>
Subject: Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3)
On Fri, May 21, 2010 at 06:56:35PM +0200, Henrik Rydberg wrote:
> Dmitry Torokhov wrote:
> > On Friday 21 May 2010 09:36:03 am Henrik Rydberg wrote:
> >> Ping Cheng wrote:
> >>> Hi Henrik,
> >>>
> >>> Thank you for your quick turnaround. Two minor comments in line.
> >>>
> >>> Ping
> >> Thanks for those, yes, both mistakes. Dmitry, in case you find these last
> >> versions acceptable, perhaps one could change them manually:
> >>
> >> 1. Patch description: s/SYN_MT_SLOT/ABS_SLOT/
> >
> > Not ABS_MT_SLOT?
>
> I wrote an argument for ABS_SLOT in the first patch, in short there is a
> namespace clash I would like to avoid.
>
Hm, I am not sure I follow that argument. While you are saying that slot
is not an MT event it is certainly not an ST event either. I would even
say that slot _is_ an MT event since it signals current "slot" or group
of MT data to userspace. Am I missing something?
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists