From: Damien Lespiau <damien.lespiau@intel.com>
To: "Barbalho, Rafael" <rafael.barbalho@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] Fix LIBDRM_PATH for top android build
Date: Fri, 31 Jan 2014 10:20:16 +0000 [thread overview]
Message-ID: <20140131102016.GA29924@strange.amr.corp.intel.com> (raw)
In-Reply-To: <4B498744C37F034EA16F6FBC6AB9FAD20145A56B@IRSMSX103.ger.corp.intel.com>
On Fri, Jan 31, 2014 at 09:36:25AM +0000, Barbalho, Rafael wrote:
> The patch is incomplete. If you change these macros in the tests
> directory then why does it not need to be changed in the tools
> directory also?
>
> I have a patch that refactors these macros into a third file, I'll
> send it up for review later once I fix another issue I have in the
> patch series.
Holding the horses then!
--
Damien
next prev parent reply other threads:[~2014-01-31 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 18:29 [PATCH] Fix LIBDRM_PATH for top android build joao.santos
2014-01-28 13:30 ` Damien Lespiau
2014-01-31 9:02 ` Mateo Lozano, Oscar
2014-01-31 9:36 ` Barbalho, Rafael
2014-01-31 10:20 ` Damien Lespiau [this message]
2014-02-07 14:39 ` Santos, Joao
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=20140131102016.GA29924@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rafael.barbalho@intel.com \
/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