From: kbuild test robot <lkp@intel.com>
To: Pascal PAILLET-LME <p.paillet@st.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
kbuild-all@01.org, Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: [regulator:for-next 103/105] drivers/regulator/stm32-pwr.c:35:5: sparse: symbol 'ready_mask_table' was not declared. Should it be static?
Date: Tue, 16 Apr 2019 00:52:38 +0800 [thread overview]
Message-ID: <201904160046.ggavw2OV%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
head: 598387d3ce4bd982272a2bc990dfad6d67d20efd
commit: 6cdae8173f6771977c3863bac7f1455c96bb1f6e [103/105] regulator: Add support for stm32 power regulators
reproduce:
# apt-get install sparse
git checkout 6cdae8173f6771977c3863bac7f1455c96bb1f6e
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
sparse warnings: (new ones prefixed by >>)
>> drivers/regulator/stm32-pwr.c:35:5: sparse: symbol 'ready_mask_table' was not declared. Should it be static?
>> drivers/regulator/stm32-pwr.c:47:5: sparse: symbol 'stm32_pwr_reg_is_ready' was not declared. Should it be static?
>> drivers/regulator/stm32-pwr.c:57:5: sparse: symbol 'stm32_pwr_reg_is_enabled' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Pascal PAILLET-LME <p.paillet@st.com>
Cc: kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: [regulator:for-next 103/105] drivers/regulator/stm32-pwr.c:35:5: sparse: symbol 'ready_mask_table' was not declared. Should it be static?
Date: Tue, 16 Apr 2019 00:52:38 +0800 [thread overview]
Message-ID: <201904160046.ggavw2OV%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
head: 598387d3ce4bd982272a2bc990dfad6d67d20efd
commit: 6cdae8173f6771977c3863bac7f1455c96bb1f6e [103/105] regulator: Add support for stm32 power regulators
reproduce:
# apt-get install sparse
git checkout 6cdae8173f6771977c3863bac7f1455c96bb1f6e
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
sparse warnings: (new ones prefixed by >>)
>> drivers/regulator/stm32-pwr.c:35:5: sparse: symbol 'ready_mask_table' was not declared. Should it be static?
>> drivers/regulator/stm32-pwr.c:47:5: sparse: symbol 'stm32_pwr_reg_is_ready' was not declared. Should it be static?
>> drivers/regulator/stm32-pwr.c:57:5: sparse: symbol 'stm32_pwr_reg_is_enabled' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-04-15 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 16:52 kbuild test robot [this message]
2019-04-15 16:52 ` [regulator:for-next 103/105] drivers/regulator/stm32-pwr.c:35:5: sparse: symbol 'ready_mask_table' was not declared. Should it be static? kbuild test robot
2019-04-15 16:52 ` [RFC PATCH regulator] regulator: ready_mask_table[] can be static kbuild test robot
2019-04-15 16:52 ` kbuild test robot
2019-04-16 15:32 ` Pascal PAILLET-LME
2019-04-16 15:32 ` Pascal PAILLET-LME
2019-04-17 16:42 ` Applied "regulator: ready_mask_table[] can be static" to the regulator tree Mark Brown
2019-04-17 16:42 ` Mark Brown
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=201904160046.ggavw2OV%lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.torgue@st.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.paillet@st.com \
/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.