From: kernel test robot <lkp@intel.com>
To: Jiri Pirko <jiri@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jpirko-mlxsw:wip_dl_pfs_parent_v2 1/2] drivers/net/ethernet/mellanox/mlx5/core/sh_devlink.c:68:55: error: too many arguments to function call, expected 3, have 4
Date: Wed, 2 Apr 2025 13:01:42 +0800 [thread overview]
Message-ID: <202504021206.MNPtSadQ-lkp@intel.com> (raw)
tree: https://github.com/jpirko/linux_mlxsw wip_dl_pfs_parent_v2
head: 7f1e9aee5ae311c2f5c2296ce444f08dfa8b6ff0
commit: ef188d299e790f2dbfd6d5272e26fb1f1a543d4a [1/2] net/mlx5: Introduce shared devlink instance for PFs on same chip
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250402/202504021206.MNPtSadQ-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250402/202504021206.MNPtSadQ-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/202504021206.MNPtSadQ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/net/ethernet/mellanox/mlx5/core/sh_devlink.c:68:55: error: too many arguments to function call, expected 3, have 4
68 | faux_dev = faux_device_create(THIS_MODULE, sn, NULL, &mlx5_shd_faux_ops);
| ~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~
include/linux/device/faux.h:50:21: note: 'faux_device_create' declared here
50 | struct faux_device *faux_device_create(const char *name,
| ^ ~~~~~~~~~~~~~~~~~
51 | struct device *parent,
| ~~~~~~~~~~~~~~~~~~~~~~
52 | const struct faux_device_ops *faux_ops);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +68 drivers/net/ethernet/mellanox/mlx5/core/sh_devlink.c
62
63 static struct mlx5_shd *mlx5_shd_create(const char *sn)
64 {
65 struct faux_device *faux_dev;
66 struct mlx5_shd *shd;
67
> 68 faux_dev = faux_device_create(THIS_MODULE, sn, NULL, &mlx5_shd_faux_ops);
69 if (!faux_dev)
70 return NULL;
71 shd = faux_device_get_drvdata(faux_dev);
72 if (!shd)
73 return NULL;
74 list_add_tail(&shd->list, &shd_list);
75 shd->sn = sn;
76 INIT_LIST_HEAD(&shd->dev_list);
77 shd->faux_dev = faux_dev;
78 return shd;
79 }
80
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-02 5:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202504021206.MNPtSadQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=jiri@nvidia.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox