From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: random <eger@theboonies.us>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Radeon 2D Acceleration for 2.6
Date: Wed, 21 Jan 2004 09:47:56 +1100 [thread overview]
Message-ID: <1074638876.793.47.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.50L0.0401201543490.1525-200000@rosencrantz.pok.ibm.com>
Can you re-export the cset as a patch in unified diff form please ?
(bk export -tpatch -du)
Ben.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-20 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 14:44 [PATCH] Radeon 2D Acceleration for 2.6 random
2004-01-20 21:40 ` Benjamin Herrenschmidt
2004-01-20 22:47 ` Benjamin Herrenschmidt [this message]
2004-01-20 23:09 ` random
2004-01-21 11:10 ` Benjamin Herrenschmidt
2004-01-23 1:22 ` Michel Dänzer
2004-01-23 2:19 ` Benjamin Herrenschmidt
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=1074638876.793.47.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=eger@theboonies.us \
--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).