From: Bastien Nocera <hadess@hadess.net>
To: Michal Suchanek <msuchanek@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH] macintosh: move mac_hid driver to input/mouse.
Date: Sun, 28 May 2017 15:26:23 +0200 [thread overview]
Message-ID: <1495977983.2423.18.camel@hadess.net> (raw)
In-Reply-To: <20170528114758.52b619f2@neko>
On Sun, 2017-05-28 at 11:47 +0200, Michal Suchanek wrote:
> On Tue, 9 May 2017 17:43:27 -0700
> Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
>
> > Hi Michal,
> >
> > On Tue, May 09, 2017 at 09:14:18PM +0200, Michal Suchanek wrote:
> > > There is nothing mac-specific about this driver. Non-mac hardware
> > > with suboptimal built-in pointer devices exists.
> > >
> > > This makes it possible to use this emulation not only on x86 and
> > > ppc
> > > notebooks but also on arm and mips.
> >
> > I'd rather we did not promote from drivers/macintosh to other
> > platforms, but rather removed it. The same functionality can be
> > done
> > from userspace.
>
> What is the status of this?
>
> Do you reply to every patch to drivers/input that is not the the core
> infrastructure that you would rather drop the driver because it can
> be
> done is in userspace?
>
> It sure can be done. Remove everything but the bus drivers and uinput
> from drivers/input and the rest can be done in userspace.
>
> The question is who does it?
>
> Are you saying that you will implement the userspace equivalent?
>
> If not then please do your job as maintainer and accept trivial
> patches
> for perfectly working drivers we have now.
>
> If you want to move drivers/input into userspace I am not against it
> but I am not willing to do that for you either.
I'd advise you to take it down a notch. We don't go yelling at each
other on this mailing-list.
next prev parent reply other threads:[~2017-05-28 13:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 19:14 [PATCH] macintosh: move mac_hid driver to input/mouse Michal Suchanek
2017-05-10 0:43 ` Dmitry Torokhov
2017-05-10 10:44 ` Michal Suchánek
2017-05-28 9:47 ` Michal Suchanek
2017-05-28 13:26 ` Bastien Nocera [this message]
2017-05-28 17:55 ` Dmitry Torokhov
2017-05-29 18:03 ` Michal Suchánek
2017-05-30 5:06 ` Dmitry Torokhov
2017-05-30 9:34 ` Michal Suchánek
2017-05-30 10:33 ` Benjamin Tissoires
2017-05-30 11:32 ` Michal Suchánek
2017-05-30 12:02 ` Benjamin Tissoires
2017-05-30 12:56 ` Michal Suchánek
2017-05-31 4:26 ` Peter Hutterer
2017-06-07 12:29 ` Michal Suchánek
2017-06-07 16:53 ` Michal Suchánek
2017-06-07 17:16 ` Dmitry Torokhov
2017-06-07 19:17 ` Michal Suchánek
2017-06-07 23:13 ` Peter Hutterer
2017-06-08 13:18 ` Michal Suchánek
2017-06-08 23:07 ` Peter Hutterer
2017-06-08 23:18 ` Dmitry Torokhov
2017-06-09 11:39 ` Michal Suchánek
2017-06-10 2:00 ` Peter Hutterer
2017-06-12 11:40 ` Michal Suchánek
2017-06-12 13:27 ` Michal Suchánek
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=1495977983.2423.18.camel@hadess.net \
--to=hadess@hadess.net \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
/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).