From: kernel test robot <lkp@intel.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Aradhya Bhatia <a-bhatia1@ti.com>
Cc: oe-kbuild-all@lists.linux.dev,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/bridge: Add debugfs print for bridge chains
Date: Fri, 21 Jul 2023 21:28:32 +0800 [thread overview]
Message-ID: <202307212102.Fxrv1Ayx-lkp@intel.com> (raw)
In-Reply-To: <20230721-drm-bridge-chain-debugfs-v1-1-8614ff7e890d@ideasonboard.com>
Hi Tomi,
kernel test robot noticed the following build errors:
[auto build test ERROR on c7a472297169156252a50d76965eb36b081186e2]
url: https://github.com/intel-lab-lkp/linux/commits/Tomi-Valkeinen/drm-bridge-Add-debugfs-print-for-bridge-chains/20230721-174615
base: c7a472297169156252a50d76965eb36b081186e2
patch link: https://lore.kernel.org/r/20230721-drm-bridge-chain-debugfs-v1-1-8614ff7e890d%40ideasonboard.com
patch subject: [PATCH] drm/bridge: Add debugfs print for bridge chains
config: x86_64-randconfig-r032-20230720 (https://download.01.org/0day-ci/archive/20230721/202307212102.Fxrv1Ayx-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230721/202307212102.Fxrv1Ayx-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@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202307212102.Fxrv1Ayx-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/drm_bridge.c: In function 'drm_bridge_chains_info':
>> drivers/gpu/drm/drm_bridge.c:1371:35: error: 'struct drm_bridge' has no member named 'of_node'
1371 | if (bridge->of_node)
| ^~
drivers/gpu/drm/drm_bridge.c:1372:70: error: 'struct drm_bridge' has no member named 'of_node'
1372 | drm_printf(&p, ", OF: %pOFfc", bridge->of_node);
| ^~
vim +1371 drivers/gpu/drm/drm_bridge.c
1349
1350 #ifdef CONFIG_DEBUG_FS
1351 static int drm_bridge_chains_info(struct seq_file *m, void *data)
1352 {
1353 struct drm_debugfs_entry *entry = m->private;
1354 struct drm_device *dev = entry->dev;
1355 struct drm_printer p = drm_seq_file_printer(m);
1356 struct drm_mode_config *config = &dev->mode_config;
1357 struct drm_encoder *encoder;
1358 unsigned int bridge_idx = 0;
1359
1360 list_for_each_entry(encoder, &config->encoder_list, head) {
1361 struct drm_bridge *bridge;
1362
1363 drm_printf(&p, "encoder[%u]\n", encoder->base.id);
1364
1365 bridge = drm_bridge_chain_get_first_bridge(encoder);
1366
1367 while (bridge) {
1368 drm_printf(&p, "\tbridge[%u] type: %u, ops: %#x",
1369 bridge_idx, bridge->type, bridge->ops);
1370
> 1371 if (bridge->of_node)
1372 drm_printf(&p, ", OF: %pOFfc", bridge->of_node);
1373
1374 drm_printf(&p, "\n");
1375
1376 bridge_idx++;
1377 bridge = drm_bridge_get_next_bridge(bridge);
1378 }
1379 }
1380
1381 return 0;
1382 }
1383
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-07-21 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 9:41 Tomi Valkeinen
2023-07-21 13:28 ` kernel test robot [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=202307212102.Fxrv1Ayx-lkp@intel.com \
--to=lkp@intel.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a-bhatia1@ti.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=francesco.dolcini@toradex.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rfoss@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--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
all inboxes | Powered by JetHome®