Message ID | 20221019153212.72350-1-chenjiahao16@huawei.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4ac7:0:0:0:0:0 with SMTP id y7csp182989wrs; Wed, 19 Oct 2022 00:43:44 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4Qj9ANGK4PgYHiQs64aMUSDeHKCcHDU9NrujtJ5iAJbEDR7blIsZs3DJjZpVudVxOy7Izm X-Received: by 2002:a65:4084:0:b0:463:aa4:49cf with SMTP id t4-20020a654084000000b004630aa449cfmr6045870pgp.164.1666165423933; Wed, 19 Oct 2022 00:43:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666165423; cv=none; d=google.com; s=arc-20160816; b=zUfxyj2Ari9UbKBOF5fv1+V8E+eUA6jPxnBW5wL+Slo+QSpKG5Fae9WGRoHM7N9fAi bBqGhNKlLaMs/gcASGUvF89D5UfoNEwvDnr8O2yiEusLsCx9dU2x0v+fVXyTUumj1Cci iVDdGTZ34q0EWUBld6gIOl0UToQGzdgKj3hopxPMNKdL+rhX5t78Xx/IPioHuUAZFiDO dRL4v5SiVAadPYQqXQucQApmdFp2U1hig9raMQbtSJD62od1gz9jWujYNSkUjqcNUvYf iv2D5juatnln8cscOcEVXXnulJDnrYY8mbcT+0L7UKyIHRqeV8TEHk6J//cL4H+iDoAy jXEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:to:from; bh=71GabrVX18v6LNzI2lyzeA4XnjRM2HsuxKXucptHXpM=; b=uprOIPRUplitf+VaBfvtTC3y357P1mxvWk/SWgRYzBLGJkKka38w8uorbif9vzm8Fc 4xKqwLdUXzTFfJujXHU6EG7H17VPLNzlPjg5Gl5RqqeI7drOq2l9FighzahQdcWoZqNC RLSbIG5HnaY4SJ53cUKmK+VUGlXQcYFU2MXp2A6hNCiEqLKbALe1prABsDChtGuVLZiS Rd07Mpz+tHDN2mr+I9Wd+XNihHQluJfseVXLJmPbg2NjwbCYNtPRUDG6Fu5rZgOsvMcO zxI+X2lMMffXJaz/VNnLQAwBzZ1bK0C7chSOCm5t6lRVm332TwwtnmxPJaCBc5vXwQ03 mH9g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v12-20020a63d54c000000b00453d2790c49si16372185pgi.11.2022.10.19.00.43.31; Wed, 19 Oct 2022 00:43:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230009AbiJSHdE (ORCPT <rfc822;samuel.l.nystrom@gmail.com> + 99 others); Wed, 19 Oct 2022 03:33:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41660 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229755AbiJSHdC (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 19 Oct 2022 03:33:02 -0400 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 17A4961121 for <linux-kernel@vger.kernel.org>; Wed, 19 Oct 2022 00:33:00 -0700 (PDT) Received: from dggpemm500021.china.huawei.com (unknown [172.30.72.55]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4MsjBC1rQ1zHv8G; Wed, 19 Oct 2022 15:32:51 +0800 (CST) Received: from dggpemm500016.china.huawei.com (7.185.36.25) by dggpemm500021.china.huawei.com (7.185.36.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Wed, 19 Oct 2022 15:32:33 +0800 Received: from huawei.com (10.67.174.205) by dggpemm500016.china.huawei.com (7.185.36.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Wed, 19 Oct 2022 15:32:33 +0800 From: Chen Jiahao <chenjiahao16@huawei.com> To: <nm@ti.com>, <ssantosh@kernel.org>, <arnd@arndb.de>, <m-karicheri2@ti.com>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org> Subject: [PATCH -next v2] drivers: soc: ti: mark knav_acc_firmwares as static Date: Wed, 19 Oct 2022 23:32:12 +0800 Message-ID: <20221019153212.72350-1-chenjiahao16@huawei.com> X-Mailer: git-send-email 2.31.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.67.174.205] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To dggpemm500016.china.huawei.com (7.185.36.25) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,DATE_IN_FUTURE_06_12, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1746975323084488061?= X-GMAIL-MSGID: =?utf-8?q?1747101075581234866?= |
Series |
[-next,v2] drivers: soc: ti: mark knav_acc_firmwares as static
|
|
Commit Message
Chen Jiahao
Oct. 19, 2022, 3:32 p.m. UTC
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>
---
drivers/soc/ti/knav_qmss_queue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
Hi Chen Jiahao, On Wed, 19 Oct 2022 23:32:12 +0800, Chen Jiahao wrote: > 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. > > [...] I have applied the following to branch ti-drivers-soc-next on [1]. Thank you! [1/1] drivers: soc: ti: mark knav_acc_firmwares as static commit: adf85adc2a7199b41e7a4da083bd17274a3d6969 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. [1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
diff --git a/drivers/soc/ti/knav_qmss_queue.c b/drivers/soc/ti/knav_qmss_queue.c index 92af7d1b6f5b..16a6d530a0d4 100644 --- a/drivers/soc/ti/knav_qmss_queue.c +++ b/drivers/soc/ti/knav_qmss_queue.c @@ -67,7 +67,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)