linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	Michael Hennerich <michael.hennerich@analog.com>,
	Robin Getz <rgetz@blackfin.uclinux.org>
Subject: Re: [git pull] Input updates for 2.6.34-rc0
Date: Tue, 9 Mar 2010 13:21:22 -0500	[thread overview]
Message-ID: <8bd0f97a1003091021u717fb87jf3e32c7258ee4011@mail.gmail.com> (raw)
In-Reply-To: <4B9690F8.1080804@cam.ac.uk>

On Tue, Mar 9, 2010 at 13:18, Jonathan Cameron wrote:
> On 03/09/10 17:58, Mike Frysinger wrote:
>> On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
>>> On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
>>>> On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
>>>>> Hi Linus,
>>>>>
>>>>> Please pull from:
>>>>>
>>>>>        git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
>>>>> or
>>>>>        master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
>>>>>
>>>>> to receive first round of updates for the input subsystem.
>>>>
>>>> i'm trying to figure out what the problem is with the ADXL34x and
>>>> AD714x drivers you seem to have accepted (at least, you didnt say
>>>> there was anything left for us to do).  i would have expected them to
>>>> be in 2.6.33/2.6.34 already, but it seems they arent moving now.  so
>>>> what's up ?
>>>
>>> I am still spooked by the fact that this is an accelerometer and does
>>> not have to be an input device but maybe used for different purposes as
>>> well.
>>
>> the AD714x is not an accelerometer, it's a capacitance touch sensor
>>
>> i understand the ADXL34x is a bit wonky, but what else would you
>> propose ?  or just leave the driver in limbo forever until people
>> forget about it ?
>
> Perhaps whilst this remains in debate it might merge under misc, or
> even staging temporarily.  That would avoid setting a precedent for
> putting them in input.  I personally agree with Dmitry's wish to
> avoid feature drift in input, but then we don't have anything else ready
> for the big time.  Under staging the entire TODO list would be along
> lines of awaiting a suitable framework...  This is effectively what
> is going to happen to the various Ambient Light sensor drivers for
> pretty much the same reason (see responses to our recent pull request).
>
> We certainly want to be careful not to loose good drivers like this
> and also to make them available to those who wish to use them.

i dont have any problems with where exactly the driver gets merged, or
if we have a goal we're working towards (in terms of a "better"
place).  but drivers sitting in perpetual limbo sucks.
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-03-09 18:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01  8:03 [git pull] Input updates for 2.6.34-rc0 Dmitry Torokhov
2010-03-09 14:44 ` Mike Frysinger
2010-03-09 16:15   ` Cory Maccarrone
2010-03-09 17:53     ` Dmitry Torokhov
2010-03-09 17:51   ` Dmitry Torokhov
2010-03-09 17:58     ` Mike Frysinger
2010-03-09 18:10       ` Dmitry Torokhov
2010-03-09 18:13         ` Mike Frysinger
2010-03-09 18:20           ` Dmitry Torokhov
2010-03-09 19:39             ` Robin Getz
2010-03-10  8:30               ` Hennerich, Michael
2010-03-12 20:55                 ` Robin Getz
2010-03-13  8:44                   ` Dmitry Torokhov
2010-03-22  6:37           ` Dmitry Torokhov
2010-03-22  7:44             ` Mike Frysinger
2010-03-09 18:18       ` Jonathan Cameron
2010-03-09 18:21         ` Mike Frysinger [this message]
2010-03-09 19:08           ` Jonathan Cameron

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=8bd0f97a1003091021u717fb87jf3e32c7258ee4011@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jic23@cam.ac.uk \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=rgetz@blackfin.uclinux.org \
    /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).