From: Chris Wright <chrisw@osdl.org>
To: Jean Delvare <khali@linux-fr.org>
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>,
Ronald Bultje <rbultje@ronald.bitfreak.net>,
Gerd Knorr <kraxel@bytesex.org>,
stable@kernel.org
Subject: Re: [PATCH 2.6] Fix i2c messsage flags in video drivers
Date: Wed, 9 Mar 2005 15:28:25 -0800 [thread overview]
Message-ID: <20050309232825.GH5389@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050309225559.061058dd.khali@linux-fr.org>
* Jean Delvare (khali@linux-fr.org) wrote:
> >
> > Are people reporting this as a problem?
>
> Not that I know. For adv7175 it couldn't be reported so far anyway
> because people would hit the oops in saa7110 before (same board: DC10+,
> oops fixed in a different patch).
Heh, right.
> It is possible that people are able to get their board to still work
> without my patch, if the chips were properly configured in the first
> place and they don't attempt to reconfigure them (like norm change). I
> don't know the chips well enough to tell how probable this is.
According to offlist mail, it does "fix a bug that bothers people."
So looks like a fine candidate, and is queued up for -stable.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-03-09 23:29 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
2005-03-10 1:33 ` Ronald S. Bultje
2005-03-09 23:28 ` Chris Wright [this message]
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=20050309232825.GH5389@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=andrei@arhont.com \
--cc=dst@bostream.nu \
--cc=icampbell@arcom.com \
--cc=khali@linux-fr.org \
--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