All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 4/5] hwmon: (lm75) Tune resolution and sample time per chip
Date: Thu, 14 Mar 2013 16:00:30 +0000	[thread overview]
Message-ID: <20130314160030.GA2734@roeck-us.net> (raw)
In-Reply-To: <20130312155108.054dd75e@endymion.delvare>

On Thu, Mar 14, 2013 at 04:22:05PM +0100, Jean Delvare wrote:
> On Thu, 14 Mar 2013 08:16:28 -0700, Guenter Roeck wrote:
> > On Thu, Mar 14, 2013 at 08:28:57AM +0100, Jean Delvare wrote:
> > > And if this ultimately lets us remove support for some chips from the
> > > w83627ehf driver and make it look sane again, I'm all for it.
> > 
> > Makes sense. This also makes one of the patches I submitted for w83627ehf
> > unnecessary, as it affects nct6775/nct6776 support.
> 
> Not necessarily an issue, having both drivers overlap for a period of
> time is desirable for smooth transition.
> 
Agreed. More a matter of time needed for the code review. I'll let you decide.

Dropping nct6775/nct6776 from the w83627ehf driver will reduce its size
by more than 500 LOC, and its size by more than 7k (49k -> 41.5k) on x86_64.

Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2013-03-14 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 14:51 [lm-sensors] [PATCH 4/5] hwmon: (lm75) Tune resolution and sample time per chip Jean Delvare
2013-03-12 15:55 ` Guenter Roeck
2013-03-12 16:34 ` Jean Delvare
2013-03-12 17:26 ` Guenter Roeck
2013-03-13 11:15 ` Jean Delvare
2013-03-13 21:50 ` Guenter Roeck
2013-03-13 21:56 ` Jean Delvare
2013-03-13 23:16 ` Guenter Roeck
2013-03-14  7:28 ` Jean Delvare
2013-03-14 15:16 ` Guenter Roeck
2013-03-14 15:22 ` Jean Delvare
2013-03-14 16:00 ` 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=20130314160030.GA2734@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.