From: kbuild test robot <lkp@intel.com>
To: s.gottschall@dd-wrt.com
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
Sebastian Gottschall <s.gottschall@newmedia-net.de>,
kvalo@codeaurora.org, kbuild-all@01.org
Subject: [RFC PATCH] ath10k: ath10k_register_gpio_chip() can be static
Date: Sat, 24 Feb 2018 22:58:43 +0800 [thread overview]
Message-ID: <20180224145843.GA55309@roam> (raw)
In-Reply-To: <20180222111534.31047-1-s.gottschall@dd-wrt.com>
Fixes: 35b91f175b35 ("ath10k: add LED and GPIO controlling support for various chipsets")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
gpio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath10k/gpio.c b/drivers/net/wireless/ath/ath10k/gpio.c
index a760319..e9ce44b 100644
--- a/drivers/net/wireless/ath/ath10k/gpio.c
+++ b/drivers/net/wireless/ath/ath10k/gpio.c
@@ -81,7 +81,7 @@ static void ath10k_gpio_pin_set(struct gpio_chip *chip, unsigned offset,
}
/* register GPIO chip */
-int ath10k_register_gpio_chip(struct ath10k *ar)
+static int ath10k_register_gpio_chip(struct ath10k *ar)
{
struct ath10k_gpiocontrol *gpio = ar->gpio;
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: s.gottschall@dd-wrt.com
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org,
kvalo@codeaurora.org, ath10k@lists.infradead.org,
Sebastian Gottschall <s.gottschall@newmedia-net.de>,
Sebastian Gottschall <s.gottschall@dd-wrt.com>
Subject: [RFC PATCH] ath10k: ath10k_register_gpio_chip() can be static
Date: Sat, 24 Feb 2018 22:58:43 +0800 [thread overview]
Message-ID: <20180224145843.GA55309@roam> (raw)
In-Reply-To: <20180222111534.31047-1-s.gottschall@dd-wrt.com>
Fixes: 35b91f175b35 ("ath10k: add LED and GPIO controlling support for various chipsets")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
gpio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath10k/gpio.c b/drivers/net/wireless/ath/ath10k/gpio.c
index a760319..e9ce44b 100644
--- a/drivers/net/wireless/ath/ath10k/gpio.c
+++ b/drivers/net/wireless/ath/ath10k/gpio.c
@@ -81,7 +81,7 @@ static void ath10k_gpio_pin_set(struct gpio_chip *chip, unsigned offset,
}
/* register GPIO chip */
-int ath10k_register_gpio_chip(struct ath10k *ar)
+static int ath10k_register_gpio_chip(struct ath10k *ar)
{
struct ath10k_gpiocontrol *gpio = ar->gpio;
next prev parent reply other threads:[~2018-02-24 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 11:15 [PATCH v9] ath10k: add LED and GPIO controlling support for various chipsets s.gottschall
2018-02-22 11:15 ` s.gottschall
2018-02-22 22:17 ` Steve deRosier
2018-02-22 22:17 ` Steve deRosier
2018-02-23 2:09 ` Sebastian Gottschall
2018-02-23 2:09 ` Sebastian Gottschall
2018-02-23 3:20 ` Steve deRosier
2018-02-23 3:20 ` Steve deRosier
2018-02-24 14:58 ` kbuild test robot
2018-02-24 14:58 ` kbuild test robot
2018-02-24 14:58 ` kbuild test robot [this message]
2018-02-24 14:58 ` [RFC PATCH] ath10k: ath10k_register_gpio_chip() can be static kbuild 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=20180224145843.GA55309@roam \
--to=lkp@intel.com \
--cc=ath10k@lists.infradead.org \
--cc=kbuild-all@01.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@dd-wrt.com \
--cc=s.gottschall@newmedia-net.de \
/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.