From: kernel test robot <lkp@intel.com>
To: Jitao Shi <jitao.shi@mediatek.com>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: kbuild-all@lists.01.org, devicetree@vger.kernel.org,
Jitao Shi <jitao.shi@mediatek.com>,
srv_heupstream@mediatek.com, shuijing.li@mediatek.com,
airlied@linux.ie, huijuan.xie@mediatek.com, stonea168@163.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] drm/mediatek: mtk_dpi: Add dpi config for mt8192
Date: Sun, 7 Feb 2021 23:09:24 +0800 [thread overview]
Message-ID: <202102072335.I1Jo78Qj-lkp@intel.com> (raw)
In-Reply-To: <20210207125850.155979-3-jitao.shi@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 2885 bytes --]
Hi Jitao,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linux/master linus/master v5.11-rc6 next-20210125]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Jitao-Shi/Add-check-for-max-clock-rate-in-mode_valid/20210207-210121
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/094ecc22dd2d9bfee293b97b33ba267a861ee301
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jitao-Shi/Add-check-for-max-clock-rate-in-mode_valid/20210207-210121
git checkout 094ecc22dd2d9bfee293b97b33ba267a861ee301
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/gpu/drm/mediatek/mtk_dpi.c:574:16: error: initialization of 'enum drm_mode_status (*)(struct drm_bridge *, const struct drm_display_info *, const struct drm_display_mode *)' from incompatible pointer type 'enum drm_mode_status (*)(struct drm_bridge *, const struct drm_display_mode *)' [-Werror=incompatible-pointer-types]
574 | .mode_valid = mtk_dpi_bridge_mode_valid,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/mediatek/mtk_dpi.c:574:16: note: (near initialization for 'mtk_dpi_bridge_funcs.mode_valid')
drivers/gpu/drm/mediatek/mtk_dpi.c:709:3: error: 'const struct mtk_dpi_conf' has no member named 'dual_edge'
709 | .dual_edge = true,
| ^~~~~~~~~
>> drivers/gpu/drm/mediatek/mtk_dpi.c:710:19: warning: initialized field overwritten [-Woverride-init]
710 | .max_clock_khz = 150000,
| ^~~~~~
drivers/gpu/drm/mediatek/mtk_dpi.c:710:19: note: (near initialization for 'mt8192_conf.max_clock_khz')
cc1: some warnings being treated as errors
vim +710 drivers/gpu/drm/mediatek/mtk_dpi.c
705
706 static const struct mtk_dpi_conf mt8192_conf = {
707 .cal_factor = mt8183_calculate_factor,
708 .reg_h_fre_con = 0xe0,
709 .dual_edge = true,
> 710 .max_clock_khz = 150000,
711 };
712
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 76477 bytes --]
next prev parent reply other threads:[~2021-02-07 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 12:58 [PATCH 0/3] Add check for max clock rate in mode_valid Jitao Shi
2021-02-07 12:58 ` [PATCH 1/3] drm/mediatek: mtk_dpi: " Jitao Shi
2021-02-07 16:58 ` kernel test robot
2021-02-07 12:58 ` [PATCH 2/3] drm/mediatek: mtk_dpi: Add dpi config for mt8192 Jitao Shi
2021-02-07 15:09 ` kernel test robot [this message]
2021-02-07 17:23 ` kernel test robot
2021-02-07 12:58 ` [PATCH 3/3] dt-bindings: mediatek,dpi: add mt8192 to mediatek,dpi Jitao Shi
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=202102072335.I1Jo78Qj-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=huijuan.xie@mediatek.com \
--cc=jitao.shi@mediatek.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=shuijing.li@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=stonea168@163.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;
as well as URLs for NNTP newsgroup(s).