From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Stone <daniels@collabora.com>
Cc: Thierry Reding <treding@nvidia.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] drm/mtk: Remove impossible internal error
Date: Fri, 18 May 2018 16:29:11 +0200 [thread overview]
Message-ID: <20180518142911.GA20436@ulmo> (raw)
In-Reply-To: <20180518134705.12533-1-daniels@collabora.com>
[-- Attachment #1.1: Type: text/plain, Size: 580 bytes --]
On Fri, May 18, 2018 at 02:47:03PM +0100, Daniel Stone wrote:
> We cannot create a framebuffer with no objects, so there's no point
> testing for it.
>
> v2: Remove the error entirely. (Sean, CK, Thierry)
>
> Signed-off-by: Daniel Stone <daniels@collabora.com>
> Cc: Sean Paul <seanpaul@chromium.org>
> Cc: Thierry Reding <treding@nvidia.com>
> Cc: CK Hu <ck.hu@mediatek.com>
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> ---
> drivers/gpu/drm/mediatek/mtk_drm_plane.c | 5 -----
> 1 file changed, 5 deletions(-)
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-18 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 13:47 [PATCH v2 1/3] drm/mtk: Remove impossible internal error Daniel Stone
2018-05-18 13:47 ` [PATCH v2 2/3] drm/mtk: Move GEM BO to drm_framebuffer Daniel Stone
2018-05-18 13:47 ` [PATCH v2 3/3] drm/mtk: mtk_drm_fb -> drm_framebuffer Daniel Stone
2018-05-18 14:29 ` Thierry Reding [this message]
2018-05-21 1:50 ` [PATCH v2 1/3] drm/mtk: Remove impossible internal error CK Hu
2018-07-02 1:46 ` CK Hu
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=20180518142911.GA20436@ulmo \
--to=thierry.reding@gmail.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=treding@nvidia.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.