From: Otto Wyss <otto.wyss@orpatec.ch>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: 'linux-kernel' <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Framebuffer drivers maintainers
Date: Sat, 21 Aug 2004 11:05:26 +0200 [thread overview]
Message-ID: <41271057.B3461220@orpatec.ch> (raw)
In-Reply-To: 41270AD0.FE6C7970@orpatec.ch
Otto Wyss wrote:
>
Sorry, forgot to add the link "http://linux-fbdev.sourceforge.net/index.php?page=driverlist.php".
O. Wyss
--
See a huge pile of work at "http://wyodesktop.sourceforge.net/"
next prev parent reply other threads:[~2004-08-21 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 8:41 Framebuffer drivers maintainers Otto Wyss
2004-08-21 9:05 ` Otto Wyss [this message]
2004-08-21 9:24 ` Romain Dolbeau
2004-08-21 13:20 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-08-22 17:28 ` Alexander Kern
2004-08-28 4:39 ` David Eger
2004-08-28 13:48 ` Otto Wyss
2004-08-28 15:05 ` David Eger
2004-08-28 15:22 ` Otto Wyss
2004-09-06 4:14 ` David Eger
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=41271057.B3461220@orpatec.ch \
--to=otto.wyss@orpatec.ch \
--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 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).