All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Prendel <andre.prendel@gmx.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [RFC PATCH v1 0/2] Add the sensors-config tool
Date: Wed, 24 Feb 2010 20:24:27 +0000	[thread overview]
Message-ID: <20100224202427.GA1914@andre-laptop> (raw)
In-Reply-To: <20100219193821.GA1917@andre-laptop>

On Wed, Feb 24, 2010 at 02:58:56PM +0100, Hans de Goede wrote:
> Hi,
> 
> Having multiple directory levels is fine by me. I was merely
> pointing out that there are some issues with that approach.
> 
> Thinking of this another possible issue is that vendors don't
> always use the same vendor string in the DMI data.
> 
> So I think that the following would be a good solution:
> 
> 1 dir per vendor, with vendor board configs in there, just like
> the wiki.
> 
> symlinks in the base dir following the symlink structure I suggested
> earlier.
> 
> This way we get the best of both worlds I think.

Sounds good. I will take some time to revise the tool and come with an
updated version.

> Regards,
> 
> Hans

Thanks,
Andre

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

      parent reply	other threads:[~2010-02-24 20:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 19:38 [lm-sensors] [RFC PATCH v1 0/2] Add the sensors-config tool Andre Prendel
2010-02-22  9:04 ` Hans de Goede
2010-02-22  9:52 ` Jean Delvare
2010-02-22 12:24 ` Hans de Goede
2010-02-22 20:28 ` Andre Prendel
2010-02-22 20:31 ` Andre Prendel
2010-02-22 20:40 ` Andre Prendel
2010-02-22 20:43 ` Jean Delvare
2010-02-22 21:26 ` Hans de Goede
2010-02-22 22:40 ` VDR User
2010-02-23  8:20 ` Hans de Goede
2010-02-23 17:00 ` VDR User
2010-02-23 20:35 ` Andre Prendel
2010-02-24 13:58 ` Hans de Goede
2010-02-24 20:24 ` Andre Prendel [this message]

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=20100224202427.GA1914@andre-laptop \
    --to=andre.prendel@gmx.de \
    --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.