From: mds@paradyne.com (Mark D. Studebaker )
To: lm-sensors@vger.kernel.org
Subject: i2c/sensors patch for 2.4.21 uploaded to my server....
Date: Thu, 19 May 2005 06:24:06 +0000 [thread overview]
Message-ID: <3F19F034.60203@paradyne.com> (raw)
In-Reply-To: <3EFCF67D.9040503@realitydiluted.com>
The rule is, "modules aren't supposed to change their own usage count"
so you shouldn't use MOD_xxx_USE_COUNT.
All the usage counts are changed in i2c-core now.
That's what caused all the struct changes.
Jean Delvare wrote:
>>I changed the name, but I also uploaded the corrected patches with the
>>2.4.21 prefix. All of the other 2.4.20 patches could be renamed with
>>the 2.4.21 prefix and new regeneration of the patches are unnecessary.
>
>
> It looks like the 2.4.21-i2c-sensors-patch.gz is older than the other
> patches. You forgot to upload the new one, didn't you?
>
>
>>I also downloaded the 2.8.0 stuff and tested it out on my dual Athlon
>>machine. I have uploaded the 2.8.0 patches for 2.4.21 to my ftp site
>>as well. There were two modules, scx200_acb.c and scx200_i2c.c that
>>did not compile. These patches have also been uploaded. The link again
>>is:
>>
>> ftp://ftp.realitydiluted.com/linux/i2c
>
>
> I've added this link to our download page. Some things would need to be
> clarified however:
>
> 1* I saw you added calls to MOD_INC_USE_COUNT and MOD_DEC_USE_COUNT in
> at least the SCx200 driver.Why that? The compatibility issue raised by
> this release was caused by the use of these. Mark D. Studebaker told me
> to get rid of them in all kernel drivers, what I did. So, what are we
> really supposed to do? Mark, I'd like to hear you on this.
>
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 i2c/sensors patch for 2.4.21 uploaded to my server Steven J. Hill
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Steven J. Hill
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker [this message]
2005-05-19 6:24 ` Steven J. Hill
2005-05-19 6:24 ` 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=3F19F034.60203@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.