From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [frank-w-bpi-r2-4.14:5.7-rc 14/45] drivers/soc/mediatek/mtk-pmic-wrap.c:2022:16: warning: no previous prototype for 'pwrap_node_to_regmap'
Date: Sun, 31 May 2020 23:10:13 +0800 [thread overview]
Message-ID: <202005312312.8tW0orQl%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]
tree: https://github.com/frank-w/BPI-R2-4.14 5.7-rc
head: 5e53b203ecc2519bfa641c2d3b98b16492865841
commit: 2f85f3115a33554612364e146c42be44e42ab101 [14/45] mt6625l: add changes outside driver dir
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 2f85f3115a33554612364e146c42be44e42ab101
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/soc/mediatek/mtk-pmic-wrap.c:2022:16: warning: no previous prototype for 'pwrap_node_to_regmap' [-Wmissing-prototypes]
2022 | struct regmap *pwrap_node_to_regmap(struct device_node *np)
| ^~~~~~~~~~~~~~~~~~~~
vim +/pwrap_node_to_regmap +2022 drivers/soc/mediatek/mtk-pmic-wrap.c
2021
> 2022 struct regmap *pwrap_node_to_regmap(struct device_node *np)
2023 {
2024 struct platform_device *pdev;
2025 struct pmic_wrapper *wrp;
2026 pdev = of_find_device_by_node(np);
2027 if (!pdev)
2028 return ERR_PTR(-ENODEV);
2029 wrp = platform_get_drvdata(pdev);
2030 return wrp->regmap;
2031 }
2032 EXPORT_SYMBOL_GPL(pwrap_node_to_regmap);
2033
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65506 bytes --]
reply other threads:[~2020-05-31 15:10 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=202005312312.8tW0orQl%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.