Linux IIO development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "ludovic.tancerel@maplehightech.com"
	<ludovic.tancerel@maplehightech.com>
Cc: Michal Marek <mmarek@suse.cz>,
	William Markezana <william.markezana@meas-spec.com>,
	Jean Delvare <jdelvare@suse.com>,
	Jonathan Cameron <jic23@kernel.org>,
	lm-sensors@lm-sensors.org, linux-iio@vger.kernel.org
Subject: Re: Duplicate htu21 drivers
Date: Wed, 28 Oct 2015 05:15:58 -0700	[thread overview]
Message-ID: <20151028121558.GB10739@roeck-us.net> (raw)
In-Reply-To: 5630AE44.3040803@suse.cz

On Wed, Oct 28, 2015 at 12:53:12PM +0100, ludovic.tancerel@maplehightech.com wrote:
> I was not sure about the timing for the plan … :)
> Now that the patch has been approved for IIO, then indeed I can remove the patch for htu21 in hwmon.

Yes, the driver in hwmon needs to be removed. Patch welcome.

Guenter

> Thanks,
> Ludovic
> 
> 
> 
> > Le 28 oct. 2015 à 12:15, Michal Marek <mmarek@suse.cz> a écrit :
> > 
> > Dne 28.10.2015 v 11:52 ludovic.tancerel@maplehightech.com napsal(a):
> >> Hello Michal,
> >> 
> >> the plan discussed with Jonathan and Guenter was to remove the driver
> >> in hwmon once the iio one was introduced.
> >> 
> >> Should I  provide a patch in Kconfig to make them conflict as of now
> >> ?
> > 
> > Then you can either execute your plan :), or make the hwmon driver
> > depend on HTU21=n.
> > 
> > Michal
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2015-10-28 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 10:03 Duplicate htu21 drivers Michal Marek
     [not found] ` <20151028105128.770BF1E93@relay1.suse.de>
2015-10-28 11:15   ` Michal Marek
2015-10-28 12:15     ` Guenter Roeck [this message]

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=20151028121558.GB10739@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=ludovic.tancerel@maplehightech.com \
    --cc=mmarek@suse.cz \
    --cc=william.markezana@meas-spec.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