From: Daniel Vetter <daniel@ffwll.ch>
To: "Reese, Armin C" <armin.c.reese@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: SNB/IVB sprite demo
Date: Sat, 11 Feb 2012 11:53:26 +0100 [thread overview]
Message-ID: <20120211105326.GC4531@phenom.ffwll.local> (raw)
In-Reply-To: <07EEC142D30DAC40BA4DD9C0F9EE51090B9FBC@FMSMSX102.amr.corp.intel.com>
Hi Armin,
On Sat, Feb 11, 2012 at 01:11:16AM +0000, Reese, Armin C wrote:
> Thanks for letting me know about the GCC warning messages. I did my
> final tweeks on the program in Android and compiled in that environment.
> The compiler there is a bit blind and the build jobs generate so much
> output, it's easy to ignore warnings.
Np. Btw I've just merged the Android build patches for i-g-t in case
that's useful for you.
> Anyway, I'll be more careful next time. The GCC compiler on my Ubuntu
> 11.04 system is version 4.5.2. I haven't installed 4.6.2 yet. GCC
> produced no warnings after the patch was applied. I attached both the
> patch and the new source code for sprite_on.c.
Thanks, patch looks nice. Can I have it as a git patch? That's much esier
to handle than your patch which contains funny paths into your own home
directory ;-)
/me is a lazy bastard
> Thanks for taking time for this. I intend on adding color key support
> into sprite_on.c to validate operation of that feature, so there will be
> more patches coming.
Awesome, but I that case if more stuff is to show up, I _really_ prefer
git patches.
Cheers, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-02-11 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 1:11 SNB/IVB sprite demo Reese, Armin C
2012-02-11 10:53 ` Daniel Vetter [this message]
2012-02-17 19:22 ` Reese, Armin C
2012-02-18 16:59 ` Paul Menzel
2012-02-22 10:00 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2012-02-08 2:16 Reese, Armin C
2012-02-08 15:50 ` Daniel Vetter
2012-02-08 18:14 ` Jesse Barnes
2012-02-10 17:48 ` Daniel Vetter
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=20120211105326.GC4531@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=armin.c.reese@intel.com \
--cc=intel-gfx@lists.freedesktop.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