From: kbuild test robot <lkp@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kbuild-all@lists.01.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: [vhost:linux-next 4/11] drivers/net/ethernet/mellanox/mlx4/en_netdev.c:1376:12: error: 'tx_ring' undeclared; did you mean 'en_print'?
Date: Wed, 4 Dec 2019 03:56:08 +0800 [thread overview]
Message-ID: <201912040307.yiR0Q7Mk%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2813 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
head: b5fe11663b48ca267829b34a65b4133e4e34c993
commit: 1f4098ea671b092af3806789d89e278e1f08e222 [4/11] mlx4: use new txqueue timeout argument
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 1f4098ea671b092af3806789d89e278e1f08e222
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=sparc64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/net/ethernet/mellanox/mlx4/en_netdev.c:50:0:
drivers/net/ethernet/mellanox/mlx4/en_netdev.c: In function 'mlx4_en_tx_timeout':
>> drivers/net/ethernet/mellanox/mlx4/en_netdev.c:1376:12: error: 'tx_ring' undeclared (first use in this function); did you mean 'en_print'?
txqueue, tx_ring->qpn, tx_ring->sp_cqn,
^
drivers/net/ethernet/mellanox/mlx4/mlx4_en.h:830:41: note: in definition of macro 'en_warn'
en_print(KERN_WARNING, priv, format, ##__VA_ARGS__)
^~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx4/en_netdev.c:1376:12: note: each undeclared identifier is reported only once for each function it appears in
txqueue, tx_ring->qpn, tx_ring->sp_cqn,
^
drivers/net/ethernet/mellanox/mlx4/mlx4_en.h:830:41: note: in definition of macro 'en_warn'
en_print(KERN_WARNING, priv, format, ##__VA_ARGS__)
^~~~~~~~~~~
drivers/net/ethernet/mellanox/mlx4/en_netdev.c:1370:6: warning: unused variable 'i' [-Wunused-variable]
int i;
^
vim +1376 drivers/net/ethernet/mellanox/mlx4/en_netdev.c
1365
1366 static void mlx4_en_tx_timeout(struct net_device *dev, unsigned int txqueue)
1367 {
1368 struct mlx4_en_priv *priv = netdev_priv(dev);
1369 struct mlx4_en_dev *mdev = priv->mdev;
1370 int i;
1371
1372 if (netif_msg_timer(priv))
1373 en_warn(priv, "Tx timeout called on port:%d\n", priv->port);
1374
1375 en_warn(priv, "TX timeout on queue: %d, QP: 0x%x, CQ: 0x%x, Cons: 0x%x, Prod: 0x%x\n",
> 1376 txqueue, tx_ring->qpn, tx_ring->sp_cqn,
1377 tx_ring->cons, tx_ring->prod);
1378
1379 priv->port_stats.tx_timeout++;
1380 en_dbg(DRV, priv, "Scheduling watchdog\n");
1381 queue_work(mdev->workqueue, &priv->watchdog_task);
1382 }
1383
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 59122 bytes --]
reply other threads:[~2019-12-03 19:56 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=201912040307.yiR0Q7Mk%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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