From: kernel test robot <lkp@intel.com>
To: "Yo-Jung (Leo) Lin" <leo.lin@canonical.com>,
Jean Delvare <jdelvare@suse.com>,
Andi Shyti <andi.shyti@kernel.org>,
Wolfram Sang <wsa-dev@sang-engineering.com>
Cc: oe-kbuild-all@lists.linux.dev, Guenter Roeck <linux@roeck-us.net>,
"Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
"Yo-Jung Lin (Leo)" <leo.lin@canonical.com>
Subject: Re: [PATCH] i2c: i801: Do not instantiate spd5118 under SPD Write Disable
Date: Thu, 29 May 2025 07:59:25 +0800 [thread overview]
Message-ID: <202505290728.VsNgBfDO-lkp@intel.com> (raw)
In-Reply-To: <20250528-for-upstream-not-instantiate-spd5118-v1-1-8216e2d38918@canonical.com>
Hi Yo-Jung,
kernel test robot noticed the following build errors:
[auto build test ERROR on 176e917e010cb7dcc605f11d2bc33f304292482b]
url: https://github.com/intel-lab-lkp/linux/commits/Yo-Jung-Leo-Lin/i2c-i801-Do-not-instantiate-spd5118-under-SPD-Write-Disable/20250528-163253
base: 176e917e010cb7dcc605f11d2bc33f304292482b
patch link: https://lore.kernel.org/r/20250528-for-upstream-not-instantiate-spd5118-v1-1-8216e2d38918%40canonical.com
patch subject: [PATCH] i2c: i801: Do not instantiate spd5118 under SPD Write Disable
config: loongarch-randconfig-001-20250529 (https://download.01.org/0day-ci/archive/20250529/202505290728.VsNgBfDO-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250529/202505290728.VsNgBfDO-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/202505290728.VsNgBfDO-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/i2c/busses/i2c-i801.c: In function 'i801_notifier_call':
>> drivers/i2c/busses/i2c-i801.c:1304:9: error: implicit declaration of function '__i801_register_spd' [-Wimplicit-function-declaration]
1304 | __i801_register_spd(priv);
| ^~~~~~~~~~~~~~~~~~~
vim +/__i801_register_spd +1304 drivers/i2c/busses/i2c-i801.c
1291
1292 static int i801_notifier_call(struct notifier_block *nb, unsigned long action,
1293 void *data)
1294 {
1295 struct i801_priv *priv = container_of(nb, struct i801_priv, mux_notifier_block);
1296 struct device *dev = data;
1297
1298 if (action != BUS_NOTIFY_ADD_DEVICE ||
1299 dev->type != &i2c_adapter_type ||
1300 i2c_root_adapter(dev) != &priv->adapter)
1301 return NOTIFY_DONE;
1302
1303 /* Call i2c_register_spd for muxed child segments */
> 1304 __i801_register_spd(priv);
1305
1306 return NOTIFY_OK;
1307 }
1308
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-29 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 8:23 [PATCH] i2c: i801: Do not instantiate spd5118 under SPD Write Disable Yo-Jung (Leo) Lin
2025-05-28 23:59 ` kernel test robot [this message]
2025-05-29 3:54 ` Yo-Jung (Leo) Lin
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=202505290728.VsNgBfDO-lkp@intel.com \
--to=lkp@intel.com \
--cc=acelan.kao@canonical.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=leo.lin@canonical.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wsa-dev@sang-engineering.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