linux-kernel - Re: [git pull] Input updates for 2.6.34-rc0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a1003091021u717fb87jf3e32c7258ee4011@mail.gmail.com>
Date:	Tue, 9 Mar 2010 13:21:22 -0500
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
	Michael Hennerich <michael.hennerich@...log.com>,
	Robin Getz <rgetz@...ckfin.uclinux.org>
Subject: Re: [git pull] Input updates for 2.6.34-rc0

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-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/