The patch titled
uvesafb: don't treat valid modes returned byfb_find_mode() as errors
has been added to the -mm tree. Its filename is
uvesafb-dont-treat-valid-modes-returned-by-fb_find_mode-as-errors.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: uvesafb: don't treat valid modes returned byfb_find_mode() as errors
From: Michal Januszewski <spock@xxxxxxxxxx>
Don't treat valid modes returned by fb_find_mode() (best-fit modes,
default modes or the first valid mode) as errors.
Signed-off-by: Michal Januszewski <spock@xxxxxxxxxx>
Cc: "Antonino A. Daplas" <adaplas@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/video/uvesafb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/video/uvesafb.c~uvesafb-dont-treat-valid-modes-returned-by-fb_find_mode-as-errors drivers/video/uvesafb.c
--- a/drivers/video/uvesafb.c~uvesafb-dont-treat-valid-modes-returned-by-fb_find_mode-as-errors
+++ a/drivers/video/uvesafb.c
@@ -885,7 +885,7 @@ static int __devinit uvesafb_vbe_init_mo
}
/* fb_find_mode() failed */
- if (i == 0 || i >= 3) {
+ if (i == 0) {
info->var.xres = 640;
info->var.yres = 480;
mode = (struct fb_videomode *)
_
Patches currently in -mm which might be from spock@xxxxxxxxxx are
fbdev-make-the-best-fit-section-of-fb_find_mode-return-the-closest-matching-mode.patch
uvesafb-dont-treat-valid-modes-returned-by-fb_find_mode-as-errors.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
