From: kernel test robot <lkp@intel.com>
To: Luo bin <luobin9@huawei.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/net/ethernet/huawei/hinic/hinic_main.c:796:25: sparse: sparse: cast to restricted __be16
Date: Wed, 2 Sep 2020 08:40:38 +0800 [thread overview]
Message-ID: <202009020835.dmWcHHcX%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2662 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b765a32a2e9170702467747e290614be072c4f76
commit: 1f62cfa19a619f82c098468660b7950477101d45 hinic: add net_device_ops associated with vf
date: 4 months ago
config: i386-randconfig-s001-20200902 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-191-g10164920-dirty
git checkout 1f62cfa19a619f82c098468660b7950477101d45
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/huawei/hinic/hinic_main.c:796:25: sparse: sparse: cast to restricted __be16
>> drivers/net/ethernet/huawei/hinic/hinic_main.c:796:25: sparse: sparse: cast to restricted __be16
>> drivers/net/ethernet/huawei/hinic/hinic_main.c:796:25: sparse: sparse: cast to restricted __be16
>> drivers/net/ethernet/huawei/hinic/hinic_main.c:796:25: sparse: sparse: cast to restricted __be16
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1f62cfa19a619f82c098468660b7950477101d45
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 1f62cfa19a619f82c098468660b7950477101d45
vim +796 drivers/net/ethernet/huawei/hinic/hinic_main.c
778
779 static void hinic_tx_timeout(struct net_device *netdev, unsigned int txqueue)
780 {
781 struct hinic_dev *nic_dev = netdev_priv(netdev);
782 u16 sw_pi, hw_ci, sw_ci;
783 struct hinic_sq *sq;
784 u16 num_sqs, q_id;
785
786 num_sqs = hinic_hwdev_num_qps(nic_dev->hwdev);
787
788 netif_err(nic_dev, drv, netdev, "Tx timeout\n");
789
790 for (q_id = 0; q_id < num_sqs; q_id++) {
791 if (!netif_xmit_stopped(netdev_get_tx_queue(netdev, q_id)))
792 continue;
793
794 sq = hinic_hwdev_get_sq(nic_dev->hwdev, q_id);
795 sw_pi = atomic_read(&sq->wq->prod_idx) & sq->wq->mask;
> 796 hw_ci = be16_to_cpu(*(u16 *)(sq->hw_ci_addr)) & sq->wq->mask;
797 sw_ci = atomic_read(&sq->wq->cons_idx) & sq->wq->mask;
798 netif_err(nic_dev, drv, netdev, "Txq%d: sw_pi: %d, hw_ci: %d, sw_ci: %d, napi->state: 0x%lx\n",
799 q_id, sw_pi, hw_ci, sw_ci,
800 nic_dev->txqs[q_id].napi.state);
801 }
802 }
803
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 44513 bytes --]
next reply other threads:[~2020-09-02 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 0:40 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-01 11:12 kernel test robot
2020-10-03 4:15 kernel test robot
2020-06-06 20:13 kernel test robot
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=202009020835.dmWcHHcX%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luobin9@huawei.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
Powered by JetHome