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] PATCH: libsensors and sensors prog support for
Date: Mon, 29 May 2006 09:30:10 +0000	[thread overview]
Message-ID: <20060529113010.26023d4d.khali@linux-fr.org> (raw)
In-Reply-To: <4470B176.5000703@hhs.nl>

Hi Hans,

> > Please only include one config example in the default configuration
> > file. We just can't include one configuration section for each
> > motherboard. You can make the other configuration files available (or
> > maybe post them to this list if you have nowhere to store them
> > publicly.)
> 
> Hmm,
> 
> I guess this is non negotiable? Wouldn't it be an idea to have a doc
> (sub)dir with known working motherboard sensors.conf parts?

Your guess is right, this is non negotiable ;)

We can't afford to maintain a collection of configuration files. CVS
isn't the right place for that, as we simply don't have the manpower to
handle it.

> As you know I'm currently "working" on an lm_sensors autoconf project,
> part of which will be a database with working/good sensors.conf entries
> matched to motherboards. As I already mailed I got 4 applications todo
> this google soc project. Most applicants listed as motivation (amongst
> other things) the fact that they had configured lm_sensors in the past
> and that it was a pain to configure. This is precisely the reason why
> I've included configs for all known motherboards using the uguru in
> sensors.conf.eg, so that end users which a known motherboard can set it
> up in a breeze (compared to not having this info).
> 
> Anyways unless this turns out to be negotiable I'll create a webpage
> with the configuration info per motherboard and put a link to this page
> in sensors.conf.eg . I assume that is acceptable?

Yes, this sounds like the right thing to do. We can also list your site
in the "Motherboard configuration files" section of our useful
addresses page:
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/useful_addresses.html#sensorsconfdb

> As for your other feedback, I'll fix/make things as requested.

Thanks,
-- 
Jean Delvare


  parent reply	other threads:[~2006-05-29  9:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 18:29 [lm-sensors] PATCH: libsensors and sensors prog support for Hans de Goede
2006-05-27 21:43 ` Jean Delvare
2006-05-28 19:24 ` Hans de Goede
2006-05-29  9:30 ` Jean Delvare [this message]
2006-05-29  9:48 ` Rudolf Marek
2006-05-29  9:51 ` Hans de Goede
2006-05-29  9:59 ` Axel Thimm
2006-05-29 10:03 ` [lm-sensors] PATCH: libsensors and sensors prog support Rudolf Marek
2006-05-29 10:03 ` [lm-sensors] PATCH: libsensors and sensors prog support for Axel Thimm
2006-05-29 21:16 ` [lm-sensors] PATCH: libsensors and sensors prog support Hans de Goede
2006-06-01 14:29 ` [lm-sensors] PATCH: libsensors and sensors prog support for Hans de Goede
2006-06-02 13:50 ` Jean Delvare
2006-06-02 17:20 ` Hans de Goede
2006-06-02 18:56 ` Jean Delvare

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=20060529113010.26023d4d.khali@linux-fr.org \
    --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.