All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, JosephChan@via.com.tw,
	ScottFang@viatech.com.cn
Subject: Re: [PATCH v2] viafb: 2D engine rewrite (and viafb patches in general)
Date: Sat, 5 Sep 2009 16:01:40 -0700	[thread overview]
Message-ID: <20090905160140.7b36527f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090905161645.74a49a84@bike.lwn.net>

On Sat, 5 Sep 2009 16:16:45 -0600 Jonathan Corbet <corbet@lwn.net> wrote:

> On Fri,  4 Sep 2009 20:43:52 +0000
> Florian Tobias Schandinat <FlorianSchandinat@gmx.de> wrote:
> 
> > This patch is a completly rewritten 2D engine. The engine is no longer
> > in a default state but reinitialized every time to allow usage for both
> > framebuffers regardless of their settings.
> > The whole engine handling is concentrated in a big function which takes
> > 16 parameters.
> 
> Ouch, that's a lot of parameters.  Might it be better to create a
> structure to encapsulate all of those drawing parameters?

I was wondering that.  There's less advantage to that than usual
because the call graph is not at all deep.

> On a more general level: is anybody maintaining a tree for patches to
> the viafb driver?

-mm.

>  I'm going to be doing some work here (writing a
> driver for the video capture engine), and there's patches sitting in
> Harald's tree and the OLPC tree.

As far as the rest of the world is concerned, that stuff doesn't exist.

>  It seems like a central merge point
> might be a nice thing to have.
> 
> I'd be happy to run such a tree.  I'm really *not* qualified to be
> passing judgment on patches to the framebuffer driver at this point,
> though, so I'm not sure that I'm the best person for the job.

Send 'em over.  I haven't heard anything from the original viafb
submitters for a long time.  Hopefully Florian has time to help out
with some review-n-test.

  reply	other threads:[~2009-09-05 23:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 21:07 [PATCH] viafb: 2D engine rewrite Florian Tobias Schandinat
2009-09-04 20:43 ` [PATCH v2] " Florian Tobias Schandinat
2009-09-05 22:16   ` [PATCH v2] viafb: 2D engine rewrite (and viafb patches in general) Jonathan Corbet
2009-09-05 22:16     ` Jonathan Corbet
2009-09-05 23:01     ` Andrew Morton [this message]
2009-09-06  0:38       ` Florian Tobias Schandinat
2009-09-06  0:38         ` [Linux-fbdev-devel] " Florian Tobias Schandinat
2009-09-06  3:02         ` Andrew Morton
2009-09-06 13:40         ` Jonathan Corbet
2009-09-07  2:51           ` 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=20090905160140.7b36527f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=FlorianSchandinat@gmx.de \
    --cc=JosephChan@via.com.tw \
    --cc=ScottFang@viatech.com.cn \
    --cc=corbet@lwn.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.