From: Liu Ying <victor.liu@nxp.com>
To: kernel test robot <lkp@intel.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, p.zabel@pengutronix.de,
airlied@gmail.com, daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, guido.gunther@puri.sm,
marcel.ziswiler@toradex.com, laurentiu.palcu@oss.nxp.com,
robh@kernel.org
Subject: Re: [PATCH v12 5/6] drm/imx: Introduce i.MX8qm/qxp DPU DRM
Date: Wed, 19 Oct 2022 10:22:43 +0800 [thread overview]
Message-ID: <fd29de19b976148011ceb39aab879d55a2f243fb.camel@nxp.com> (raw)
In-Reply-To: <202210190730.rlLYtBVv-lkp@intel.com>
On Wed, 2022-10-19 at 07:41 +0800, kernel test robot wrote:
> Hi Liu,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on drm-misc/drm-misc-next]
> [also build test ERROR on drm/drm-next drm-exynos/exynos-drm-next
> drm-intel/for-linux-next drm-tip/drm-tip linus/master v6.1-rc1 next-
> 20221018]
[...]
> All errors (new ones prefixed by >>):
>
> drivers/gpu/drm/imx/dpu/dpu-drv.c: In function 'dpu_drm_bind':
> > > drivers/gpu/drm/imx/dpu/dpu-drv.c:67:12: error: 'struct
> > > drm_device' has no member named 'irq_enabled'
>
> 67 | drm->irq_enabled = true;
> | ^~
I've sent v13 to fix the potential build break by removing this line
since drm->irq_enabled should only be used by legacy drm drivers with
userspace modesetting but not imx-dpu drm driver.
Thanks for reporting the issue.
Liu Ying
[...]
next prev parent reply other threads:[~2022-10-19 2:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 9:23 [PATCH v12 0/6] drm/imx: Introduce i.MX8qm/qxp DPU DRM Liu Ying
2022-10-17 9:23 ` [PATCH v12 1/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPU binding Liu Ying
2022-10-17 9:23 ` [PATCH v12 2/6] dt-bindings: display: imx: Add i.MX8qxp/qm PRG binding Liu Ying
2022-10-17 9:23 ` [PATCH v12 3/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPR channel binding Liu Ying
2022-10-17 9:23 ` [PATCH v12 4/6] drm/atomic: Avoid unused-but-set-variable warning on for_each_old_plane_in_state Liu Ying
2022-10-17 9:23 ` [PATCH v12 5/6] drm/imx: Introduce i.MX8qm/qxp DPU DRM Liu Ying
2022-10-18 23:41 ` kernel test robot
2022-10-19 2:22 ` Liu Ying [this message]
2022-10-17 9:23 ` [PATCH v12 6/6] MAINTAINERS: add maintainer for i.MX8qxp DPU DRM driver Liu Ying
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=fd29de19b976148011ceb39aab879d55a2f243fb.camel@nxp.com \
--to=victor.liu@nxp.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=guido.gunther@puri.sm \
--cc=kbuild-all@lists.01.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marcel.ziswiler@toradex.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tzimmermann@suse.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;
as well as URLs for NNTP newsgroup(s).