From: mds@paradyne.com (Mark D. Studebaker )
To: lm-sensors@vger.kernel.org
Subject: CVS tests report
Date: Thu, 19 May 2005 06:23:58 +0000 [thread overview]
Message-ID: <3EE15EE4.9070500@paradyne.com> (raw)
In-Reply-To: <20030606183514.2e884183.khali@linux-fr.org>
That's definitely it.
i2c_register_entry() in lk2-4 doesn't kmalloc and copy the client's ctl_table_template.
So the sysctl table is all messed up.
The HEAD branch looks much closer to correct.
But the CVS log shows merges by Kyosti from 2.5 back to 2.4 so not quite sure
yet what went wrong.
I'll work on it tomorrow.
BTW when you rmmod i2c-proc right now, it doesn't completely remove
the sysctl table, and things really go bad.
I'm doing lots of diffs to figure out what to do next and hope to get things into shape tomorrow.
mds
Mark D. Studebaker wrote:
> Great catch on the eeprom problem.
> I duplicated it here.
> i2cdump returns the correct values.
> However all eeprom directories in /proc/sys/dev/sensors contain
> the same values (I have eeproms at 50,51,52 and all the values
> are from the chip at 52).
>
> I wonder if the problem is in i2c_register_entry() in i2c-proc.c.
> The function was rewritten between 2.7.0 and the branch, then
> rewritten again after the branch in the HEAD branch.
> I tried the i2c-proc from the HEAD branch but it oopsed
> in i2c_register_entry().
>
> I'll keep looking. Anybody with ideas speak up.
>
> Jean Delvare wrote:
>
>> Hi,
next prev parent reply other threads:[~2005-05-19 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 CVS tests report Jean Delvare
2005-05-19 6:23 ` Mark D. Studebaker
2005-05-19 6:23 ` Mark D. Studebaker [this message]
2005-05-19 6:23 ` Mark D. Studebaker
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Mark D. Studebaker
2005-05-19 6:23 ` Greg KH
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=3EE15EE4.9070500@paradyne.com \
--to=mds@paradyne.com \
--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.