All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [patch 2.6.23-pre] s/SENSORS_/HWMON_/  in Kconfig,
Date: Tue, 12 Jun 2007 20:44:28 +0000	[thread overview]
Message-ID: <20070612224428.6fea0dba@hyperion.delvare> (raw)
In-Reply-To: <466E2E83.4010203@gmail.com>

Hi Mark, Hi Jim,

On Tue, 12 Jun 2007 07:23:46 -0400, Mark M. Hoffman wrote:
> Hi Jim:
> 
> * Jim Cromie <jim.cromie@gmail.com> [2007-06-11 23:26:27 -0600]:
> > 
> > (patch attached, with this stuff at the top - hope thats ok)
> > 
> > This changes SENSORS to HWMON in Kconfig and Makefile,
> > which makes it agree with 'menuconfig HWMON' at the top of Kconfig,
> > and with the dir-name itself.  ISTM that theres no reason
> > (save legacy) to keep this arbitrary difference.
> 
> It will break 'make oldconfig', although I don't care *too* much about that.
> Does anyone else care one way or the other?

Yes, it will break 'make oldconfig', this is the reason why I never did
it. But in fact, I don't care too much either. People will simply
select their driver again, no big deal.

However, if we do that, let's do it completely and clean up the
occurrences of CONFIG_SENSORS_* that are left under drivers/i2c/chips
at the same time. Otherwise some confusion will be left. Jim, can you
please submit a new patch doing this?

Thanks,
-- 
Jean Delvare

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

  parent reply	other threads:[~2007-06-12 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  5:26 [lm-sensors] [patch 2.6.23-pre] s/SENSORS_/HWMON_/ in Kconfig, Jim Cromie
2007-06-12 11:23 ` Mark M. Hoffman
2007-06-12 20:44 ` Jean Delvare [this message]
2007-06-13 17:52 ` Jim Cromie
2007-06-14 18:26 ` Jean Delvare
2007-06-14 20:56 ` Jim Cromie
2007-06-15 18:20 ` Jean Delvare
2007-06-16  3:14 ` Mark M. Hoffman

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=20070612224428.6fea0dba@hyperion.delvare \
    --to=khali@linux-fr.org \
    --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.