public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
	Jean Delvare <khali@linux-fr.org>,
	mems applications <mems.applications@st.com>,
	rdunlap@xenotime.net, carmine.iascone@st.com,
	matteo.dameno@st.com, rubini@cvml.unipv.it,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Guenter Roeck <guenter.roeck@ericsson.com>,
	Greg KH <greg@kroah.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] Add STMicroelectronics LPS001WP pressure sensor device driver into misc
Date: Tue, 15 Mar 2011 14:31:21 +0100	[thread overview]
Message-ID: <201103151431.22052.arnd@arndb.de> (raw)
In-Reply-To: <20110315125149.GC17277@sirena.org.uk>

On Tuesday 15 March 2011, Mark Brown wrote:
> > 2) Basically make a copy.  This would look like the original patch set did when we went
> 
> A third option is just to lift everything out of staging roughly as it
> is now with anything that definitely needs redoing dropped, addressing
> any review comments for mainline but not doing much else, and then
> resume working on adding additional stuff.  It sounds like the userspace
> interfaces that are there at present are mostly OK and most of the
> issues are in-kernel?
> 
> You could perhaps have a Kconfig control for disabling any experimental
> features in the API if you want to give people hints about areas that
> are likely to churn.

I agree, that sounds like a good idea for preparing the code before a split.

	Arnd

  reply	other threads:[~2011-03-15 13:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 18:55 [PATCH] Add STMicroelectronics LPS001WP pressure sensor device driver into misc mems applications
2011-03-14 19:19 ` Jonathan Cameron
2011-03-14 19:46   ` Arnd Bergmann
2011-03-14 20:14     ` Jonathan Cameron
2011-03-14 20:18       ` Jean Delvare
2011-03-14 20:27         ` Guenter Roeck
2011-03-14 20:36         ` Arnd Bergmann
2011-03-14 21:42           ` Jean Delvare
2011-03-14 22:48             ` Guenter Roeck
2011-03-15  9:24               ` Arnd Bergmann
2011-03-15 11:30                 ` Jonathan Cameron
2011-03-15 13:58                   ` Arnd Bergmann
2011-03-14 23:23             ` Jonathan Cameron
2011-03-15  9:38               ` Arnd Bergmann
2011-03-15 11:11                 ` Jonathan Cameron
2011-03-15 12:51                   ` Mark Brown
2011-03-15 13:31                     ` Arnd Bergmann [this message]
2011-03-15 14:35                       ` Jonathan Cameron
2011-03-15 14:38                     ` Jonathan Cameron
2011-03-15 13:29                   ` Arnd Bergmann
2011-03-15 14:47                     ` Jonathan Cameron
2011-03-15 16:50                       ` Arnd Bergmann

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=201103151431.22052.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=carmine.iascone@st.com \
    --cc=greg@kroah.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=jic23@cam.ac.uk \
    --cc=khali@linux-fr.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteo.dameno@st.com \
    --cc=mems.applications@st.com \
    --cc=rdunlap@xenotime.net \
    --cc=rubini@cvml.unipv.it \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox