From: Thomas Winischhofer <twini@xfree86.org>
To: kronos@kronoz.cjb.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
James Simmons <jsimmons@infradead.org>
Subject: Re: [PATCH] sisfb: New framebuffer_alloc API and class_dev changes
Date: Tue, 16 Sep 2003 01:18:25 +0200 [thread overview]
Message-ID: <3F6648C1.9010500@xfree86.org> (raw)
In-Reply-To: <20030915204703.GB23294@dreamland.darkstar.lan>
Erm, after reading the list archives I think I'll wait a while before
merging this. Seems not everyone agrees on the direction this is
currently taking.
Thomas
Kronos wrote:
> Hi,
> this patch converts driver/video/sis to framebuffer_alloc:
--
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net http://www.winischhofer.net/
twini AT xfree86 DOT org
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-09-15 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 20:47 [PATCH] sisfb: New framebuffer_alloc API and class_dev changes Kronos
2003-09-15 23:12 ` Thomas Winischhofer
2003-09-16 13:42 ` Kronos
2003-09-15 23:18 ` Thomas Winischhofer [this message]
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=3F6648C1.9010500@xfree86.org \
--to=twini@xfree86.org \
--cc=jsimmons@infradead.org \
--cc=kronos@kronoz.cjb.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).