linux-kernel - Re: [PATCH] staging: lis331dlh: add lis331dlh driver

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: <20101110160412.GB10561@suse.de>
Date:	Wed, 10 Nov 2010 08:04:12 -0800
From:	Greg KH <gregkh@...e.de>
To:	Carmine IASCONE <carmine.iascone@...com>
Cc:	Jiri Slaby <jirislaby@...il.com>,
	Matteo DAMENO <matteo.dameno@...com>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	mems applications <mems.applications@...com>,
	Alan Cox <alan.cox@...el.com>
Subject: Re: [PATCH] staging: lis331dlh: add lis331dlh driver

On Wed, Nov 10, 2010 at 04:17:41PM +0100, Jiri Slaby wrote:
> On 11/10/2010 12:51 PM, Carmine IASCONE wrote:
> > Hi Greg, Hi JS,
> > Matteo and I have started to develop linux device drivers for our STMicroelectronics sensors about one year ago. Our main target is the Android platform (mobile phone or tablet pc), and for this reason the drivers are thought to be used on I2C bus. The drivers are enough stable, we have several customers that are using them, and also with the advice of these customers, we would like to make available them for all the linux community, merging them in the kernel upstream to be used in all linux supported platforms.
> > The drivers have had a initial review by Alan Cox, that gives us some very precious advices to improve the style and robustness of the drivers. 
> > We are newbies in patch generation and submission: we have followed the instructions in the Greg's video on you tube to create this first patch, so sorry if there is something that we missed. We thought to put the driver in staging directory, because before merging them in the main tree we would like to have a general revision, and also because in this first release we haven't managed the device interrupts yet. At the end the right position for these drivers could be drivers/input/misc.
> > How do we proceed now? Do we need to generate a new patch adding the TODO file? Please advice.
> 
> Hi, well, I don't think this should go into staging at all as I think
> it's clean enough to go upstream directly (but I repeat I'm no IIC
> expert). So please resend to IIC people:
> I2C SUBSYSTEM
> M:      "Jean Delvare (PC drivers, core)" <khali@...ux-fr.org>
> M:      "Ben Dooks (embedded platforms)" <ben-linux@...ff.org>
> L:      linux-i2c@...r.kernel.org
> 
> but before that, move that out of staging to drivers/i2c/ (or anywhere
> where it make sense).
> 
> It's perfectly OK to add functionality later (IRQs).

I agree, this should be sent to Jean and the i2c developers first.
Please work to get your driver into the main tree, only use staging as a
last-resort if you have a lot of work left to do on the code.

thanks,

greg k-h
--
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/