All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: mems applications <mems.applications@st.com>
Cc: carmine.iascone@st.com, matteo.dameno@st.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: lis331dlh: add lis331dlh driver
Date: Tue, 9 Nov 2010 09:35:40 -0800	[thread overview]
Message-ID: <20101109173540.GA20370@suse.de> (raw)
In-Reply-To: <1289323527-5501-1-git-send-email-carmine.iascone@st.com>

On Tue, Nov 09, 2010 at 06:25:27PM +0100, mems applications wrote:
> Add STMicroelectronics LIS331DLH digital accelerometer device driver
> 
> From: Carmine Iascone <carmine.iascone@st.com>
> ---
>  drivers/staging/Kconfig               |    2 +
>  drivers/staging/Makefile              |    1 +
>  drivers/staging/lis331dlh/Kconfig     |    7 +
>  drivers/staging/lis331dlh/Makefile    |    1 +
>  drivers/staging/lis331dlh/lis331dlh.c |  836 +++++++++++++++++++++++++++++++++
>  drivers/staging/lis331dlh/lis331dlh.h |   83 ++++
>  6 files changed, 930 insertions(+), 0 deletions(-)

Why is this a staging driver?  What is keeping it from being merged to
the main portion of the kernel tree?

Can you please provide a TODO file that lists the things left to do on
it, and provide some email addresses to contact you for it?  Look at the
other TODO files in drivers/staging/*/TODO for examples.

thanks,

greg k-h

  reply	other threads:[~2010-11-09 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 17:25 [PATCH] staging: lis331dlh: add lis331dlh driver mems applications
2010-11-09 17:35 ` Greg KH [this message]
2010-11-10 11:51   ` Carmine IASCONE
2010-11-10 15:17     ` Jiri Slaby
2010-11-10 16:04       ` Greg KH
2010-11-10 17:12         ` Carmine IASCONE
2010-11-18 16:27           ` Jonathan Cameron
2010-11-18 16:51             ` Guenter Roeck
2010-11-09 20:32 ` Jiri Slaby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101109173540.GA20370@suse.de \
    --to=gregkh@suse.de \
    --cc=carmine.iascone@st.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteo.dameno@st.com \
    --cc=mems.applications@st.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.