LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Chun-Kuang Hu <chunkuang.hu@kernel.org> To: "jason-jh.lin" <jason-jh.lin@mediatek.com> Cc: Matthias Brugger <matthias.bgg@gmail.com>, Chun-Kuang Hu <chunkuang.hu@kernel.org>, fshao@chromium.org, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, DRI Development <dri-devel@lists.freedesktop.org>, "moderated list:ARM/Mediatek SoC support" <linux-mediatek@lists.infradead.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, linux-kernel <linux-kernel@vger.kernel.org>, Hsin-Yi Wang <hsinyi@chromium.org>, Yongqiang Niu <yongqiang.niu@mediatek.com>, Nancy Lin <nancy.lin@mediatek.com>, singo.chang@mediatek.com Subject: Re: [PATCH v2] drm/mediatek: Add component_del in OVL and COLOR remove function Date: Thu, 12 Aug 2021 07:05:57 +0800 [thread overview] Message-ID: <CAAOTY_9+G92rhKCiZZS39VCjo6g3Zj+Ag=SeEuRtbP3c=jsSug@mail.gmail.com> (raw) In-Reply-To: <20210810040148.17157-1-jason-jh.lin@mediatek.com> Hi, Jason: jason-jh.lin <jason-jh.lin@mediatek.com> 於 2021年8月10日 週二 下午12:02寫道: > > Add component_del in OVL and COLOR remove function. Applied to mediatek-drm-fixes [1], thanks. [1] https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git/log/?h=mediatek-drm-fixes Regards, Chun-Kuang. > > Fixes: ff1395609e20 ("drm/mediatek: Move mtk_ddp_comp_init() from sub driver to DRM driver") > Signed-off-by: jason-jh.lin <jason-jh.lin@mediatek.com> > --- > Change in v2: > - add component_del function in COLOR remove function > --- > drivers/gpu/drm/mediatek/mtk_disp_color.c | 2 ++ > drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 2 ++ > 2 files changed, 4 insertions(+) > > diff --git a/drivers/gpu/drm/mediatek/mtk_disp_color.c b/drivers/gpu/drm/mediatek/mtk_disp_color.c > index 6f4c80bbc0eb..473f5bb5cbad 100644 > --- a/drivers/gpu/drm/mediatek/mtk_disp_color.c > +++ b/drivers/gpu/drm/mediatek/mtk_disp_color.c > @@ -133,6 +133,8 @@ static int mtk_disp_color_probe(struct platform_device *pdev) > > static int mtk_disp_color_remove(struct platform_device *pdev) > { > + component_del(&pdev->dev, &mtk_disp_color_component_ops); > + > return 0; > } > > diff --git a/drivers/gpu/drm/mediatek/mtk_disp_ovl.c b/drivers/gpu/drm/mediatek/mtk_disp_ovl.c > index fa9d79963cd3..5326989d5206 100644 > --- a/drivers/gpu/drm/mediatek/mtk_disp_ovl.c > +++ b/drivers/gpu/drm/mediatek/mtk_disp_ovl.c > @@ -423,6 +423,8 @@ static int mtk_disp_ovl_probe(struct platform_device *pdev) > > static int mtk_disp_ovl_remove(struct platform_device *pdev) > { > + component_del(&pdev->dev, &mtk_disp_ovl_component_ops); > + > return 0; > } > > -- > 2.18.0 >
parent reply other threads:[~2021-08-11 23:06 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <20210810040148.17157-1-jason-jh.lin@mediatek.com>]
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='CAAOTY_9+G92rhKCiZZS39VCjo6g3Zj+Ag=SeEuRtbP3c=jsSug@mail.gmail.com' \ --to=chunkuang.hu@kernel.org \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=fshao@chromium.org \ --cc=hsinyi@chromium.org \ --cc=jason-jh.lin@mediatek.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=matthias.bgg@gmail.com \ --cc=nancy.lin@mediatek.com \ --cc=singo.chang@mediatek.com \ --cc=yongqiang.niu@mediatek.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: linkBe 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; as well as URLs for NNTP newsgroup(s).