linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jan Blunck <jblunck@infradead.org>
Cc: linux-omap@vger.kernel.org, Sergio Aguirre <saaguirre@ti.com>,
	Imre Deak <imre.deak@nokia.com>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [APPLIED] [PATCH] omapfb: Reorder Register_framebuffer call
Date: Tue, 22 Sep 2009 09:28:54 -0700	[thread overview]
Message-ID: <20090922162853.GC14890@atomide.com> (raw)
In-Reply-To: <4de7f8a60909220759g63b592eek85a2bca04b264d2e@mail.gmail.com>

* Jan Blunck <jblunck@infradead.org> [090922 07:59]:
> On Tue, Sep 22, 2009 at 3:31 AM, Tony Lindgren <tony@atomide.com> wrote:
> > This patch has been applied to the linux-omap
> > by youw fwiendly patch wobot.
> >
> > Branch in linux-omap: omap-fixes
> >
> > Initial commit ID (Likely to change): 9aef1066fb5ca8506068eaab1c552ecca4c85475
> >
> > PatchWorks
> > http://patchwork.kernel.org/patch/47089/
> >
> 

Added back the original Cc's that were dropped from the linux-omap
commit message.

> Is it actually safe to do this? The framebuffer can be used directly
> after it is registered. In this case it would mean it is used before
> it is even fully initialized (set_fb_var(), set_fb_fix(), ... are
> being called).

Good point, dropping the patch.

Also, let's let Tomi Valkeinen deal with queueing up the omap fb code.
I can then merge Tomi's branck into linux-omap master branch as needed.

Regards,

Tony

  parent reply	other threads:[~2009-09-22 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-12 16:34 [PATCH] omapfb: Reorder Register_framebuffer call Sergio Aguirre
2009-09-14 14:43 ` Aguirre Rodriguez, Sergio Alberto
2009-09-14 15:22   ` Felipe Contreras
     [not found] ` <notify-1253583118@atomide.com>
     [not found]   ` <4de7f8a60909220759g63b592eek85a2bca04b264d2e@mail.gmail.com>
2009-09-22 16:28     ` Tony Lindgren [this message]
2009-09-22 16:57       ` [APPLIED] " Aguirre Rodriguez, Sergio Alberto
2009-09-23 17:03         ` Jan Blunck
2009-09-25 10:13           ` [Linux-fbdev-devel] " Florian Tobias Schandinat

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=20090922162853.GC14890@atomide.com \
    --to=tony@atomide.com \
    --cc=imre.deak@nokia.com \
    --cc=jblunck@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=saaguirre@ti.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;
as well as URLs for NNTP newsgroup(s).