From: "Jürgen Beisert" <jbe@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Jonathan Cameron" <jic23@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Marek Vašut" <marex@denx.de>,
linux-iio@vger.kernel.org,
"Fabio Estevam" <fabio.estevam@freescale.com>
Subject: Re: [PATCH] iio: adc: Move mxs-lradc out of staging
Date: Wed, 9 Oct 2013 16:14:00 +0200 [thread overview]
Message-ID: <201310091614.00683.jbe@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5AmncWZdtJjN54+PA9KBAnRf_-h8Tp=34hEckQo-S_gaw@mail.gmail.com>
Hi Fabio,
On Wednesday 09 October 2013 15:17:33 Fabio Estevam wrote:
> On Wed, Oct 9, 2013 at 10:08 AM, Jürgen Beisert <jbe@pengutronix.de> wrote:
> >> Would it be acceptable if I move the mxs TODO text into mxs-lradc.c?
> >
> > Sounds like you want to make it forgotten. ;)
>
> What would you suggest?
Keep the driver in staging until somebody can spend some effort to split this
driver into an MFD and at least into its IIO (generic ADC) and touchscreen
components. IMHO the touchscreen component should go into the input subsystem
part of the kernel tree, its not related to IIO.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-10-09 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 20:16 [PATCH] iio: adc: Move mxs-lradc out of staging Fabio Estevam
2013-10-08 20:57 ` Marek Vasut
2013-10-09 6:37 ` Lars-Peter Clausen
2013-10-09 12:31 ` Fabio Estevam
2013-10-09 13:08 ` Jürgen Beisert
2013-10-09 13:17 ` Fabio Estevam
2013-10-09 14:14 ` Jürgen Beisert [this message]
2013-10-12 10:46 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2016-02-06 22:23 Ksenija Stanojevic
2016-02-07 5:55 ` Greg KH
[not found] ` <56B8DF81.3000901@kernel.org>
2016-02-09 17:52 ` Torokhov
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=201310091614.00683.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).