From: Arnd Bergmann <arnd@arndb.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
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>
Subject: Re: [PATCH] Add STMicroelectronics LPS001WP pressure sensor device driver into misc
Date: Mon, 14 Mar 2011 21:36:43 +0100 [thread overview]
Message-ID: <201103142136.43566.arnd@arndb.de> (raw)
In-Reply-To: <20110314211809.29da8518@endymion.delvare>
On Monday 14 March 2011 21:18:09 Jean Delvare wrote:
> Jonathan is correct. Pressure sensors are not hardware monitoring
> devices, their drivers have nothing to do in drivers/hwmon. This is
> something for drivers/misc or staging/iio.
I generally try to prevent people from adding more ad-hoc interfaces
to drivers/misc. Anything that is called a drivers/misc driver to me
must qualify as "there can't possibly be a second driver with the
same semantics", otherwise it should be part of another subsystem
with clear rules, or be put into its own file system.
While it seems that right now everyone is just trying to keep move
the driver to some other subsystem, I think it's worth noting that
it is indeed a useful thing to have the driver, I'm optimistic
that we can find some place for it. ;-)
Now how about the IIO stuff? This is the first time I've even
heard about it. Does it have any major disadvantages besides
being staging-quality?
Arnd
next prev parent reply other threads:[~2011-03-14 20:36 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 [this message]
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
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=201103142136.43566.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=carmine.iascone@st.com \
--cc=guenter.roeck@ericsson.com \
--cc=jic23@cam.ac.uk \
--cc=khali@linux-fr.org \
--cc=linux-doc@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