All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
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:05 +0000	[thread overview]
Message-ID: <20030715174643.5702961e.khali@linux-fr.org> (raw)
In-Reply-To: <3EFCF67D.9040503@realitydiluted.com>


> 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.

2* It isn't clear what each of your patch does. I'd appreciate a list
that says which patch changes which files, and in which way.

We now have our own patch set for i2c-2.8.0 (we don't have any for
lm_sensors-2.8.0 yet though.) I'd like you to take a look at my page
that explains in detail what the patches do and why they are necessary.
In a way, I guess we made some common work, and trying to compare what
you and I did should be interesting:

    http://www.ensicaen.ismra.fr/~delvare/devel/i2c/

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

  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 [this message]
2005-05-19  6:24 ` Mark D. Studebaker 
2005-05-19  6:24 ` Jean Delvare
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=20030715174643.5702961e.khali@linux-fr.org \
    --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.