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 patch for Linux 2.4.23-rc1 [Was: i2c oops]
Date: Thu, 19 May 2005 06:24:25 +0000	[thread overview]
Message-ID: <20031116145353.463076d4.khali@linux-fr.org> (raw)
In-Reply-To: <20031115212538.677d0fd2.khali@linux-fr.org>

> Thanks for the patch on the website.  However, I personally am more 
> interested in a patch for 2.4.23 (when it becomes available).

The fact that I made one available for 2.4.23-rc1 doesn't mean I won't
make one available for 2.4.23. I *will* support 2.4.23 as it becomes
available (probably not before a few weeks), and I should be able to be
rather quick since there probably won't be much changes compared with
-rc1.

> However, I do appreciate your time.  Have been able to successfully
> patch my kernel with the mkpatch.pl scripts from i2c and lm_sensors2. 
> Of course, I had to modify $diff_command in each script, but I was
> successful.  I compiled 2.4.23-rc1 with it and everything went fine. 
> I was really trying to do this just to make sure I could create one
> when 2.4.23 was released.
> 
> Do you think that this method should be sufficient for 2.4.23, or
> should I wait before I do it and use your unified patch?  I know that
> you put more into it than just simply running the mkpatch.pl scripts.

As said before, there probably won't be important changes between -rc1
and final (that's why it is called a release candidate). So what works
with -rc1 is likely to work the same with final.

That said, yes, my patches have more than just that. They have modified
Makefile and Config.in (I suspect that some drivers do not properly
appear in your configuration menu) and the required fixes for
non-sensors i2c drivers (mostly video devices such as the bttv/zoran and
similar drivers, matroxfb and some more. Read the installation guide for
a detailed list. If you don't use these drivers, than you don't need my
patch.

My patch also fixes a few incorectnesses here and there, that I
discovered while finding all the drivers that would need fixing.

I would really appreciate if you could take some time to test my patch
and make sure it's working OK for you.

> Anyway, thanks again!

You're welcome.

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

  parent reply	other threads:[~2005-05-19  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 I2C patch for Linux 2.4.23-rc1 [Was: i2c oops] Jean Delvare
2005-05-19  6:24 ` Troy Henderson
2005-05-19  6:24 ` Jean Delvare [this message]
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=20031116145353.463076d4.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.