All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH nbd168-wireless] mt76: mt7615: mt7615_mcu_wait_response() can be static
Date: Wed, 18 Mar 2020 05:51:47 +0800	[thread overview]
Message-ID: <20200317215050.GA11834@4315b99345f9> (raw)
In-Reply-To: <202003180547.u8iembWK%lkp@intel.com>

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


Fixes: 044a43256a35 ("mt76: mt7615: introduce mt7615_mcu_wait_response")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 mcu.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/wireless/mediatek/mt76/mt7615/mcu.c b/drivers/net/wireless/mediatek/mt76/mt7615/mcu.c
index a4e971d7f6a779..15f57d355a7feb 100644
--- a/drivers/net/wireless/mediatek/mt76/mt7615/mcu.c
+++ b/drivers/net/wireless/mediatek/mt76/mt7615/mcu.c
@@ -144,7 +144,7 @@ mt7615_mcu_parse_response(struct mt7615_dev *dev, int cmd,
 	return ret;
 }
 
-int mt7615_mcu_wait_response(struct mt7615_dev *dev, int cmd, int seq)
+static int mt7615_mcu_wait_response(struct mt7615_dev *dev, int cmd, int seq)
 {
 	unsigned long expires = jiffies + 20 * HZ;
 	struct sk_buff *skb;

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 21:50 [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? kbuild test robot
2020-03-17 21:51 ` kbuild test robot [this message]
2020-03-17 21:58   ` [RFC PATCH nbd168-wireless] mt76: mt7615: mt7615_mcu_wait_response() can be static 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=20200317215050.GA11834@4315b99345f9 \
    --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.