All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [nbd168-wireless:mt76 12/35] drivers/net/wireless/mediatek/mt76/mt7615/mcu.c:147:5: sparse: sparse: symbol 'mt7615_mcu_wait_response' was not declared. Should it be static?
Date: Wed, 18 Mar 2020 05:50:45 +0800	[thread overview]
Message-ID: <202003180547.u8iembWK%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

tree:   https://github.com/nbd168/wireless mt76
head:   f40ac0f3d3c0e2b17185e1707a3b4552e5187dd5
commit: 044a43256a357e43bb3669ed46346f273a8d3e9c [12/35] mt76: mt7615: introduce mt7615_mcu_wait_response
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-180-g0558317d-dirty
        git checkout 044a43256a357e43bb3669ed46346f273a8d3e9c
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> drivers/net/wireless/mediatek/mt76/mt7615/mcu.c:147:5: sparse: sparse: symbol 'mt7615_mcu_wait_response' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

             reply	other threads:[~2020-03-17 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 21:50 kbuild test robot [this message]
2020-03-17 21:51 ` [RFC PATCH nbd168-wireless] mt76: mt7615: mt7615_mcu_wait_response() can be static kbuild test robot
2020-03-17 21:58   ` Lorenzo Bianconi

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=202003180547.u8iembWK%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.