Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel GFX discussion <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] lib: Fix build when vc4 headers are present
Date: Tue, 9 Feb 2016 16:25:00 +0100	[thread overview]
Message-ID: <20160209152500.GA11240@phenom.ffwll.local> (raw)
In-Reply-To: <1455029137-8218-1-git-send-email-tomeu.vizoso@collabora.com>

On Tue, Feb 09, 2016 at 03:45:37PM +0100, Tomeu Vizoso wrote:
> Automake seems to not like variable assignments indented with tabs.
> 
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> Fixes: 9e5478dc4345 ("lib: Only compile igt_vc4 is we have it")

Yay, I'm incompetent. Thanks for fixing this up, applied.
-Daniel

> ---
>  lib/Makefile.am | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lib/Makefile.am b/lib/Makefile.am
> index 460e0046e00f..e3a456bacaf3 100644
> --- a/lib/Makefile.am
> +++ b/lib/Makefile.am
> @@ -9,9 +9,9 @@ noinst_LTLIBRARIES = libintel_tools.la
>  noinst_HEADERS = check-ndebug.h
>  
>  if HAVE_VC4
> -	libintel_tools_la_SOURCES += 	\
> -		igt_vc4.c		\
> -		igt_vc4.h
> +    libintel_tools_la_SOURCES += 	\
> +        igt_vc4.c			\
> +        igt_vc4.h
>  endif
>  
>  AM_CPPFLAGS = -I$(top_srcdir)
> -- 
> 2.5.0
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-02-09 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 14:45 [PATCH i-g-t] lib: Fix build when vc4 headers are present Tomeu Vizoso
2016-02-09 15:25 ` Daniel Vetter [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=20160209152500.GA11240@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tomeu.vizoso@collabora.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