From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Éric Piel" <eric.piel@tremplin-utc.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Darren Hart <dvhart@linux.intel.com>,
"lkml, " <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Carmine Iascone <carmine.iascone@st.com>,
Matteo Dameno <matteo.dameno@st.com>
Subject: Re: LIS331DLH accelerometer driver, IIO or not?
Date: Sat, 26 May 2012 14:59:14 +0100 [thread overview]
Message-ID: <20120526145914.47b7812d@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <4FC0C422.8080605@tremplin-utc.net>
> > Make it an IIO driver and then we can delete the misc driver, which
> > shouldn't have snuck in there in the first place :)
> >
>
> To be more fair to the misc driver, I wouldn't say it snucked in there,
> but more "it ended up there as the least worse place" ;-)
Because IIO spent forever in staging, as well as blocking lots of other
driver work and meaning tons of drivers are now not to be found anywhere
but obscure git trees. Thankfully they didn't manage to block the LIS
driver during this mess.
Until all the needed support for the LIS IIO driver exists outside of
staging the driver needs to stay where it is and without IIO
dependancies. It is not acceptable to cripple existing working code with
staging tree dependancies.
Hopefully commit a980e046098b0a40eaff5e4e7fcde6cf035b7c06 has finally set
the basis for this happening when it hits mainline.
Alan
next prev parent reply other threads:[~2012-05-26 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 4:29 Darren Hart
2012-05-25 5:10 ` Greg Kroah-Hartman
2012-05-25 7:45 ` Jonathan Cameron
2012-05-25 15:23 ` Darren Hart
2012-05-25 16:21 ` Jonathan Cameron
2012-05-26 11:53 ` Éric Piel
2012-05-26 13:59 ` Alan Cox [this message]
2012-05-27 3:16 ` Darren Hart
2012-05-26 17:40 ` Jonathan Cameron
2012-05-27 3:14 ` Darren Hart
2012-05-27 9:32 ` Jonathan Cameron
2012-05-27 16:27 ` Darren Hart
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=20120526145914.47b7812d@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=carmine.iascone@st.com \
--cc=dvhart@linux.intel.com \
--cc=eric.piel@tremplin-utc.net \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matteo.dameno@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®