public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Simmons <jsimmons@transvirtual.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] new fbdev api.
Date: Thu, 4 Apr 2002 13:58:17 +0200	[thread overview]
Message-ID: <20020404135817.Q20040@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10204031224280.14670-100000@www.transvirtual.com> <Pine.GSO.4.21.0204040949550.28139-100000@vervain.sonytel.be>

On Thu, Apr 04, 2002 at 09:50:09AM +0200, Geert Uytterhoeven wrote:
 > > This will have a very important impact on linux embedded devices. It has
 > > been tested and has been in Dave Jones tree for some time. Geert with
 > > your blessing I like to have it added to Linus tree.
 > 
 > Please go ahead!

Indeed, the fb changes are the largest chunk of -dj right now.
The three heavy-weight patches pending integration by their maintainers
make up for half of whats left to be resynced..

(davej@noodles:resync)$ ll new-*
-rw-r--r--    1 davej    users      527576 Apr  1 21:48 new-console-layer.diff
-rw-r--r--    1 davej    users     2005697 Apr  1 03:12 new-fbdev.diff
-rw-r--r--    1 davej    users      396297 Apr  1 19:01 new-input-layer.diff


-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-04-04 11:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 20:30 [PATCH] new fbdev api James Simmons
2002-04-04  7:50 ` Geert Uytterhoeven
2002-04-04 11:58   ` Dave Jones [this message]
2002-04-04 19:04     ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2002-03-29 20:55 James Simmons

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=20020404135817.Q20040@suse.de \
    --to=davej@suse.de \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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