All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Re: [RFC PATCH 2.6.12-rc3-mm2 1/2] i2c: new sysfs class
Date: Mon, 23 May 2005 14:48:11 +0000	[thread overview]
Message-ID: <mffDf43m.1116851987.0503830.khali@localhost> (raw)
In-Reply-To: <20050503034928.GC4977@jupiter.solarsys.private>


Hi Yani,

> (...) It would seem to me that basically everything
> under drivers/i2c/chips should be moved into drivers/hwmon

No, not all i2c chip drivers are hardware monitoring monitors. At least
the following should stay in drivers/i2c/chips:
* ds1337
* eeprom
* isp1301_omap (what is this BTW?)
* m41t00
* pcf8574
* pcf8591
* rtc8564

And then there's atxp1, not too sure what to do with this one (it's
meant to overclock systems, not monitor them, but it shares code and
interface with hwmon).

> (...) and perhaps
> drivers/i2c/bus to drivers/i2c (although the latter isn't necessary,
> it just makes sense to me).

I don't this it is a good idea. The current scheme makes it clear which
drivers create i2c busses, which are i2c chip drivers, which are
algorithms and which are core drivers. I wouldn't change that.

Thanks,
--
Jean Delvare

  parent reply	other threads:[~2005-05-23 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 [RFC PATCH 2.6.12-rc3-mm2 1/2] i2c: new sysfs class "hwmon" Mark M. Hoffman
2005-05-19  6:25 ` Greg KH
2005-05-21 15:22 ` [lm-sensors] Re: [RFC PATCH 2.6.12-rc3-mm2 1/2] i2c: new sysfs Yani Ioannou
2005-05-23  4:01 ` Mark M. Hoffman
2005-05-23  5:37 ` Yani Ioannou
2005-05-23 14:48 ` Jean Delvare [this message]
2005-05-23 16:28 ` Yani Ioannou
2005-05-25  3:42 ` Yani Ioannou
2005-05-26  5:38 ` Mark M. Hoffman
2005-05-26  5:55 ` Mark M. Hoffman
2005-05-26  6:18 ` Yani Ioannou

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=mffDf43m.1116851987.0503830.khali@localhost \
    --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.