From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-fbdev-devel@lists.sourceforge.net, ioe-lkml@rameria.de,
linux-kernel@vger.kernel.org, davem@davemloft.net,
benh@kernel.crashing.org, linux-kernel@hansmi.ch
Subject: Re: [PATCH] fbdev: Fix usage of blank value passed to fb_blank
Date: Sun, 29 Jan 2006 18:40:06 +0800 [thread overview]
Message-ID: <43DC9B86.2000200@gmail.com> (raw)
In-Reply-To: <20060129001832.4fe6fd7f.akpm@osdl.org>
Andrew Morton wrote:
> "Antonino A. Daplas" <adaplas@gmail.com> wrote:
>> Unfortunately, this may cause some userland breakage. X should work.
>> However, some apps may have been developed that uses the FB_BLANK constants
>> (DirectFB?). In these cases, they'll get a deeper blank level instead, so it
>> probably won't affect them significantly. A follow up patch that hides the
>> FB_BLANK constants may be worthwhile.
>
> Would prefer to avoid any userland breakage. Is this followup patch
> happening?
I'm still doing research on which major fb apps depend on the FB_BLANK constants, but
my guess is that the follow up patch is inevitable. We cannot avoid bending over
backwards for X :(
Tony
next prev parent reply other threads:[~2006-01-29 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 23:13 [PATCH] framebuffer: Remove old radeon driver Michael Hanselmann
2006-01-28 4:09 ` Benjamin Herrenschmidt
2006-01-28 4:46 ` David S. Miller
2006-01-28 5:59 ` Antonino A. Daplas
2006-01-28 20:06 ` Ingo Oeser
2006-01-29 2:18 ` [PATCH] fbdev: Fix usage of blank value passed to fb_blank Antonino A. Daplas
2006-01-29 8:18 ` Andrew Morton
2006-01-29 10:40 ` Antonino A. Daplas [this message]
2006-01-29 14:42 ` [Linux-fbdev-devel] " Ville Syrjälä
2006-01-29 22:19 ` Antonino A. Daplas
2006-01-29 23:34 ` Antonino A. Daplas
2006-01-30 10:22 ` Geert Uytterhoeven
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=43DC9B86.2000200@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=ioe-lkml@rameria.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@hansmi.ch \
--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