From: Henrik Rydberg <rydberg@bitmath.org>
To: Peter Hutterer <peter.hutterer@who-t.net>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joe Perches <joe@perches.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
linux-input <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update rydberg's addresses
Date: Wed, 21 Jan 2015 16:25:07 +0100 [thread overview]
Message-ID: <54BFC4D3.6090607@bitmath.org> (raw)
In-Reply-To: <20150121043520.GB17900@jelly.redhat.com>
Hi Peter,
> it wasn't the first reaction. it was the third, after we hacked up
> synaptics [1], then libinput [2], both rather unsatisfactory. Not sure what
> chromeos does but they'll probably would need similar code. And any other
> users of the evdev API of course.
So if this approach did not work very well in userland, why would it work any
better in the kernel?
Henrik
next prev parent reply other threads:[~2015-01-21 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 9:06 [PATCH] MAINTAINERS: Update rydberg's addresses Henrik Rydberg
2015-01-19 21:08 ` Benjamin Tissoires
2015-01-20 0:13 ` Dmitry Torokhov
2015-01-20 0:34 ` Benjamin Tissoires
2015-01-20 22:26 ` Henrik Rydberg
2015-01-21 4:35 ` Peter Hutterer
2015-01-21 15:25 ` Henrik Rydberg [this message]
2015-01-21 16:23 ` Benjamin Tissoires
2015-01-21 19:38 ` Henrik Rydberg
2015-01-22 4:21 ` Fixing touch point jumps in the kernel (was Re: [PATCH] MAINTAINERS: Update rydberg's addresses) Peter Hutterer
2015-01-22 8:00 ` Henrik Rydberg
2015-02-15 12:19 ` [PATCH] MAINTAINERS: Update rydberg's addresses Pavel Machek
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=54BFC4D3.6090607@bitmath.org \
--to=rydberg@bitmath.org \
--cc=akpm@linux-foundation.org \
--cc=benjamin.tissoires@gmail.com \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=peter.hutterer@who-t.net \
/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).