From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
To: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
Cc: Joonyoung Shim <jy0922.shim@samsung.com>,
linux-samsung-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org, inki.dae@samsung.com
Subject: Re: [PATCH v2 2/2] drm/exynos: remove unused 'activated' field from exynos_drm_plane
Date: Fri, 17 Apr 2015 16:00:17 -0300 [thread overview]
Message-ID: <20150417190017.GB1997@joana> (raw)
In-Reply-To: <456f092fcd8f60331518a44fe898b0eb@math.uni-bielefeld.de>
2015-04-17 Tobias Jakobi <tjakobi@math.uni-bielefeld.de>:
> Hello Joonyoung,
>
> On 2015-04-17 08:30, Joonyoung Shim wrote:
> >Hi Tobias,
> >
> >On 04/16/2015 04:54 AM, Tobias Jakobi wrote:
> >>No component of Exynos DRM uses this field. Perhaps it was
> >>once meant to provide more fine-grained information in
> >>addition to the status stored in the 'enabled' field.
> >>
> >>Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> >>Signed-off-by: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
> >>---
> >> drivers/gpu/drm/exynos/exynos_drm_drv.h | 2 --
> >> 1 file changed, 2 deletions(-)
> >>
> >>diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.h
> >>b/drivers/gpu/drm/exynos/exynos_drm_drv.h
> >>index 6a849cf..4c14a89 100644
> >>--- a/drivers/gpu/drm/exynos/exynos_drm_drv.h
> >>+++ b/drivers/gpu/drm/exynos/exynos_drm_drv.h
> >>@@ -77,7 +77,6 @@ extern void exynos4412_qos(u8 tm, u8 ac);
> >> * @color_key: color key on or off.
> >> * @local_path: in case of lcd type, local path mode on or off.
> >> * @transparency: transparency on or off.
> >>- * @activated: activated or not.
> >> * @enabled: enabled or not.
> >> * @resume: to resume or not.
> >> *
> >>@@ -112,7 +111,6 @@ struct exynos_drm_plane {
> >> bool color_key:1;
> >> bool local_path:1;
> >> bool transparency:1;
> >>- bool activated:1;
> >> bool enabled:1;
> >> bool resume:1;
> >> };
> >>
> >
> >The following fields also are unused in exynos drm driver,
> >- default win, color_key, local_path, transparency
> Yeah, looks like it. I just stumbled upon 'activated' because I was
> wondering what the difference between 'enabled' and 'activated' was.
> Grepping than revealed that nothing was using that field. I didn't check any
> other fields.
>
> Also I just noticed that due to how git formats the patches, this one
> doesn't apply to any of Inki's branches (due to the 'extern void
> exynos4412_qos(u8 tm, u8 ac);' line).
>
> Should I respin this, and if yes, should I also drop the other fields
> mentioned? Question is more directed to Gustavo, since he's cleaning
> 'exynos_drm_plane' anyway.
Let's remove them now, that doesn't affect my work.
Gustavo
prev parent reply other threads:[~2015-04-17 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 19:54 drm/exynos: two small fixes Tobias Jakobi
2015-04-15 19:54 ` [PATCH v2 1/2] drm/exynos: mixer: move pixelformat defines Tobias Jakobi
2015-04-15 19:54 ` [PATCH v2 2/2] drm/exynos: remove unused 'activated' field from exynos_drm_plane Tobias Jakobi
2015-04-17 6:30 ` Joonyoung Shim
2015-04-17 8:04 ` Tobias Jakobi
2015-04-17 8:23 ` Joonyoung Shim
2015-04-17 9:16 ` Inki Dae
2015-04-17 19:00 ` Gustavo Padovan [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=20150417190017.GB1997@joana \
--to=gustavo.padovan@collabora.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tjakobi@math.uni-bielefeld.de \
/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