From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH] drm/bridge: adv7511: Fix Intermittent EDID failures
Date: Wed, 22 May 2024 22:55:17 +0800 [thread overview]
Message-ID: <202405222253.p3vRbJDH-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20240521011614.496421-1-aford173@gmail.com>
References: <20240521011614.496421-1-aford173@gmail.com>
TO: Adam Ford <aford173@gmail.com>
TO: dri-devel@lists.freedesktop.org
CC: dmitry.baryshkov@linaro.org
CC: ictor.liu@nxp.com
CC: sui.jingfeng@linux.dev
CC: aford@beaconembedded.com
CC: Adam Ford <aford173@gmail.com>
CC: Andrzej Hajda <andrzej.hajda@intel.com>
CC: Neil Armstrong <neil.armstrong@linaro.org>
CC: Robert Foss <rfoss@kernel.org>
CC: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
CC: Jonas Karlman <jonas@kwiboo.se>
CC: Jernej Skrabec <jernej.skrabec@gmail.com>
CC: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
CC: Maxime Ripard <mripard@kernel.org>
CC: Thomas Zimmermann <tzimmermann@suse.de>
CC: David Airlie <airlied@gmail.com>
CC: Daniel Vetter <daniel@ffwll.ch>
CC: linux-kernel@vger.kernel.org
Hi Adam,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-tip/drm-tip linus/master drm-intel/for-linux-next-fixes v6.9 next-20240522]
[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/Adam-Ford/drm-bridge-adv7511-Fix-Intermittent-EDID-failures/20240521-091841
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20240521011614.496421-1-aford173%40gmail.com
patch subject: [PATCH] drm/bridge: adv7511: Fix Intermittent EDID failures
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: i386-randconfig-141-20240522 (https://download.01.org/0day-ci/archive/20240522/202405222253.p3vRbJDH-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.5.0-4ubuntu2) 9.5.0
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202405222253.p3vRbJDH-lkp@intel.com/
smatch warnings:
drivers/gpu/drm/bridge/adv7511/adv7511_drv.c:507 adv7511_irq_process() error: uninitialized symbol 'cec_status'.
vim +/cec_status +507 drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
3b1b975003e4a3 drivers/gpu/drm/bridge/adv7511/adv7511_drv.c Hans Verkuil 2017-10-07 505
2d0835b065781a drivers/gpu/drm/bridge/adv7511/adv7511_drv.c Adam Ford 2024-05-20 506 /* If there is no IRQ to handle, exit indicating no IRQ data */
2d0835b065781a drivers/gpu/drm/bridge/adv7511/adv7511_drv.c Adam Ford 2024-05-20 @507 if (irq_status == IRQ_HANDLED || cec_status == IRQ_HANDLED)
2d0835b065781a drivers/gpu/drm/bridge/adv7511/adv7511_drv.c Adam Ford 2024-05-20 508 return IRQ_HANDLED;
2d0835b065781a drivers/gpu/drm/bridge/adv7511/adv7511_drv.c Adam Ford 2024-05-20 509
2d0835b065781a drivers/gpu/drm/bridge/adv7511/adv7511_drv.c Adam Ford 2024-05-20 510 return IRQ_NONE;
a5241289c4139f drivers/gpu/drm/i2c/adv7511.c Laurent Pinchart 2015-02-18 511 }
9c8af882bf1230 drivers/gpu/drm/i2c/adv7511.c Lars-Peter Clausen 2012-03-05 512
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-05-22 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 14:55 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-21 1:16 [PATCH] drm/bridge: adv7511: Fix Intermittent EDID failures Adam Ford
2024-05-21 21:12 ` kernel test robot
2024-05-21 21:51 ` Adam Ford
2024-05-22 1:58 ` Liu Ying
2024-05-22 9:48 ` Dmitry Baryshkov
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=202405222253.p3vRbJDH-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.