linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: linux-iio@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
	Jean Delvare <khali@linux-fr.org>,
	lm-sensors@lm-sensors.org
Subject: MAX1363 IIO driver questions
Date: Fri, 23 Nov 2012 21:27:07 -0800	[thread overview]
Message-ID: <20121124052707.GA17392@roeck-us.net> (raw)

Hi all,

What would it take to move the MAX1363 driver out of staging ?

Background is that I need a hardware monitoring driver for MAX1139, and would
like to avoid using a driver from staging if possible (after all, it might
go away anytime). Another option would be to submit a hwmon driver for it,
but that doesn't seem to be the best approach.

Thanks,
Guenter

             reply	other threads:[~2012-11-24  5:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24  5:27 Guenter Roeck [this message]
2012-11-24 10:18 ` MAX1363 IIO driver questions Jonathan Cameron
2012-11-24 11:12   ` Guenter Roeck
2013-01-16  5:49   ` Guenter Roeck
2013-01-16  8:41     ` Jonathan Cameron
     [not found]       ` <20130117204549.GB22045@roeck-us.net>
2013-01-17 21:03         ` Jonathan Cameron
2013-01-17 21:37           ` Userspace IIO map instantiation [was MAX1363 IIO driver questions] Jonathan Cameron
2013-01-18 22:09           ` MAX1363 IIO driver questions Guenter Roeck
2013-01-26 11:25             ` Jonathan Cameron
2013-01-29 20:00               ` Guenter Roeck
2013-01-29 20:10                 ` Lars-Peter Clausen
2013-01-29 21:05                   ` Guenter Roeck
2013-01-29 21:21                     ` Lars-Peter Clausen
2013-01-29 21:46                       ` Doug Anderson

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=20121124052707.GA17392@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jic23@kernel.org \
    --cc=khali@linux-fr.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    /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).