summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChen Jiahao <chenjiahao16@huawei.com>2022-10-19 23:32:12 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-01-18 11:30:02 +0100
commitd1911dc5231678293f2f0e3a5b2e9bc503870910 (patch)
treebd7137070f5c3c44278aa6f208067563123eb6fe
parent839feaae15c40aa29ad3c2d559c756e4a1f26da3 (diff)
downloadlinux-stable-d1911dc5231678293f2f0e3a5b2e9bc503870910.tar.gz
linux-stable-d1911dc5231678293f2f0e3a5b2e9bc503870910.tar.bz2
linux-stable-d1911dc5231678293f2f0e3a5b2e9bc503870910.zip
drivers: soc: ti: knav_qmss_queue: Mark knav_acc_firmwares as static
[ Upstream commit adf85adc2a7199b41e7a4da083bd17274a3d6969 ] There is a sparse warning shown below: drivers/soc/ti/knav_qmss_queue.c:70:12: warning: symbol 'knav_acc_firmwares' was not declared. Should it be static? Since 'knav_acc_firmwares' is only called within knav_qmss_queue.c, mark it as static to fix the warning. Fixes: 96ee19becc3b ("soc: ti: add firmware file name as part of the driver") Signed-off-by: Chen Jiahao <chenjiahao16@huawei.com> Signed-off-by: Nishanth Menon <nm@ti.com> Link: https://lore.kernel.org/r/20221019153212.72350-1-chenjiahao16@huawei.com Signed-off-by: Sasha Levin <sashal@kernel.org>
-rw-r--r--drivers/soc/ti/knav_qmss_queue.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/soc/ti/knav_qmss_queue.c b/drivers/soc/ti/knav_qmss_queue.c
index 9f5ce52e6c16..b264c36b2c0e 100644
--- a/drivers/soc/ti/knav_qmss_queue.c
+++ b/drivers/soc/ti/knav_qmss_queue.c
@@ -72,7 +72,7 @@ static DEFINE_MUTEX(knav_dev_lock);
* Newest followed by older ones. Search is done from start of the array
* until a firmware file is found.
*/
-const char *knav_acc_firmwares[] = {"ks2_qmss_pdsp_acc48.bin"};
+static const char * const knav_acc_firmwares[] = {"ks2_qmss_pdsp_acc48.bin"};
static bool device_ready;
bool knav_qmss_device_ready(void)