From: "David S. Miller" <davem@redhat.com>
To: kronos@kronoz.cjb.net
Cc: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org
Subject: Re: [PATCH] cg*: New framebuffer_alloc API and class_dev changes
Date: Mon, 15 Sep 2003 16:27:05 -0700 [thread overview]
Message-ID: <20030915162705.24913719.davem@redhat.com> (raw)
In-Reply-To: <20030915194259.GG16370@dreamland.darkstar.lan>
On Mon, 15 Sep 2003 21:42:59 +0200
Kronos <kronos@kronoz.cjb.net> wrote:
> this patch converts driver/video/cg*.c to framebuffer_alloc:
This patch also does not apply cleanly to current 2.6.x sources.
Are these patches against some special set of framebuffer changes
that are not in 2.6.x yet?
If so, could you _PLEASE_ indicate this when you send patches
directly to me? When I see a patch that I'm sent directly, I
expect that this means I should apply it to my tree and that the
patch works with current vanilla sources.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-15 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 19:42 [PATCH] cg*: New framebuffer_alloc API and class_dev changes Kronos
2003-09-15 23:27 ` David S. Miller [this message]
2003-09-16 13:46 ` Kronos
2003-09-17 1:21 ` David S. Miller
2003-09-17 16:37 ` Kronos
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=20030915162705.24913719.davem@redhat.com \
--to=davem@redhat.com \
--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).