Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Jiří Moravec" <jim.lkml@gmail.com>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Typo in drivers/video/modedb.c
Date: Sat, 25 Oct 2008 18:16:42 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0810251816040.15317@anakin> (raw)
In-Reply-To: <49033AE4.3000502@gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1242 bytes --]

On Sat, 25 Oct 2008, Ji�~Yí Moravec wrote:
> When I viewed drivers/video/modedb.c, so I accidentally noticed a very old typo already contained in 2.6.0.
> This typo remained unheeded at least 5 years. Clear evidence of its importance.  ;) 

Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

> ---
> diff -Nupr a/drivers/video/modedb.c b/drivers/video/modedb.c
> --- a/drivers/video/modedb.c	2008-10-25 16:18:00.000000000 +0200
> +++ b/drivers/video/modedb.c	2008-10-25 16:18:10.000000000 +0200
> @@ -329,7 +329,7 @@ const struct fb_videomode vesa_modes[] =
>  	  FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
>  	  FB_VMODE_NONINTERLACED, FB_MODE_IS_VESA },
>  	/* 17 1152x864-75 VESA */
> -	{ NULL, 75, 1153, 864, 9259, 256, 64, 32, 1, 128, 3,
> +	{ NULL, 75, 1152, 864, 9259, 256, 64, 32, 1, 128, 3,
>  	  FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
>  	  FB_VMODE_NONINTERLACED, FB_MODE_IS_VESA },
>  	/* 18 1280x960-60 VESA */

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

           reply	other threads:[~2008-10-25 16:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <49033AE4.3000502@gmail.com>]

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=Pine.LNX.4.64.0810251816040.15317@anakin \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=jim.lkml@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox