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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E7AA1C4167B for ; Wed, 6 Dec 2023 10:43:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377553AbjLFKnc (ORCPT ); Wed, 6 Dec 2023 05:43:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39324 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1377467AbjLFKn2 (ORCPT ); Wed, 6 Dec 2023 05:43:28 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2C56D18F; Wed, 6 Dec 2023 02:43:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1701859415; x=1733395415; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=3uXxhAR1Qiqm9bUuA39C2LKMCytRXXgtpDoxTsBQBYk=; b=klvo3B9QrweMtMEA5VnqXrs9BtT8A2ScXVCVIVGa0wlFhJbMSnElBM2s ogr387wxpRLWAnl4cw6TS4MNLVwWpdB2+d0AW6ExUqQzTlUf9GeYuwGJE Jgfq0fRzoBwBWtRpqwc5iFYKlRZywmUu44/wYw1wphiKrGpjGlCqSN1PJ TajrLT3h6soEG8vl+8KMCfQB73MkJdDjO+iO1BqEtxyoTS9hdbgnrwHF9 cihcURZe2SP7hUCZJuTcQLnNfPij7iWI3IXkbOrB6k8Xb0HRaUnyjJoHq wCqu90NXUO23KasOebG8wb2y87VPpDE987hl65jXEm+yfBgPb8T3Sw/KX A==; X-IronPort-AV: E=McAfee;i="6600,9927,10915"; a="880138" X-IronPort-AV: E=Sophos;i="6.04,254,1695711600"; d="scan'208";a="880138" Received: from orviesa002.jf.intel.com ([10.64.159.142]) by fmvoesa105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Dec 2023 02:43:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.04,254,1695711600"; d="scan'208";a="12657196" Received: from lkp-server02.sh.intel.com (HELO b07ab15da5fe) ([10.239.97.151]) by orviesa002.jf.intel.com with ESMTP; 06 Dec 2023 02:43:31 -0800 Received: from kbuild by b07ab15da5fe with local (Exim 4.96) (envelope-from ) id 1rApNI-000AeE-16; Wed, 06 Dec 2023 10:43:28 +0000 Date: Wed, 6 Dec 2023 18:42:38 +0800 From: kernel test robot To: gabriel.fernandez@foss.st.com, Michael Turquette , Stephen Boyd , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Maxime Coquelin , Alexandre Torgue , Philipp Zabel Cc: oe-kbuild-all@lists.linux.dev, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 2/5] clk: stm32mp1: use stm32mp13 reset driver Message-ID: <202312061848.1bvWrret-lkp@intel.com> References: <20231128164851.588315-3-gabriel.fernandez@foss.st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231128164851.588315-3-gabriel.fernandez@foss.st.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, kernel test robot noticed the following build warnings: [auto build test WARNING on atorgue-stm32/stm32-next] [also build test WARNING on clk/clk-next robh/for-next linus/master v6.7-rc4 next-20231206] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/gabriel-fernandez-foss-st-com/clk-stm32mp1-move-stm32mp1-clock-driver-into-stm32-directory/20231129-005157 base: https://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git stm32-next patch link: https://lore.kernel.org/r/20231128164851.588315-3-gabriel.fernandez%40foss.st.com patch subject: [PATCH v4 2/5] clk: stm32mp1: use stm32mp13 reset driver config: arm-randconfig-r132-20231201 (https://download.01.org/0day-ci/archive/20231206/202312061848.1bvWrret-lkp@intel.com/config) compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0 reproduce: (https://download.01.org/0day-ci/archive/20231206/202312061848.1bvWrret-lkp@intel.com/reproduce) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot | Closes: https://lore.kernel.org/oe-kbuild-all/202312061848.1bvWrret-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/clk/stm32/clk-stm32mp13.c:1516:29: sparse: sparse: symbol 'stm32mp13_reset_data' was not declared. Should it be static? -- >> drivers/clk/stm32/clk-stm32mp1.c:2148:29: sparse: sparse: symbol 'stm32mp1_reset_data' was not declared. Should it be static? vim +/stm32mp13_reset_data +1516 drivers/clk/stm32/clk-stm32mp13.c 1515 > 1516 struct clk_stm32_reset_data stm32mp13_reset_data = { 1517 .nr_lines = STM32MP1_RESET_ID_MASK, 1518 .clear_offset = RCC_CLR_OFFSET, 1519 }; 1520 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki