From: Damien Lespiau <damien.lespiau@intel.com>
To: Kenneth Graunke <kenneth@whitecape.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: A few clean-ups and a baby step towards unified register definitions
Date: Tue, 7 Jan 2014 16:49:28 +0000 [thread overview]
Message-ID: <20140107164928.GG21071@strange.amr.corp.intel.com> (raw)
In-Reply-To: <52CB4D47.8030903@whitecape.org>
On Mon, Jan 06, 2014 at 04:41:43PM -0800, Kenneth Graunke wrote:
> On 01/06/2014 07:02 AM, Damien Lespiau wrote:
> > Having one source for registers defines sounds like a good idea. These patches,
> > written long ago, were a baby step towards that goal by cleaning-up the
> > INSTDONE definitons to be like the kernel ones.
> >
> > Along the way, I removed one tool that isn't even compiled and another unusued
> > one.
> >
>
> Series is:
> Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
Thanks for the review, pushed.
--
Damien
prev parent reply other threads:[~2014-01-07 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 15:02 A few clean-ups and a baby step towards unified register definitions Damien Lespiau
2014-01-06 15:02 ` [PATCH igt 1/6] intel_reg: Renamed INST_DONE to INSTDONE Damien Lespiau
2014-01-06 15:02 ` [PATCH igt 2/6] instdone: Add an assert to make sure we never overflow instdone_bits Damien Lespiau
2014-01-06 15:02 ` [PATCH igt 3/6] lib: Move the INSTDONE bit definitions to instdone.c Damien Lespiau
2014-01-06 15:02 ` [PATCH igt 4/6] lib: Use INSTDONE_I965 and INSTDONE_1 for gen6 Damien Lespiau
2014-01-06 15:02 ` [PATCH igt 5/6] tools: Removed unused tools/intel_iosf_read.c Damien Lespiau
2014-01-06 15:02 ` [PATCH igt 6/6] tools: Remove intel_disable_clock_gating Damien Lespiau
2014-01-07 0:41 ` A few clean-ups and a baby step towards unified register definitions Kenneth Graunke
2014-01-07 16:49 ` Damien Lespiau [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=20140107164928.GG21071@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kenneth@whitecape.org \
/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