public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jean Delvare" <khali@linux-fr.org>
To: rbultje@ronald.bitfreak.net
Cc: "Chris Wright" <chrisw@osdl.org>,
	"Randy.Dunlap" <rddunlap@osdl.org>,
	"Daniel Staaf" <dst@bostream.nu>,
	"LKML" <linux-kernel@vger.kernel.org>,
	"Andrei Mikhailovsky" <andrei@arhont.com>,
	"Ian Campbell" <icampbell@arcom.com>,
	"Gerd Knorr" <kraxel@bytesex.org>,
	stable@kernel.org
Subject: Re: [PATCH 2.6] Fix i2c messsage flags in video drivers
Date: Thu, 10 Mar 2005 12:50:08 +0100 (CET)	[thread overview]
Message-ID: <cvxT6YRf.1110455408.1808270.khali@localhost> (raw)
In-Reply-To: <Pine.LNX.4.56.0503100141390.22284@www.ithos.nl>


Hi Ronald,

> I indeed don't test RC/MM kernels. I'm fairly happy with the current
> driver status, so I'm not doing any active new development on it. I run
> standard Fedora kernels with CVS of the driver (which is the same as
> what's in 2.6.10).
> (...)
> My experience is not the same as yours, it seems... I cannot explain why,
> unfortunately. (...)

I can. You are using a 2.6.10 kernel at best (that's what FC3 updates
have), and the bug is triggered by changes made to the i2c-algo-bit
driver somewhere between 2.6.10 and 2.6.11. So it's not surprising that
you don't see any problem. Note that the version of the media/video
drivers you use is not relevant here. The bug has been there for over a
year, but the code path where it lies was never taken until i2c-algo-bit
was updated recently. What matters is the version of i2c-algo-bit.

So as long as you don't move to a 2.6.11 kernel, don't even bother
trying my patches, because you will never hit the code that I am trying
to fix.

Thanks,
--
Jean Delvare

  reply	other threads:[~2005-03-10 11:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05 12:11 amd64 2.6.11 oops on modprobe Andrei Mikhailovsky
2005-03-06  0:53 ` Randy.Dunlap
2005-03-06 13:33   ` Andrei Mikhailovsky
2005-03-07  3:52     ` Randy.Dunlap
2005-03-07  5:01     ` Randy.Dunlap
2005-03-07 21:47     ` Randy.Dunlap
2005-03-08 19:15       ` Jean Delvare
2005-03-08 19:25         ` [PATCH 2.6] Fix i2c messsage flags in video drivers Jean Delvare
2005-03-09 18:40           ` Chris Wright
2005-03-09 21:55             ` Jean Delvare
2005-03-09 22:40               ` Ronald S. Bultje
2005-03-10 10:56                 ` Jean Delvare
2005-03-10  0:47                   ` Ronald S. Bultje
2005-03-10 11:50                     ` Jean Delvare [this message]
2005-03-10  1:33                       ` Ronald S. Bultje
2005-03-09 23:28               ` Chris Wright
2005-03-21 22:47 ` amd64 2.6.11 oops on modprobe Andrew Morton
2005-05-25 22:24 ` Andrew Morton

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=cvxT6YRf.1110455408.1808270.khali@localhost \
    --to=khali@linux-fr.org \
    --cc=andrei@arhont.com \
    --cc=chrisw@osdl.org \
    --cc=dst@bostream.nu \
    --cc=icampbell@arcom.com \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbultje@ronald.bitfreak.net \
    --cc=rddunlap@osdl.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox