From: Joerg Sommrey <jo@sommrey.de>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH] bad temperature values from w83781d in
Date: Thu, 09 Aug 2007 16:41:52 +0000 [thread overview]
Message-ID: <20070809164152.GA28404@sommrey.de> (raw)
In-Reply-To: <20070809122619.GF3584@jupiter.solarsys.private>
Hi Mark,
On Thu, Aug 09, 2007 at 08:26:19AM -0400, Mark M. Hoffman wrote:
> Hi Joerg:
>
> > On Wed, Aug 08, 2007 at 11:56:42PM -0400, Mark M. Hoffman wrote:
> > > Thanks for sending all that. I see one bug clearly, and I'm pretty close to
> > > seeing the other one. But for tonight, I need sleep.
>
> There's just one bug after all. The second was a figment of my sleep-deprived
> imagination.
>
[...]
>
> My bad, there's a second i2cset command that would have done it. Please try
> this patch against v2.6.22.
>
Great, problem fixed. Thanks a lot for your prompt solution!
-jo
--
-rw-r--r-- 1 jo users 62 2007-08-09 08:46 /home/jo/.signature
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Sommrey <jo@sommrey.de>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [PATCH] bad temperature values from w83781d in 2.6.22
Date: Thu, 9 Aug 2007 18:41:52 +0200 [thread overview]
Message-ID: <20070809164152.GA28404@sommrey.de> (raw)
In-Reply-To: <20070809122619.GF3584@jupiter.solarsys.private>
Hi Mark,
On Thu, Aug 09, 2007 at 08:26:19AM -0400, Mark M. Hoffman wrote:
> Hi Joerg:
>
> > On Wed, Aug 08, 2007 at 11:56:42PM -0400, Mark M. Hoffman wrote:
> > > Thanks for sending all that. I see one bug clearly, and I'm pretty close to
> > > seeing the other one. But for tonight, I need sleep.
>
> There's just one bug after all. The second was a figment of my sleep-deprived
> imagination.
>
[...]
>
> My bad, there's a second i2cset command that would have done it. Please try
> this patch against v2.6.22.
>
Great, problem fixed. Thanks a lot for your prompt solution!
-jo
--
-rw-r--r-- 1 jo users 62 2007-08-09 08:46 /home/jo/.signature
next prev parent reply other threads:[~2007-08-09 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070805183219.0d54802b.akpm@linux-foundation.org>
2007-08-05 10:26 ` bad temperature values from w83781d in 2.6.22 Joerg Sommrey
2007-08-05 11:20 ` Rene Herman
2007-08-05 16:27 ` Joerg Sommrey
2007-08-08 1:03 ` [lm-sensors] " Mark M. Hoffman
2007-08-08 1:03 ` Mark M. Hoffman
2007-08-08 15:17 ` [lm-sensors] " Joerg Sommrey
2007-08-08 15:17 ` Joerg Sommrey
2007-08-09 3:56 ` [lm-sensors] " Mark M. Hoffman
2007-08-09 3:56 ` Mark M. Hoffman
2007-08-09 7:09 ` Joerg Sommrey
2007-08-09 7:09 ` Joerg Sommrey
2007-08-09 12:26 ` [lm-sensors] [PATCH] " Mark M. Hoffman
2007-08-09 12:26 ` Mark M. Hoffman
2007-08-09 16:41 ` Joerg Sommrey [this message]
2007-08-09 16:41 ` Joerg Sommrey
2007-08-12 18:18 ` [lm-sensors] [PATCH] bad temperature values from w83781d in Jean Delvare
2007-08-12 18:18 ` [PATCH] bad temperature values from w83781d in 2.6.22 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=20070809164152.GA28404@sommrey.de \
--to=jo@sommrey.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
/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.