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] FW: PATCH: add sections for the new FTS chips to
Date: Wed, 16 Sep 2009 19:07:35 +0000	[thread overview]
Message-ID: <20090916210735.3463378b@hyperion.delvare> (raw)
In-Reply-To: <1C27BF3FB8EE3A4D8F901C22ADE1DE07CE9D65F6E0@ABGEX72E.FSC.NET>

Hi Andre,

On Wed, 16 Sep 2009 20:45:06 +0200, Andre Prendel wrote:
> On Wed, Sep 16, 2009 at 10:18:53AM +0200, Cestonaro, Thilo wrote:
> > here is a patch which adds new sections to the sensors.conf.default.
> > The fts.conf can be used as a custom configuration in the wiki.
> > 
> > I was not able to create a new page, as described at the bottom of the page, cause no create button is there and I found no register button or such thing.
> > Could someone please add this custom configuration to the wiki as long as the patch is not included in the sources.
> 
> While doing this I realized that it isn't a motherboard specific
> configuration. It's just the chip configuration. On which motherboard
> one can find the chips?
> 
> Jean, sorry I did a typo creating the page. So we now have a second
> page named "Configurations/FujitsuSiemensTechnology" :(
> Can you please delete the page? It seems I don't have the permissions.

Done.

> 
> > btw. Fujitsu Siemens Computers GmbH is known as FUJITSU TECHNOLOGY SOLUTIONS GmbH since 1st April 2009.
> > and the webpage address has changed to http://ts.fujitsu.com/, perhaps someone can change this in the device wiki page.
> 
> I've updated the wiki but now we have a mismatch between the
> manufacturer and the driver name. Jean, any objections?

This is a frequent problem, not just when manufacturers change their
name, but also when chip divisions are sold from one manufacturer to
another (for example Analog Devices to ON Semi, recently). But it
doesn't really matter. Driver names are arbitrary anyway, and once we
have settled for a name, this is how people (and sensors-detect!) know
the driver and I'd rather not change it afterwards: that's more pain
than is worth.

-- 
Jean Delvare

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

  parent reply	other threads:[~2009-09-16 19:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 10:41 [lm-sensors] PATCH: add sections for the new FTS chips to Cestonaro, Thilo
2009-09-16  8:18 ` [lm-sensors] FW: " Cestonaro, Thilo
2009-09-16 18:45 ` [lm-sensors] FW: PATCH: add sections for the new FTS chips Andre Prendel
2009-09-16 19:07 ` Jean Delvare [this message]
2009-09-21  7:46 ` [lm-sensors] FW: FW: PATCH: add sections for the new FTS chips to Cestonaro, Thilo
2009-09-27 16:48 ` [lm-sensors] FW: PATCH: add sections for the new FTS chips Andre Prendel
2009-09-28  7:43 ` [lm-sensors] PATCH: add sections for the new FTS chips to Jean Delvare
2009-09-28 18:58 ` [lm-sensors] PATCH: add sections for the new FTS chips Andre Prendel
2009-09-28 19:01 ` [lm-sensors] PATCH: add sections for the new FTS chips to Jean Delvare
2009-10-01 18:01 ` [lm-sensors] PATCH: add sections for the new FTS chips Andre Prendel
2009-10-05 13:17 ` [lm-sensors] PATCH: add sections for the new FTS chips to Cestonaro, Thilo
2009-10-05 13:40 ` Jean Delvare
2009-10-05 18:23 ` [lm-sensors] PATCH: add sections for the new FTS chips Andre Prendel
2009-10-05 19:10 ` [lm-sensors] PATCH: add sections for the new FTS chips to Jean Delvare
2009-10-06  7:17 ` [lm-sensors] PATCH: add sections for the new FTS chips Cestonaro, Thilo
2009-10-06 18:47 ` Andre Prendel
2009-10-06 18:55 ` [lm-sensors] PATCH: add sections for the new FTS chips to Jean Delvare
2009-10-07 19:42 ` [lm-sensors] PATCH: add sections for the new FTS chips Andre Prendel
2009-10-08  7:06 ` Cestonaro, Thilo
2009-10-08  7:07 ` [lm-sensors] PATCH: add sections for the new FTS chips to Jean Delvare
2009-10-08 18:17 ` [lm-sensors] PATCH: add sections for the new FTS chips Andre Prendel

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=20090916210735.3463378b@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.