From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Finn Thain <fthain@telegraphics.com.au>,
stable@kernel.org
Subject: Re: [PATCH] macfb: Do not overflow fb_fix_screeninfo.id
Date: Mon, 27 Oct 2008 22:09:57 -0700 [thread overview]
Message-ID: <20081027220957.42cac1db.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0810270822540.15317@anakin>
On Mon, 27 Oct 2008 08:23:43 +0100 (CET) Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> From: Finn Thain <fthain@telegraphics.com.au>
>
> Don't overflow the 16-character fb_fix_screeninfo id string (fixes some
> console erasing and blanking artifacts). Have the ID default to "Unknown"
> on machines with no built-in video and no nubus devices. Check for
> fb_alloc_cmap failure.
The patch applies OK to 2.6.27, 2.6.26 and 2.6.25 (at least).
Should we backport it and if so, how far?
Thanks.
next prev parent reply other threads:[~2008-10-28 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 7:23 [PATCH] macfb: Do not overflow fb_fix_screeninfo.id Geert Uytterhoeven
2008-10-28 5:09 ` Andrew Morton [this message]
2008-10-28 8:58 ` Finn Thain
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=20081027220957.42cac1db.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-m68k@vger.kernel.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