All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@intel.com>,
	linux-kernel@vger.kernel.org,
	Philippe Cornu <philippe.cornu@st.com>,
	Yannick Fertre <yannick.fertre@st.com>
Subject: Re: [PATCH v3 12/16] drm/stm: remove unneeded -Iinclude/drm compiler flag
Date: Mon, 22 May 2017 09:37:56 +0200	[thread overview]
Message-ID: <20170522073756.fubdnkt3ymzv2dm3@phenom.ffwll.local> (raw)
In-Reply-To: <1495081793-9707-13-git-send-email-yamada.masahiro@socionext.com>

On Thu, May 18, 2017 at 01:29:49PM +0900, Masahiro Yamada wrote:
> With the include directives under include/drm/ fixed, this flag is
> no longer needed.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>

Ok, this and patch 1 applied, pls double-check I've done the right thing
and it's all good now (well, once linux-next has rebuild with the 2
patches merged, which should be in 1-2 days at most).

Thanks, Daniel

> ---
> 
> Changes in v3: None
> 
>  drivers/gpu/drm/stm/Makefile | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/stm/Makefile b/drivers/gpu/drm/stm/Makefile
> index e114d45..a09ecf4 100644
> --- a/drivers/gpu/drm/stm/Makefile
> +++ b/drivers/gpu/drm/stm/Makefile
> @@ -1,5 +1,3 @@
> -ccflags-y := -Iinclude/drm
> -
>  stm-drm-y := \
>  	drv.o \
>  	ltdc.o
> -- 
> 2.7.4
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Yannick Fertre <yannick.fertre@st.com>,
	Daniel Vetter <daniel.vetter@intel.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Philippe Cornu <philippe.cornu@st.com>
Subject: Re: [PATCH v3 12/16] drm/stm: remove unneeded -Iinclude/drm compiler flag
Date: Mon, 22 May 2017 09:37:56 +0200	[thread overview]
Message-ID: <20170522073756.fubdnkt3ymzv2dm3@phenom.ffwll.local> (raw)
In-Reply-To: <1495081793-9707-13-git-send-email-yamada.masahiro@socionext.com>

On Thu, May 18, 2017 at 01:29:49PM +0900, Masahiro Yamada wrote:
> With the include directives under include/drm/ fixed, this flag is
> no longer needed.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>

Ok, this and patch 1 applied, pls double-check I've done the right thing
and it's all good now (well, once linux-next has rebuild with the 2
patches merged, which should be in 1-2 days at most).

Thanks, Daniel

> ---
> 
> Changes in v3: None
> 
>  drivers/gpu/drm/stm/Makefile | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/stm/Makefile b/drivers/gpu/drm/stm/Makefile
> index e114d45..a09ecf4 100644
> --- a/drivers/gpu/drm/stm/Makefile
> +++ b/drivers/gpu/drm/stm/Makefile
> @@ -1,5 +1,3 @@
> -ccflags-y := -Iinclude/drm
> -
>  stm-drm-y := \
>  	drv.o \
>  	ltdc.o
> -- 
> 2.7.4
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

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

  reply	other threads:[~2017-05-22  7:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18  4:29 [PATCH v3 00/16] gpu/drm: remove -Iinclude/drm compiler flags from Makefile Masahiro Yamada
2017-05-18  4:29 ` Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 01/16] drm/vc4: fix include notation and remove -Iinclude/drm flag Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 02/16] drm/virtio: " Masahiro Yamada
2017-05-18  4:29 ` Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 03/16] drm/vmwgfx: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 04/16] drm/gma500: remove unneeded -Iinclude/drm compiler flag Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 05/16] drm/i810: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 06/16] drm/i2c: " Masahiro Yamada
2017-05-18  5:25   ` Archit Taneja
2017-05-18  5:25     ` Archit Taneja
2017-05-18  4:29 ` [PATCH v3 07/16] drm/mga: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 08/16] drm/omap: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 09/16] drm/r128: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 10/16] drm/savage: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 11/16] drm/sis: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 12/16] drm/stm: " Masahiro Yamada
2017-05-22  7:37   ` Daniel Vetter [this message]
2017-05-22  7:37     ` Daniel Vetter
2017-05-22  7:48     ` Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 13/16] drm/tdfx: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 14/16] drm/udl: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 15/16] drm/vgem: " Masahiro Yamada
2017-05-18  4:29 ` [PATCH v3 16/16] drm/via: " Masahiro Yamada

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=20170522073756.fubdnkt3ymzv2dm3@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philippe.cornu@st.com \
    --cc=yamada.masahiro@socionext.com \
    --cc=yannick.fertre@st.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.