linux-kernel - Re: [PATCH 1/3] drm/mediatek: mtk_dpi: Add check for max clock rate in mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <202102080056.aBS36ve3-lkp@intel.com>
Date:   Mon, 8 Feb 2021 00:58:28 +0800
From:   kernel test robot <lkp@...el.com>
To:     Jitao Shi <jitao.shi@...iatek.com>,
        Chun-Kuang Hu <chunkuang.hu@...nel.org>,
        Philipp Zabel <p.zabel@...gutronix.de>
Cc:     kbuild-all@...ts.01.org, devicetree@...r.kernel.org,
        Jitao Shi <jitao.shi@...iatek.com>,
        srv_heupstream@...iatek.com, shuijing.li@...iatek.com,
        airlied@...ux.ie, huijuan.xie@...iatek.com, stonea168@....com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] drm/mediatek: mtk_dpi: Add check for max clock rate
 in mode_valid

Hi Jitao,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on robh/for-next]
[also build test ERROR on pza/reset/next 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/730e2bd7e5dd88d40a320cd8d74057a51a3d3395
        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 730e2bd7e5dd88d40a320cd8d74057a51a3d3395
        # 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@...el.com>

All errors (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')
   cc1: some warnings being treated as errors


vim +574 drivers/gpu/drm/mediatek/mtk_dpi.c

   570	
   571	static const struct drm_bridge_funcs mtk_dpi_bridge_funcs = {
   572		.attach = mtk_dpi_bridge_attach,
   573		.mode_set = mtk_dpi_bridge_mode_set,
 > 574		.mode_valid = mtk_dpi_bridge_mode_valid,
   575		.disable = mtk_dpi_bridge_disable,
   576		.enable = mtk_dpi_bridge_enable,
   577	};
   578	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

Download attachment ".config.gz" of type "application/gzip" (76477 bytes)