From: Dave Airlie <airlied@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.sourceforge.net, Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/5] clean up radeon_asic.h v2
Date: Mon, 15 Mar 2010 11:33:39 +1000 [thread overview]
Message-ID: <21d7e9971003141833l2d03bd7eub4d50211f6dcff7f@mail.gmail.com> (raw)
In-Reply-To: <20100312094833.GA3818@viiv.ffwll.ch>
On Fri, Mar 12, 2010 at 7:48 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Mar 12, 2010 at 10:25:56AM +0100, Jerome Glisse wrote:
>> I would merge patch 1 & 2 into a single patch,
> I've split this up to make patch-reading easier. And it's fully
> bisectable.
I quite like where this is going compared to what was there before,
so I've applied the work so far to drm-radeon-testing, its probably
2.6.35 material at this point anyways.
Dave.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
prev parent reply other threads:[~2010-03-15 1:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 21:19 [PATCH 0/5] clean up radeon_asic.h v2 Daniel Vetter
2010-03-11 21:19 ` [PATCH 1/5] drm/radeon: create radeon_asic.c Daniel Vetter
2010-03-11 21:19 ` [PATCH 2/5] drm/radeon: move asic structs to radeon_asic.c Daniel Vetter
2010-03-11 21:19 ` [PATCH 3/5] drm/radeon: unconfuse return value of radeon_asic->clear_surface_reg Daniel Vetter
2010-03-11 21:19 ` [PATCH 4/5] drm/radeon: include radeon_asic.h in the asic specific files Daniel Vetter
2010-03-11 21:19 ` [PATCH 5/5] drm/radeon: collect r100 asic related declarations in radeon_asic.h Daniel Vetter
2010-03-12 9:25 ` [PATCH 0/5] clean up radeon_asic.h v2 Jerome Glisse
2010-03-12 9:48 ` Daniel Vetter
2010-03-15 1:33 ` Dave Airlie [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=21d7e9971003141833l2d03bd7eub4d50211f6dcff7f@mail.gmail.com \
--to=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-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).