All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Richard Acayan <mailingradian@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Linus Walleij <linusw@kernel.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Dmitry Baryshkov <lumag@kernel.org>
Subject: [linux-next:master 12114/12445] drivers/pinctrl/qcom/pinctrl-sdm670-lpass-lpi.c:83:27: sparse: sparse: symbol 'sdm670_lpi_pinctrl_groups' was not declared. Should it be static?
Date: Wed, 08 Apr 2026 09:08:31 +0800	[thread overview]
Message-ID: <202604080950.Mvm8aN0a-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   f3e6330d7fe42b204af05a2dbc68b379e0ad179e
commit: 9826035a75da609ac2424c97915d6fe5b836ee65 [12114/12445] pinctrl: qcom: add sdm670 lpi tlmm
config: hexagon-randconfig-r132-20260408 (https://download.01.org/0day-ci/archive/20260408/202604080950.Mvm8aN0a-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260408/202604080950.Mvm8aN0a-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 <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202604080950.Mvm8aN0a-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/pinctrl/qcom/pinctrl-sdm670-lpass-lpi.c:83:27: sparse: sparse: symbol 'sdm670_lpi_pinctrl_groups' was not declared. Should it be static?
>> drivers/pinctrl/qcom/pinctrl-sdm670-lpass-lpi.c:118:27: sparse: sparse: symbol 'sdm670_lpi_pinctrl_functions' was not declared. Should it be static?

vim +/sdm670_lpi_pinctrl_groups +83 drivers/pinctrl/qcom/pinctrl-sdm670-lpass-lpi.c

    82	
  > 83	const struct lpi_pingroup sdm670_lpi_pinctrl_groups[] = {
    84		LPI_PINGROUP(0, LPI_NO_SLEW, _, _, _, _),
    85		LPI_PINGROUP(1, LPI_NO_SLEW, _, _, _, _),
    86		LPI_PINGROUP(2, LPI_NO_SLEW, _, _, _, _),
    87		LPI_PINGROUP(3, LPI_NO_SLEW, _, _, _, _),
    88		LPI_PINGROUP(4, LPI_NO_SLEW, _, _, _, _),
    89		LPI_PINGROUP(5, LPI_NO_SLEW, _, _, _, _),
    90		LPI_PINGROUP(6, LPI_NO_SLEW, _, _, _, _),
    91		LPI_PINGROUP(7, LPI_NO_SLEW, _, _, _, _),
    92		LPI_PINGROUP(8, LPI_NO_SLEW, _, _, i2s1_clk, _),
    93		LPI_PINGROUP(9, LPI_NO_SLEW, _, _, i2s1_ws, _),
    94		LPI_PINGROUP(10, LPI_NO_SLEW, _, _, _, i2s1_data),
    95		LPI_PINGROUP(11, LPI_NO_SLEW, _, i2s1_data, _, _),
    96		LPI_PINGROUP(12, LPI_NO_SLEW, _, _, _, _),
    97		LPI_PINGROUP(13, LPI_NO_SLEW, _, _, _, _),
    98		LPI_PINGROUP(14, LPI_NO_SLEW, _, _, _, _),
    99		LPI_PINGROUP(15, LPI_NO_SLEW, _, _, _, _),
   100		LPI_PINGROUP(16, LPI_NO_SLEW, _, _, _, _),
   101		LPI_PINGROUP(17, LPI_NO_SLEW, _, _, _, _),
   102		LPI_PINGROUP(18, LPI_NO_SLEW, _, slimbus_clk, _, _),
   103		LPI_PINGROUP(19, LPI_NO_SLEW, mclk0, _, pdm_sync, _),
   104		LPI_PINGROUP(20, LPI_NO_SLEW, _, pdm_tx, _, _),
   105		LPI_PINGROUP(21, LPI_NO_SLEW, _, pdm_rx, _, _),
   106		LPI_PINGROUP(22, LPI_NO_SLEW, _, comp_rx, _, _),
   107		LPI_PINGROUP(23, LPI_NO_SLEW, pdm_rx, _, _, _),
   108		LPI_PINGROUP(24, LPI_NO_SLEW, comp_rx, _, _, _),
   109		LPI_PINGROUP(25, LPI_NO_SLEW, pdm_rx, _, _, _),
   110		LPI_PINGROUP(26, LPI_NO_SLEW, dmic1_clk, _, _, _),
   111		LPI_PINGROUP(27, LPI_NO_SLEW, dmic1_data, _, _, _),
   112		LPI_PINGROUP(28, LPI_NO_SLEW, dmic2_clk, _, _, _),
   113		LPI_PINGROUP(29, LPI_NO_SLEW, dmic2_data, lpi_cdc_rst, _, _),
   114		LPI_PINGROUP(30, LPI_NO_SLEW, _, _, _, _),
   115		LPI_PINGROUP(31, LPI_NO_SLEW, _, _, _, _),
   116	};
   117	
 > 118	const struct lpi_function sdm670_lpi_pinctrl_functions[] = {
   119		LPI_FUNCTION(comp_rx),
   120		LPI_FUNCTION(dmic1_clk),
   121		LPI_FUNCTION(dmic1_data),
   122		LPI_FUNCTION(dmic2_clk),
   123		LPI_FUNCTION(dmic2_data),
   124		LPI_FUNCTION(i2s1_clk),
   125		LPI_FUNCTION(i2s1_data),
   126		LPI_FUNCTION(i2s1_ws),
   127		LPI_FUNCTION(lpi_cdc_rst),
   128		LPI_FUNCTION(mclk0),
   129		LPI_FUNCTION(pdm_tx),
   130		LPI_FUNCTION(pdm_rx),
   131		LPI_FUNCTION(pdm_sync),
   132		LPI_FUNCTION(slimbus_clk),
   133	};
   134	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-04-08  1:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202604080950.Mvm8aN0a-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linusw@kernel.org \
    --cc=lumag@kernel.org \
    --cc=mailingradian@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.