linux-kernel - Re: [PATCH v6 02/10] drm/bridge: Set firmware node of drm

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] [day] [month] [year] [list]

Message-ID: <db39b18b-b941-44b8-abeb-d06c5cc087d7@linux.dev>
Date: Mon, 27 May 2024 10:06:20 +0800
From: Sui Jingfeng <sui.jingfeng@...ux.dev>
To: kernel test robot <lkp@...el.com>, Robert Foss <rfoss@...nel.org>,
 Laurent Pinchart <Laurent.pinchart@...asonboard.com>
Cc: llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
 dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 02/10] drm/bridge: Set firmware node of drm_bridge
 instances automatically

Hi,


On 5/27/24 07:33, kernel test robot wrote:
> Hi Sui,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on drm-exynos/exynos-drm-next]
> [also build test ERROR on linus/master v6.10-rc1 next-20240523]
> [cannot apply to shawnguo/for-next]
> [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#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Sui-Jingfeng/drm-bridge-Allow-using-fwnode-APIs-to-get-the-next-bridge/20240527-042402
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git exynos-drm-next
> patch link:    https://lore.kernel.org/r/20240526202115.129049-3-sui.jingfeng%40linux.dev
> patch subject: [PATCH v6 02/10] drm/bridge: Set firmware node of drm_bridge instances automatically
> config: arm-defconfig (https://download.01.org/0day-ci/archive/20240527/202405270622.VDMbp9FR-lkp@intel.com/config)
> compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240527/202405270622.VDMbp9FR-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202405270622.VDMbp9FR-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>>> drivers/gpu/drm/omapdrm/dss/hdmi5.c:487:49: error: expected identifier
>             drm_bridge_add(&hdmi->bridge, &hdmi->pdev->dev.);
>                                                            ^
>     1 error generated.
> 
> 
> vim +487 drivers/gpu/drm/omapdrm/dss/hdmi5.c
> 
>     480	
>     481	static void hdmi5_bridge_init(struct omap_hdmi *hdmi)
>     482	{
>     483		hdmi->bridge.funcs = &hdmi5_bridge_funcs;
>     484		hdmi->bridge.ops = DRM_BRIDGE_OP_EDID;
>     485		hdmi->bridge.type = DRM_MODE_CONNECTOR_HDMIA;
>     486	
>   > 487		drm_bridge_add(&hdmi->bridge, &hdmi->pdev->dev.);
>     488	}
>     489	
> 


Sorry, my bad. I have do compile test on ARM64 before posting.
checkpatch.pl report a style problem, then I manually modify this
patch, accidentally add the tail '.' character. Will be fixed
at the next version.

-- 
Best regards
Sui