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] Motherboard-specific configurations (sensors4mobo)
Date: Sat, 31 Mar 2007 12:50:41 +0000	[thread overview]
Message-ID: <20070331145041.12f4ec25.khali@linux-fr.org> (raw)
In-Reply-To: <46084A44.4070101@eberian.com>

Hi Ivo,

On Thu, 29 Mar 2007 15:20:53 +0200, Ivo Manca wrote:
> One thing I noticed, looking through your code, was the fact that your 
> script is capable of finding multipe matches. I wonder whether or not this 
> is something we want to have there?
> Giving a random, unique DMI string, there should only be one possible 
> configuration, unless the dmistrings are bogus.
> 
> It is possible that users want to improve the config, but then he or she 
> should just modify the existing and upload it, isn't it?
> So I don't really see a point of supporting more matches. Maybe I'm 
> overlooking something.

Different people might upload a configuration file for the same
motherboard, in the "unconfirmed" state or whatever we call it. Until
someone reviews them, validates one of them and discards the other, we
have two files for the same board. So yes, it can happen. There should
never be several "confirmed" configuration files for a given board,
though.

Now, what is true of the website database may not be true of the local
cache (files in a directory, if we do that.) We may decide to only
export the confirmed files for the cache, for example, or only one of
the possible configurations (maybe based on a mark given by the site
visitors.) I have no strong opinion on this.

-- 
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-03-31 12:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 22:33 [lm-sensors] Motherboard-specific configurations (sensors4mobo) Ed Lucas
2007-03-27 15:39 ` Jean Delvare
2007-03-27 16:07 ` Ivo Manca
2007-03-28  9:30 ` Ed Lucas
2007-03-28 10:56 ` Ivo Manca
2007-03-28 11:20 ` Hans de Goede
2007-03-28 11:49 ` Ed Lucas
2007-03-28 12:07 ` Ivo Manca
2007-03-28 17:09 ` David Hubbard
2007-03-29  8:03 ` Pinkel
2007-03-29 10:00 ` Ed Lucas
2007-03-29 13:20 ` Ivo Manca
2007-03-29 14:18 ` Ed Lucas
2007-03-29 14:56 ` Hans de Goede
2007-03-31 12:22 ` Jean Delvare
2007-03-31 12:36 ` Jean Delvare
2007-03-31 12:42 ` Jean Delvare
2007-03-31 12:45 ` Jean Delvare
2007-03-31 12:50 ` Jean Delvare [this message]
2007-04-04  9:34 ` Ivo Manca
2007-04-08 11:13 ` 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=20070331145041.12f4ec25.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.