All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] dynamic chip support in libsensors + generic chip
Date: Mon, 09 Apr 2007 19:56:31 +0000	[thread overview]
Message-ID: <461A9EAE.3010601@hhs.nl> (raw)
In-Reply-To: <461A59D4.2050409@hhs.nl>

Bob Schlärmann wrote:
> On Mon, 09 Apr 2007 17:20:52 +0200
> Hans de Goede <j.w.r.degoede@hhs.nl> wrote:
> 
>> ...
>> So please test this:
>> 1) checkout the 3.0.0 branch:
>>     svn checkout
>> http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0 2)
>> comment the entries for your chips int he table at the end of
>> lib/chips.c and in the table near the end of progs/sensors/main.c 3)
> Note that this isn't needed if you give sensors the -g argument. This
> forces sensors to use the generic printing routines.
> 

Yes, the removal from progs/sensors/main.c isn't really necessary to test the 
generic printing routines, that can be done with -g too. However the removal / 
commenting from lib/chips.c _really_ is necessary to test the dynamic chip support.

Regards,

Hans


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

  parent reply	other threads:[~2007-04-09 19:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 15:20 [lm-sensors] dynamic chip support in libsensors + generic chip Hans de Goede
2007-04-09 18:31 ` Bob Schlärmann
2007-04-09 19:56 ` Hans de Goede [this message]
2007-04-11 11:59 ` Jean Delvare
2007-04-11 19:02 ` Bob Schlärmann
2007-05-25 13:47 ` Jean Delvare
2007-05-25 14:58 ` Jean Delvare
2007-05-25 20:10 ` Hans de Goede
2007-05-28 15:05 ` Jean Delvare
2007-05-29  8:19 ` Hans de Goede
2007-05-29 17:01 ` 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=461A9EAE.3010601@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --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.