public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PREVIEW 2] New display subsystem for OMAP2/3
Date: Tue, 23 Sep 2008 11:19:45 +0300	[thread overview]
Message-ID: <1222157985.8299.38.camel@tubuntu> (raw)
In-Reply-To: <20080922151045.GC8171@atomide.com>

Hi,

On Mon, 2008-09-22 at 18:10 +0300, ext Tony Lindgren wrote:
> Hi,
> 
> * Tomi Valkeinen <tomi.valkeinen@nokia.com> [080922 17:49]:
> > Hi,
> > 
> > I sent a preview of a new display subsystem for OMAP2/3 some time ago:
> > http://marc.info/?l=linux-omap&m=122114505030542&w=2
> > 
> > I now have updated it, the patches are at the same place:
> > http://www.bat.org/~tomba/omap-dss/
> 
> This discussion should go to linux-fbdev-devel list. Please keep l-o
> list Cc'd though. Also you should post the patches as a proper inline
> series, please see git-send-email man page.
> 

Ok, I'll move it to linux-fbdev-devel.

I didn't post the patches inline, as they are quite big (250k+). I
thought there was a "rule" to put big patches to some public place, not
to mail them.

What is the proper procedure for this work? Discuss and review the
patches on fbdevel, and mail to l-o when finalized? Or go directly to
Linus' tree?

 Tomi



  reply	other threads:[~2008-09-23  8:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 14:48 [PREVIEW 2] New display subsystem for OMAP2/3 Tomi Valkeinen
2008-09-22 15:10 ` Tony Lindgren
2008-09-23  8:19   ` Tomi Valkeinen [this message]
2008-09-23  8:41     ` Koen Kooi
2008-09-23  9:24       ` Tony Lindgren
2008-09-23 10:27         ` Koen Kooi
2008-09-23 10:40           ` Tony Lindgren
2008-09-23 11:08             ` Hiremath, Vaibhav

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=1222157985.8299.38.camel@tubuntu \
    --to=tomi.valkeinen@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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