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] Hacking on libsensors
Date: Wed, 27 Jun 2007 19:02:44 +0000	[thread overview]
Message-ID: <20070627210244.3da5a09a@hyperion.delvare> (raw)
In-Reply-To: <20070626142055.079a4d89@hyperion.delvare>

Hi Hans,

On Wed, 27 Jun 2007 17:19:56 +0200, Hans de Goede wrote:
> Jean Delvare wrote:
> > Hi all,
> > 
> > My employer, Novell, has organized a "hack week". This is one week where
> > every employee is free to hack on whatever he/she wants [1].
> > Unsurprisingly I decided I would spend that time on libsensors. I
> > posted the idea here:
> > http://idea.opensuse.org/content/ideas/generic-sensors-library
> 
> It sounds like an excellent plan to start working on the 3.0 branch! Let me 
> know if you need any help, and/or when you want me to test this on the machines 
> I have access too.

I'll let you know. However, I fear that I've been spending too much
time on the cleanup steps. 3 days have passed already, only 2 left, and
I still didn't have a look at the libsensors interface. Not to say that
the work I've done wasn't needed, it certainly was, but I don't think
there will be much to test at the end of this week. I'll have to find
more time to keep working on it in the next few weeks.

> Some time ago we had a discussion about amongst other things some bad 
> assumptions in the generic voltage printing code. I promised to fix this, but 
> its still on my todo, I will happily fix this once things stabilize (I would 
> like to avoid svn commit conflicts), if you feel inclined to fix it yourself 
> thats fine too, here is the important part of our previous conversation on this:
> 
>  > Also print_generic_chip_in(), has some dangerous and unneeded assumptions, for
>  > example:
>  > -it assumes that if there is a inX_max that there will also always be a inX_min
>  > -it assumes that if there is no inX_max there will also be no alarms
>  >
> Somewhat less "unneeded" assumption
>  > -it doesn't check for inX_max_alarm without an inX_min_alarm and visa versa, I
>  >   admit this would be a driver bug, as then the driver should have just a
>  >   inX_alarm, but still we might want to concider this.

Please commit your changes as soon as possible. Don't worry about
conflicts, I won't touch this part of the code before you've committed
your own changes.

Thanks,
-- 
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-06-27 19:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26 12:20 [lm-sensors] Hacking on libsensors Jean Delvare
2007-06-27 15:19 ` Hans de Goede
2007-06-27 19:02 ` Jean Delvare [this message]
2007-06-28 21:04 ` Jean Delvare
2007-06-28 21:17 ` Hans de Goede
2007-06-30 15:35 ` 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=20070627210244.3da5a09a@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.