From: Dave Gordon <david.s.gordon@intel.com>
To: "Morton, Derek J" <derek.j.morton@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Wood, Thomas" <thomas.wood@intel.com>
Subject: Re: [PATCH i-g-t v3] Android.mk: Disable tools that do not build for android
Date: Mon, 03 Aug 2015 15:53:42 +0100 [thread overview]
Message-ID: <55BF8076.3030904@intel.com> (raw)
In-Reply-To: <2D016F5BA44C744783BA96B1D3EBC5BD11D25E8F@IRSMSX104.ger.corp.intel.com>
On 17/07/15 09:53, Morton, Derek J wrote:
>>
>>
>> -----Original Message-----
>> From: Morton, Derek J
>> Sent: Friday, July 17, 2015 9:44 AM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Wood, Thomas; Morton, Derek J
>> Subject: [PATCH i-g-t v3] Android.mk: Disable tools that do not build for android
>>
>> Disable the tools / demo code that do not currently build for android until they can be fixed.
>>
>> Affected tools / demos
>> intel_display_crc
>> intel_sprite_on
>>
>> v2: intel_display_crc compiled conditionally on ANDROID_HAS_CAIRO flag.
>> v3: removed intel_reg from the skip list as Thomas has prepared a patch to fix it for Android.
>>
>> Signed-off-by: Derek Morton <derek.j.morton@intel.com>
>> ---
>> Android.mk | 2 +-
>> tools/Android.mk | 5 +++++
>> 2 files changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/Android.mk b/Android.mk
>> index 1ab3e64..681d114 100644
>> --- a/Android.mk
>> +++ b/Android.mk
>> @@ -1,2 +1,2 @@
>> -include $(call all-named-subdir-makefiles, lib tests tools benchmarks demos)
>> +include $(call all-named-subdir-makefiles, lib tests tools benchmarks)
>>
>> diff --git a/tools/Android.mk b/tools/Android.mk index 39f4512..4be0032 100644
>> --- a/tools/Android.mk
>> +++ b/tools/Android.mk
>> @@ -37,10 +37,15 @@ endef
>>
>> skip_tools_list := \
>> intel_framebuffer_dump \
>> + intel_reg \
>
> That's weird, git diff HEAD^ shows this being removed but git format-patch HEAD^ has left it in.
The relevant man pages say:
git diff [--options] <commit> [--] [<path>...]
This form is to view the changes you have in your working
tree relative to the named <commit>. You can use HEAD to compare it with
the latest commit, or a branch name to compare with the tip of a
different branch.
git format-patch [-k] [(-o|--output-directory) <dir> | --stdout]
...
[<common diff options>]
[ <since> | <revision range> ]
So "git format-patch HEAD^" is describing the changes between HEAD^ and
HEAD i.e. 'since' == HEAD^, equivalent to revision range "HEAD^..HEAD"
Whereas "git diff HEAD^" is comparing the commit referenced by "HEAD^"
with the current working tree (which might differ from HEAD). They'll be
different if you have uncommitted changes in your working tree!
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-03 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 8:44 [PATCH i-g-t v3] Android.mk: Disable tools that do not build for android Derek Morton
2015-07-17 8:53 ` Morton, Derek J
2015-08-03 14:53 ` Dave Gordon [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-17 9:15 Derek Morton
2015-07-17 14:18 ` Thomas Wood
2015-07-17 15:42 ` Morton, Derek J
2015-07-21 6:53 ` Daniel Vetter
2015-07-21 9:34 ` Morton, Derek J
2015-07-21 9:39 ` Gore, Tim
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=55BF8076.3030904@intel.com \
--to=david.s.gordon@intel.com \
--cc=derek.j.morton@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.