Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: Daniel Vetter <daniel@ffwll.ch>,
	Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
Cc: linux-samsung-soc@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/exynos: remove superfluous inclusions of fbdev header
Date: Fri, 10 Jun 2016 17:26:53 +0200	[thread overview]
Message-ID: <575ADC3D.5050600@math.uni-bielefeld.de> (raw)
In-Reply-To: <20160610141148.GY3363@phenom.ffwll.local>

Hello Daniel,

Daniel Vetter wrote:
> On Fri, Jun 10, 2016 at 12:12:45PM +0200, Tobias Jakobi wrote:
>> Ping!
> 
> exynos maintainer Inki isn't on cc, so good chances he'll miss this.
Both the initial mail and my ping have Inki in the Cc.

- Tobias


> -Daniel
> 
>>
>> - Tobias
>>
>> Tobias Jakobi wrote:
>>> Neither of these files issue any fbdev related calls.
>>>
>>> Signed-off-by: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
>>> ---
>>>  drivers/gpu/drm/exynos/exynos7_drm_decon.c | 1 -
>>>  drivers/gpu/drm/exynos/exynos_drm_core.c   | 1 -
>>>  drivers/gpu/drm/exynos/exynos_drm_fimd.c   | 1 -
>>>  3 files changed, 3 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/exynos/exynos7_drm_decon.c b/drivers/gpu/drm/exynos/exynos7_drm_decon.c
>>> index da1bd84..d9b2d77 100644
>>> --- a/drivers/gpu/drm/exynos/exynos7_drm_decon.c
>>> +++ b/drivers/gpu/drm/exynos/exynos7_drm_decon.c
>>> @@ -31,7 +31,6 @@
>>>  #include "exynos_drm_plane.h"
>>>  #include "exynos_drm_drv.h"
>>>  #include "exynos_drm_fb.h"
>>> -#include "exynos_drm_fbdev.h"
>>>  #include "exynos_drm_iommu.h"
>>>  
>>>  /*
>>> diff --git a/drivers/gpu/drm/exynos/exynos_drm_core.c b/drivers/gpu/drm/exynos/exynos_drm_core.c
>>> index 011211e..edbd98f 100644
>>> --- a/drivers/gpu/drm/exynos/exynos_drm_core.c
>>> +++ b/drivers/gpu/drm/exynos/exynos_drm_core.c
>>> @@ -15,7 +15,6 @@
>>>  #include <drm/drmP.h>
>>>  #include "exynos_drm_drv.h"
>>>  #include "exynos_drm_crtc.h"
>>> -#include "exynos_drm_fbdev.h"
>>>  
>>>  static LIST_HEAD(exynos_drm_subdrv_list);
>>>  
>>> diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
>>> index e20a194..bc175d6 100644
>>> --- a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
>>> +++ b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
>>> @@ -30,7 +30,6 @@
>>>  
>>>  #include "exynos_drm_drv.h"
>>>  #include "exynos_drm_fb.h"
>>> -#include "exynos_drm_fbdev.h"
>>>  #include "exynos_drm_crtc.h"
>>>  #include "exynos_drm_plane.h"
>>>  #include "exynos_drm_iommu.h"
>>>
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-06-10 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 12:35 [PATCH] drm/exynos: remove superfluous inclusions of fbdev header Tobias Jakobi
2016-06-10 10:12 ` Tobias Jakobi
2016-06-10 14:11   ` Daniel Vetter
2016-06-10 15:26     ` Tobias Jakobi [this message]
2016-06-13  1:34   ` Inki Dae

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=575ADC3D.5050600@math.uni-bielefeld.de \
    --to=tjakobi@math.uni-bielefeld.de \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-samsung-soc@vger.kernel.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