[lkml]   [2010]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [git pull] Input updates for 2.6.34-rc0
    On 03/09/10 18:21, Mike Frysinger wrote:
    > 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:// for-linus
    >>>>>> or
    >>>>>> 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
    In that case, I suggest asking Greg KH to pull it into staging for now
    with suitable explanation (and perhaps an ack for putting it there from


     \ /
      Last update: 2010-03-09 20:09    [W:0.029 / U:64.952 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site