linux-kernel - Re: LIS331DLH accelerometer driver, IIO or not?

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: <20120526145914.47b7812d@pyramind.ukuu.org.uk>
Date:	Sat, 26 May 2012 14:59:14 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Éric Piel <eric.piel@...mplin-utc.net>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Darren Hart <dvhart@...ux.intel.com>,
	"lkml, " <linux-kernel@...r.kernel.org>,
	Jonathan Cameron <jic23@...nel.org>,
	Lars-Peter Clausen <lars@...afoo.de>,
	Carmine Iascone <carmine.iascone@...com>,
	Matteo Dameno <matteo.dameno@...com>
Subject: Re: LIS331DLH accelerometer driver, IIO or not?

> > Make it an IIO driver and then we can delete the misc driver, which
> > shouldn't have snuck in there in the first place :)
> >
> 
> To be more fair to the misc driver, I wouldn't say it snucked in there, 
> but more "it ended up there as the least worse place" ;-)

Because IIO spent forever in staging, as well as blocking lots of other
driver work and meaning tons of drivers are now not to be found anywhere
but obscure git trees. Thankfully they didn't manage to block the LIS
driver during this mess.

Until all the needed support for the LIS IIO driver exists outside of
staging the driver needs to stay where it is and without IIO
dependancies. It is not acceptable to cripple existing working code with
staging tree dependancies.

Hopefully commit a980e046098b0a40eaff5e4e7fcde6cf035b7c06 has finally set
the basis for this happening when it hits mainline.

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