linux-kernel - Re: Sensor event related attribute naming.

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] [day] [month] [year] [list]

Message-ID: <20E08A7079E04279971AFD632B5A00A9@wipblrx0099946>
Date:	Mon, 8 Nov 2010 19:37:03 +0530
From:	"Hemanth V" <hemanthv@...com>
To:	"Jonathan Cameron" <jic23@....ac.uk>,
	"Dmitry Torokhov" <dtor@...l.ru>
Cc:	"LKML" <linux-kernel@...r.kernel.org>, <linux-iio@...r.kernel.org>,
	<linux-input@...r.kernel.org>,
	"Manuel Stahl" <manuel.stahl@....fraunhofer.de>,
	"Jean Delvare" <khali@...ux-fr.org>, "Greg KH" <greg@...ah.com>,
	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"Andrew Morton" <akpm@...ux-foundation.org>, <drivers@...log.com>,
	<achew@...dia.com>, "Donggeun Kim" <dg77.kim@...sung.com>
Subject: Re: Sensor event related attribute naming.

----- Original Message ----- 
From: "Jonathan Cameron" <jic23@....ac.uk>
To: "Jonathan Cameron" <jic23@....ac.uk>
Sent: Thursday, September 30, 2010 3:36 PM
Subject: Re: Sensor event related attribute naming.


> Given the lack of further comment, I went ahead and implemented the above 
> naming
> scheme for IIO. As the above discussion with Hemanth shows, there are some 
> corner cases
> that will need futher thought in the future.
>

Jonathan, haven't seen many comments on this. Do u think the reason
might be that these interfaces are hidden behind a HAL layer like in android 
and
might not be a burning issue for many people.

Thanks
Hemanth


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