From: kernel test robot <lkp@intel.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>,
andi.shyti@kernel.org, jarkko.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, jsd@semihalf.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, rmk+kernel@armlinux.org.uk,
piotr.raczynski@intel.com, andrew@lunn.ch,
linux-i2c@vger.kernel.org, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
mengyuanlou@net-swift.com, duanqiangwen@net-swift.com,
Jiawen Wu <jiawenwu@trustnetic.com>,
stable@vger.kernel.org
Subject: Re: [PATCH net 2/3] i2c: designware: add device private data passing to lock functions
Date: Thu, 29 Aug 2024 13:16:55 +0800 [thread overview]
Message-ID: <202408291212.L5DejDpz-lkp@intel.com> (raw)
In-Reply-To: <20240823030242.3083528-3-jiawenwu@trustnetic.com>
Hi Jiawen,
kernel test robot noticed the following build errors:
[auto build test ERROR on net/main]
url: https://github.com/intel-lab-lkp/linux/commits/Jiawen-Wu/net-txgbe-add-IO-address-in-I2C-platform-device-data/20240826-122232
base: net/main
patch link: https://lore.kernel.org/r/20240823030242.3083528-3-jiawenwu%40trustnetic.com
patch subject: [PATCH net 2/3] i2c: designware: add device private data passing to lock functions
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240829/202408291212.L5DejDpz-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240829/202408291212.L5DejDpz-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/202408291212.L5DejDpz-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/i2c/busses/i2c-designware-amdpsp.c:246:22: error: too few arguments to function call, single argument 'dev' was not specified
246 | psp_acquire_i2c_bus();
| ~~~~~~~~~~~~~~~~~~~ ^
drivers/i2c/busses/i2c-designware-amdpsp.c:170:12: note: 'psp_acquire_i2c_bus' declared here
170 | static int psp_acquire_i2c_bus(struct dw_i2c_dev *dev)
| ^ ~~~~~~~~~~~~~~~~~~~~~~
drivers/i2c/busses/i2c-designware-amdpsp.c:259:22: error: too few arguments to function call, single argument 'dev' was not specified
259 | psp_acquire_i2c_bus();
| ~~~~~~~~~~~~~~~~~~~ ^
drivers/i2c/busses/i2c-designware-amdpsp.c:170:12: note: 'psp_acquire_i2c_bus' declared here
170 | static int psp_acquire_i2c_bus(struct dw_i2c_dev *dev)
| ^ ~~~~~~~~~~~~~~~~~~~~~~
drivers/i2c/busses/i2c-designware-amdpsp.c:267:22: error: too few arguments to function call, single argument 'dev' was not specified
267 | psp_release_i2c_bus();
| ~~~~~~~~~~~~~~~~~~~ ^
drivers/i2c/busses/i2c-designware-amdpsp.c:209:13: note: 'psp_release_i2c_bus' declared here
209 | static void psp_release_i2c_bus(struct dw_i2c_dev *dev)
| ^ ~~~~~~~~~~~~~~~~~~~~~~
3 errors generated.
vim +/dev +246 drivers/i2c/busses/i2c-designware-amdpsp.c
78d5e9e299e31bc Jan Dabros 2022-02-08 235
78d5e9e299e31bc Jan Dabros 2022-02-08 236 /*
78d5e9e299e31bc Jan Dabros 2022-02-08 237 * Locking methods are based on the default implementation from
78d5e9e299e31bc Jan Dabros 2022-02-08 238 * drivers/i2c/i2c-core-base.c, but with psp acquire and release operations
78d5e9e299e31bc Jan Dabros 2022-02-08 239 * added. With this in place we can ensure that i2c clients on the bus shared
78d5e9e299e31bc Jan Dabros 2022-02-08 240 * with psp are able to lock HW access to the bus for arbitrary number of
78d5e9e299e31bc Jan Dabros 2022-02-08 241 * operations - that is e.g. write-wait-read.
78d5e9e299e31bc Jan Dabros 2022-02-08 242 */
78d5e9e299e31bc Jan Dabros 2022-02-08 243 static void i2c_adapter_dw_psp_lock_bus(struct i2c_adapter *adapter,
78d5e9e299e31bc Jan Dabros 2022-02-08 244 unsigned int flags)
78d5e9e299e31bc Jan Dabros 2022-02-08 245 {
78d5e9e299e31bc Jan Dabros 2022-02-08 @246 psp_acquire_i2c_bus();
78d5e9e299e31bc Jan Dabros 2022-02-08 247 rt_mutex_lock_nested(&adapter->bus_lock, i2c_adapter_depth(adapter));
78d5e9e299e31bc Jan Dabros 2022-02-08 248 }
78d5e9e299e31bc Jan Dabros 2022-02-08 249
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-29 5:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 3:02 [PATCH net 0/3] Add I2C bus lock for Wangxun Jiawen Wu
2024-08-23 3:02 ` [PATCH net 1/3] net: txgbe: add IO address in I2C platform device data Jiawen Wu
2024-08-23 14:14 ` Andy Shevchenko
2024-08-23 3:02 ` [PATCH net 2/3] i2c: designware: add device private data passing to lock functions Jiawen Wu
2024-08-23 14:06 ` Andy Shevchenko
2024-08-27 13:24 ` Paolo Abeni
2024-08-29 5:16 ` kernel test robot [this message]
2024-08-23 3:02 ` [PATCH net 3/3] i2c: designware: support hardware lock for Wangxun 10Gb NIC Jiawen Wu
2024-08-23 14:13 ` Andy Shevchenko
2024-08-29 9:15 ` Jiawen Wu
2024-08-29 10:59 ` 'Andy Shevchenko'
2024-08-23 11:04 ` [PATCH net 0/3] Add I2C bus lock for Wangxun Jarkko Nikula
2024-08-27 2:26 ` Jiawen Wu
2024-08-26 1:32 ` Andrew Lunn
2024-08-26 2:04 ` Jiawen Wu
2024-08-26 2:33 ` Andrew Lunn
2024-08-27 2:21 ` Jiawen Wu
2024-08-27 12:18 ` Andrew Lunn
2024-08-29 6:40 ` Jiawen Wu
2024-08-29 15:27 ` Andrew Lunn
2024-09-03 6:31 ` Jiawen Wu
2024-09-03 12:45 ` Andrew Lunn
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=202408291212.L5DejDpz-lkp@intel.com \
--to=lkp@intel.com \
--cc=andi.shyti@kernel.org \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=duanqiangwen@net-swift.com \
--cc=edumazet@google.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jiawenwu@trustnetic.com \
--cc=jsd@semihalf.com \
--cc=kuba@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mengyuanlou@net-swift.com \
--cc=mika.westerberg@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=piotr.raczynski@intel.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).