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: <20100309181037.GB19814@core.coreip.homeip.net>
Date:	Tue, 9 Mar 2010 10:10:37 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	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 09, 2010 at 12:58:24PM -0500, 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
>

OK, will dig it up.
 
> 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 ?

No, just till we have proper framework for it to be merged into.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ