From: kernel test robot <lkp@intel.com>
To: Ryder Lee <ryder.lee@mediatek.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Felix Fietkau <nbd@nbd.name>
Subject: drivers/net/wireless/mediatek/mt76/mt7915/debugfs.c:365:6: warning: no previous prototype for 'mt7915_sta_add_debugfs'
Date: Mon, 13 Jul 2020 17:44:25 +0800 [thread overview]
Message-ID: <202007131721.1yYu7cOM%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
Hi Ryder,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 11ba468877bb23f28956a35e896356252d63c983
commit: ec9742a8f38ef69876e9f04be68d985c6bbb8f5f mt76: mt7915: add .sta_add_debugfs support
date: 9 weeks ago
config: i386-randconfig-r025-20200713 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce (this is a W=1 build):
git checkout ec9742a8f38ef69876e9f04be68d985c6bbb8f5f
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/net/wireless/mediatek/mt76/mt7915/debugfs.c:365:6: warning: no previous prototype for 'mt7915_sta_add_debugfs' [-Wmissing-prototypes]
365 | void mt7915_sta_add_debugfs(struct ieee80211_hw *hw, struct ieee80211_vif *vif,
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/mt7915_sta_add_debugfs +365 drivers/net/wireless/mediatek/mt76/mt7915/debugfs.c
364
> 365 void mt7915_sta_add_debugfs(struct ieee80211_hw *hw, struct ieee80211_vif *vif,
---
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: 34681 bytes --]
next reply other threads:[~2020-07-13 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 9:44 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-12 9:31 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=202007131721.1yYu7cOM%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.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
all inboxes | Powered by JetHome®