From: Jean Delvare <khali@linux-fr.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: vandrove@vc.cvut.cz, linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, adaplas@gmail.com
Subject: Re: [PATCH 0/3] matroxfb fixes and improvements
Date: Sat, 9 Aug 2008 10:57:56 +0200 [thread overview]
Message-ID: <20080809105756.633b3658@hyperion.delvare> (raw)
In-Reply-To: <20080808140019.32d949f7.akpm@linux-foundation.org>
Hi Andrew,
On Fri, 8 Aug 2008 14:00:19 -0700, Andrew Morton wrote:
> On Fri, 8 Aug 2008 16:49:37 +0200
> Jean Delvare <khali@linux-fr.org> wrote:
>
> > Not having heard of Petr in one month and a half, I am sending these 3
> > patches again. Patch 1/3 (matrox maven: Fix a broken error path) in
> > particular should be applied ASAP. Patch 2/3 (matroxfb: i2c structure
> > templates clean-up) would be good to have as well and I tested it.
> > Patch 3/3 (matrox maven: Convert to a new-style i2c driver) needs
> > testing before it can go upstream. I can't test it myself, but it has
> > been in linux-next for 6 weeks or so.
>
> I'll put all three into 2.6.27.
Thank you.
> I suspect that #1 should be backported to 2.6.25.x and to 2.6.26.x but
> I am unsure about that due to its poor changelogging.
>
> I _think_ that the machine will crash if the i2c_attach_client() or
> maven_init_client() calls fail. But I don't know under what
> circumstances that can happen, nor whether the bug has been reported in
> the field, etc.
I found it while working on patch #3. I am not aware of it having been
reported in the field. The maven driver doesn't have that many users
(which is why I am struggling to get patch #3 tested.) And then the
errors in question are unlikely to happen. In fact, maven_init_client()
always returns 0, it simply cannot fail. So I'd say that the chances
that someone hits that bug are thin.
That would mean that we don't really need to backport the fix. But OTOH
it's a regression and the fix is pretty easy and not intrusive. So, I
think I would still backport it.
> And the -stable people also will be interested in such information when
> making their decisions.
I think I will let them decide.
--
Jean Delvare
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
prev parent reply other threads:[~2008-08-09 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 14:49 [PATCH 0/3] matroxfb fixes and improvements Jean Delvare
2008-08-08 14:58 ` [PATCH 1/3] matrox maven: Fix a broken error path Jean Delvare
2008-08-08 16:35 ` Krzysztof Helt
2008-08-08 15:02 ` [PATCH 2/3] matroxfb: i2c structure templates clean-up Jean Delvare
2008-08-08 16:36 ` Krzysztof Helt
2008-08-08 15:05 ` [PATCH 3/3] matrox maven: Convert to a new-style i2c driver Jean Delvare
2008-08-08 16:42 ` Krzysztof Helt
2008-08-08 21:00 ` [PATCH 0/3] matroxfb fixes and improvements Andrew Morton
2008-08-09 8:57 ` Jean Delvare [this message]
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=20080809105756.633b3658@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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;
as well as URLs for NNTP newsgroup(s).