From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 5A3B4C433FE for ; Fri, 25 Feb 2022 18:35:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:Subject:Cc:To: From:Date:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=QsS6n2JGbYweEVI//OSTuYePHerrbUyqrWp8Nkj2+tg=; b=RSIpPrhVwEY+5a lzpi7Pq3YhMPZNOxhg+5nfhgn9I/lmMyEbVp/kFvelqrlgk77WrqgSuKj2s691UMwfZImOiRXrPXF xVsqum2LbQd4oMY7UaNV2lAOh6/ng5KdKA4OGY9tsQdjoOjj0B06SsrmOr1sg7XYXASkLl0f4+JAW KnUzqcddz9MVF6Hcgib3t+QFp9zHlMQj4VvkyxEuhm1Du9YFYccBBroB9iM0YIFuTugoTE0UvTMUE wpPqyZg3fo1GqZKhDErTwIOSQuqzR0yqGKbLiOywjevvwimSwHxWG7O+iey7ZufL8CFy17NR1RHcw e7hjoCJf5aVyH9DQ3IeQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nNfQJ-006dFt-Ie; Fri, 25 Feb 2022 18:34:37 +0000 Received: from mga01.intel.com ([192.55.52.88]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nNfQ8-006dES-CT for linux-arm-kernel@lists.infradead.org; Fri, 25 Feb 2022 18:34:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645814064; x=1677350064; h=date:from:to:cc:subject:message-id:mime-version; bh=yaOMKKur4WWS5E6368GwbAe47jpPtv4SWwbT5//UBiU=; b=V8XXpX8hM/KA6BIErpTbRX3kXFuQxmddh809g3iM6Mtlxm+4LQMmONo7 KglKKZChYHdcFlpHoLk3obg+VuVMmN8gpb7sm4ifRtdDMcd/aYsTxH0x5 1opxJOYFSQGOwU3To4VCNmUCRDIUHt3etp0FvBn6iyF1Hks9hfv7OiDIn nrp/0NPpeIcNtwlqhzNbXA7OrtGzsrf3DgcE9VE0iDzKBcxqzI3+RGvN7 p7F1B9t9MgPp323ZE985LChBf4eKQGyFDexlv8hrdFA27oKx08VCmwrR8 UHAh7otZ2+GmHPjpirtrHQ9Ie2QzuXbkvEBlws5J14Ahm/FNeriRxVoB2 g==; X-IronPort-AV: E=McAfee;i="6200,9189,10268"; a="277192515" X-IronPort-AV: E=Sophos;i="5.90,137,1643702400"; d="scan'208";a="277192515" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Feb 2022 10:34:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,136,1643702400"; d="scan'208";a="592570448" Received: from lkp-server01.sh.intel.com (HELO 788b1cd46f0d) ([10.239.97.150]) by fmsmga008.fm.intel.com with ESMTP; 25 Feb 2022 10:34:22 -0800 Received: from kbuild by 788b1cd46f0d with local (Exim 4.92) (envelope-from ) id 1nNfQ5-0004bt-LQ; Fri, 25 Feb 2022 18:34:21 +0000 Date: Sat, 26 Feb 2022 02:34:14 +0800 From: kernel test robot To: Linus Walleij Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org Subject: [linusw-nomadik:ux500-href-charging-v5.17-rc1 28/30] drivers/power/supply/samsung-sdi-battery.c:29:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb_l1m7flu' was not declared. Should it be static? Message-ID: <202202260125.d751ECgs-lkp@intel.com> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220225_103424_486377_6D1D2EFA X-CRM114-Status: GOOD ( 11.89 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org tree: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git ux500-href-charging-v5.17-rc1 head: ff2a9483749f5860407c6fb4798202b774978a81 commit: 77f450def23a94bcdea9a60f4df683461899158e [28/30] power: supply: Static data for Samsung batteries config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220226/202202260125.d751ECgs-lkp@intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce: # apt-get install sparse # sparse version: v0.6.4-dirty # https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git/commit/?id=77f450def23a94bcdea9a60f4df683461899158e git remote add linusw-nomadik https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-nomadik.git git fetch --no-tags linusw-nomadik ux500-href-charging-v5.17-rc1 git checkout 77f450def23a94bcdea9a60f4df683461899158e # save the config file to linux build tree mkdir build_dir make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/power/supply/ If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot sparse warnings: (new ones prefixed by >>) >> drivers/power/supply/samsung-sdi-battery.c:29:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb_l1m7flu' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:57:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb_l1m7flu' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:77:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb425161la' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:109:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb425161la' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:186:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb425161lu' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:218:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb425161lu' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:248:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb485159lu' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:275:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb485159lu' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:295:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb535151vu' was not declared. Should it be static? >> drivers/power/supply/samsung-sdi-battery.c:315:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb535151vu' was not declared. Should it be static? drivers/power/supply/samsung-sdi-battery.c:335:35: sparse: sparse: symbol 'samsung_vbat2res_discharging_eb585157lu' was not declared. Should it be static? drivers/power/supply/samsung-sdi-battery.c:405:35: sparse: sparse: symbol 'samsung_vbat2res_charging_eb585157lu' was not declared. Should it be static? drivers/power/supply/samsung-sdi-battery.c:617:46: sparse: sparse: symbol 'samsung_maint_charge_table' was not declared. Should it be static? drivers/power/supply/samsung-sdi-battery.c:632:28: sparse: sparse: symbol 'samsung_sdi_batteries' was not declared. Should it be static? Please review and possibly fold the followup patch. --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel