From: Jason-JH Lin <jason-jh.lin@mediatek.com>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Matthias Brugger <matthias.bgg@gmail.com>, <tzungbi@google.com>,
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>,
"Fei Shao" <fshao@chromium.org>,
Nancy Lin <nancy.lin@mediatek.com>, <singo.chang@mediatek.com>
Subject: Re: [PATCH v4 2/2] drm/mediatek: add devlink to cmdq dev
Date: Tue, 1 Mar 2022 09:46:42 +0800 [thread overview]
Message-ID: <fa9a04263ed0b1aa54a140e7eec47e838d3e5587.camel@mediatek.com> (raw)
In-Reply-To: <CAAOTY__rnVMRB=OhkTm4Ojh31yAcYwCQTBGozpGsnC_oC_jqvQ@mail.gmail.com>
Hi Chun-Kuang,
Thanks for the reviews.
I forgot to add the comment that the patch should be based on [1].
We can only apply it after applying [1].
So please apply it after that. Thank you very much!
Regards,
Jason-JH.Lin
---
[1] drm/mediatek: modify mediatek-drm for mt8195 multi mmsys support
https://patchwork.kernel.org/project/linux-mediatek/patch/20220222100741.30138-21-nancy.lin@mediatek.com/
---
On Sun, 2022-02-27 at 11:33 +0800, Chun-Kuang Hu wrote:
> Hi, Jason:
>
> Build error:
>
> ../drivers/gpu/drm/mediatek/mtk_drm_crtc.c: In function
> ‘mtk_drm_crtc_create’:
> ../drivers/gpu/drm/mediatek/mtk_drm_crtc.c:902:26: error: ‘struct
> mtk_drm_private’ has no member named ‘dev’
> mtk_crtc->drm_dev = priv->dev;
> ^
> ../drivers/gpu/drm/mediatek/mtk_drm_crtc.c:974:30: error: ‘struct
> mtk_drm_private’ has no member named ‘dev’
> link = device_link_add(priv->dev, mtk_crtc->cmdq_client.chan-
> >mbox->dev,
> ^
> In file included from ../include/linux/device.h:15:0,
> from ../include/linux/dma-mapping.h:7,
> from ../drivers/gpu/drm/mediatek/mtk_drm_crtc.c:7:
> ../drivers/gpu/drm/mediatek/mtk_drm_crtc.c:977:16: error: ‘struct
> mtk_drm_private’ has no member named ‘dev’
> dev_err(priv->dev, "Unable to link dev=%s\n",
> ^
> Regards,
> Chun-Kuang.
prev parent reply other threads:[~2022-03-01 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211202064039.20797-1-jason-jh.lin@mediatek.com>
[not found] ` <20211202064039.20797-2-jason-jh.lin@mediatek.com>
2021-12-02 23:21 ` [PATCH v4 1/2] drm/mediatek: add wait_for_event for crtc disable by cmdq Chun-Kuang Hu
2022-02-27 3:36 ` Chun-Kuang Hu
[not found] ` <20211202064039.20797-3-jason-jh.lin@mediatek.com>
2021-12-02 23:28 ` [PATCH v4 2/2] drm/mediatek: add devlink to cmdq dev Chun-Kuang Hu
2022-02-27 3:33 ` Chun-Kuang Hu
2022-03-01 1:46 ` Jason-JH Lin [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=fa9a04263ed0b1aa54a140e7eec47e838d3e5587.camel@mediatek.com \
--to=jason-jh.lin@mediatek.com \
--cc=airlied@linux.ie \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=fshao@chromium.org \
--cc=hsinyi@chromium.org \
--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=p.zabel@pengutronix.de \
--cc=singo.chang@mediatek.com \
--cc=tzungbi@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®