From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Guido Guenther <agx@sigxcpu.org>
Cc: linux-fbdev-devel@lists.sf.net
Subject: Re: [PATCH]: rivafb, use framebuffer_alloc
Date: Mon, 27 Sep 2004 08:10:40 +0800 [thread overview]
Message-ID: <200409270810.40336.adaplas@hotpop.com> (raw)
In-Reply-To: <20040926092750.GA3936@bogon.ms20.nix>
On Sunday 26 September 2004 17:27, Guido Guenther wrote:
> Hi,
> attached patch against 2.6.9-rc2 converts rivafb to use
> framebuffer_alloc and tries to be more specific about the errors that
> occure during init. Please apply.
rivafb in Andrew's tree is already converted to framebuffer_alloc/release.
Tony
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
prev parent reply other threads:[~2004-09-27 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 9:27 [PATCH]: rivafb, use framebuffer_alloc Guido Guenther
2004-09-27 0:10 ` Antonino A. Daplas [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=200409270810.40336.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=agx@sigxcpu.org \
--cc=linux-fbdev-devel@lists.sf.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).