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: <3EE22F3D.2070201@paradyne.com> (raw)
In-Reply-To: <20030606183514.2e884183.khali@linux-fr.org>
I think i2c-proc is fixed. Please test.
I've added several updates to the home page and the download page
in the last few days.
On the download page we already have a warning in bold that CVS is under
"active development" which is intended as a warning.
On your issue with matroxfb_maven unresolved symbols,
we unfortunately are no longer compatible with i2c modules in stock 2.4 kernels,
due to struct changes adding owner and removing inc_use and dec_use.
You definitely don't want i2c drivers from a 2.4 kernel compiled-in or
loaded as modules
Let's discuss what to do about this - some possiblilities:
We can back out the struct changes...
We can add big warnings to the release and work on submitting a 2.4 patch....
We can try and require a very recent 2.4 kernel...
We can include a patch to a recent 2.4 kernel to convert all i2c drivers...
We can include some compatibility code...
Would anybody like to work on a patch for 2.4 for submission to Marcelo?
Jean Delvare wrote:
>>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
>
>
> OK, thanks. Let me know if I can help (though I really have no knowledge
> about I2C and such).
>
> Maybe adding a news item saying I2C is known to be somewhat broken could
> be welcome? The latest related new item was added in March, readers
> could believe the situation has changed since.
>
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 ` Jean Delvare
2005-05-19 6:23 ` Mark D. Studebaker [this message]
2005-05-19 6:23 ` Mark D. Studebaker
2005-05-19 6:23 ` Mark D. Studebaker
2005-05-19 6:23 ` Greg KH
2005-05-19 6:23 ` Mark D. Studebaker
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=3EE22F3D.2070201@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.