From: Felipe Contreras <felipe.contreras@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Trilok Soni <soni.trilok@gmail.com>,
linux-fbdev-devel@lists.sourceforge.net,
linux-omap@vger.kernel.org, felipe.contreras@nokia.com,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] omapfb: Fix argument of blank operation.
Date: Thu, 12 Mar 2009 00:43:18 +0200 [thread overview]
Message-ID: <94a0d4530903111543y4745ade0ofac867ef43e7ab1b@mail.gmail.com> (raw)
In-Reply-To: <20090311152000.8a3db19c.akpm@linux-foundation.org>
On Thu, Mar 12, 2009 at 12:20 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Wed, 11 Mar 2009 22:47:41 +0530
> Trilok Soni <soni.trilok@gmail.com> wrote:
>
>> Hi Felipe,
>>
>> On Fri, Dec 5, 2008 at 4:15 AM, Felipe Contreras
>
> I bet he thought we'd forgotten.
You bet correctly :)
>> <felipe.contreras@gmail.com> wrote:
>> > From: Felipe Contreras <felipe.contreras@nokia.com>
>> >
>> > The blank operation should receive FB_BLANK_POWERDOWN, not
>> > VESA_POWERDOWN.
>> >
>>
>> Thanks. Looks good.
>>
>> Signed-off-by: Trilok Soni <soni.trilok@gmail.com>
>>
>
> Unfortunately the changelog didn't give me any hint as to the
> seriousness of the problem which was fixed. So I queued it for 2.6.30,
> perhaps inappropriately.
I noticed because of another bug in omapfb which required blanking in
order to actually see something (PM stuff?). If user-space tries to
blank the usual way, it wouldn't work.
My guess is that it's not a big issue, in part because nobody has
noticed, but perhaps I'm wrong. I was hoping the fbdev guys would know
better.
--
Felipe Contreras
prev parent reply other threads:[~2009-03-11 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1228430755-4221-1-git-send-email-felipe.contreras@gmail.com>
2009-03-11 17:17 ` Trilok Soni
2009-03-11 22:20 ` Andrew Morton
2009-03-11 22:43 ` Felipe Contreras [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=94a0d4530903111543y4745ade0ofac867ef43e7ab1b@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=felipe.contreras@nokia.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=soni.trilok@gmail.com \
/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
all inboxes | Powered by JetHome®