From: Philipp Zabel <p.zabel@pengutronix.de>
To: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
Cc: k.kozlowski@samsung.com, linux-samsung-soc@vger.kernel.org,
jingoohan1@gmail.com, virtualization@lists.linux-foundation.org,
linux-rockchip@lists.infradead.org, kgene@kernel.org,
dri-devel@lists.freedesktop.org, benjamin.gaignard@linaro.org,
vincent.abriou@st.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 10/17] drm/imx: removed optional dummy encoder mode_fixup function.
Date: Mon, 15 Feb 2016 17:16:55 +0100 [thread overview]
Message-ID: <1455553015.4899.38.camel@pengutronix.de> (raw)
In-Reply-To: <8bf274e8f6908142a9f940d3f2913e4a735e0caa.1455540137.git.palminha@synopsys.com>
Am Montag, den 15.02.2016, 13:00 +0000 schrieb Carlos Palminha:
> mode_fixup function for encoder drivers became optional with patch
> http://patchwork.freedesktop.org/patch/msgid/1455106522-32307-1-git-send-email-palminha@synopsys.com
>
> This patch set nukes all the dummy mode_fixup implementations.
>
> (made on top of Daniel topic/drm-misc branch)
>
> Signed-off-by: Carlos Palminha <palminha@synopsys.com>
Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-02-15 16:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 12:57 [PATCH v2 00/17] drm encoders cleanup: nuke optional dummy encoder mode_fixup function Carlos Palminha
2016-02-15 12:57 ` [PATCH v2 01/17] drm/virtio: removed " Carlos Palminha
2016-02-15 12:57 ` [PATCH v2 02/17] drm/udl: " Carlos Palminha
2016-02-15 12:58 ` [PATCH v2 03/17] drm/exynos: " Carlos Palminha
2016-02-15 13:49 ` Patrik Jakobsson
2016-02-15 15:18 ` Carlos Palminha
2016-02-16 14:31 ` Daniel Vetter
2016-02-15 12:58 ` [PATCH v2 04/17] drm/amdgpu: " Carlos Palminha
2016-02-15 12:59 ` [PATCH v2 05/17] drm/ast: " Carlos Palminha
2016-02-15 12:59 ` [PATCH v2 06/17] drm/bochs: " Carlos Palminha
2016-02-15 12:59 ` [PATCH v2 07/17] drm/cirrus: " Carlos Palminha
2016-02-15 12:59 ` [PATCH v2 08/17] drm/exynos: " Carlos Palminha
2016-02-15 13:00 ` [PATCH v2 09/17] drm/gma500: " Carlos Palminha
2016-02-15 14:24 ` Patrik Jakobsson
2016-02-15 13:00 ` [PATCH v2 10/17] drm/imx: " Carlos Palminha
2016-02-15 16:16 ` Philipp Zabel [this message]
2016-02-15 13:00 ` [PATCH v2 11/17] drm/msm/mdp: " Carlos Palminha
2016-02-15 13:00 ` [PATCH v2 12/17] drm/mgag200: " Carlos Palminha
2016-02-15 13:00 ` [PATCH v2 13/17] drm/qxl: " Carlos Palminha
2016-02-15 13:01 ` [PATCH v2 14/17] drm/radeon: " Carlos Palminha
2016-02-15 13:01 ` [PATCH v2 15/17] drm/rockchip: " Carlos Palminha
2016-02-16 0:39 ` Mark yao
2016-02-15 13:01 ` [PATCH v2 16/17] drm/sti: " Carlos Palminha
2016-02-15 16:44 ` Vincent ABRIOU
2016-02-15 13:01 ` [PATCH v2 17/17] drm/tilcdc: " Carlos Palminha
2016-02-15 14:19 ` [PATCH v2 00/17] drm encoders cleanup: nuke " Christian König
2016-02-16 14:38 ` Daniel Vetter
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=1455553015.4899.38.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=vincent.abriou@st.com \
--cc=virtualization@lists.linux-foundation.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