From: kernel test robot <lkp@intel.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [miquelraynal:nvmem-layouts-and-of-cleanup 20/57] drivers/nvmem/core.c:770:9: error: implicit declaration of function 'of_device_node_request_module'
Date: Wed, 8 Mar 2023 07:26:57 +0800 [thread overview]
Message-ID: <202303080730.Qtk3lUUd-lkp@intel.com> (raw)
tree: https://github.com/miquelraynal/linux-0day.git nvmem-layouts-and-of-cleanup
head: d8752324726fdde6bb205a5aa95ae8ff7d84eff7
commit: b3a67512c995dbf8f71e14e7df1278ee7c6d26ca [20/57] nvmem: core: request layout modules loading
config: riscv-randconfig-r042-20230305 (https://download.01.org/0day-ci/archive/20230308/202303080730.Qtk3lUUd-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.1.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
# https://github.com/miquelraynal/linux-0day/commit/b3a67512c995dbf8f71e14e7df1278ee7c6d26ca
git remote add miquelraynal https://github.com/miquelraynal/linux-0day.git
git fetch --no-tags miquelraynal nvmem-layouts-and-of-cleanup
git checkout b3a67512c995dbf8f71e14e7df1278ee7c6d26ca
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=riscv olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303080730.Qtk3lUUd-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/nvmem/core.c: In function 'nvmem_layout_get':
>> drivers/nvmem/core.c:770:9: error: implicit declaration of function 'of_device_node_request_module' [-Werror=implicit-function-declaration]
770 | of_device_node_request_module(layout_np);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/of_device_node_request_module +770 drivers/nvmem/core.c
755
756 static struct nvmem_layout *nvmem_layout_get(struct nvmem_device *nvmem)
757 {
758 struct device_node *layout_np, *np = nvmem->dev.of_node;
759 struct nvmem_layout *l, *layout = ERR_PTR(-EPROBE_DEFER);
760
761 layout_np = of_get_child_by_name(np, "nvmem-layout");
762 if (!layout_np)
763 return NULL;
764
765 /*
766 * In case the nvmem device was built-in while the layout was built as a
767 * module, we shall manually request the layout driver loading otherwise
768 * we'll never have any match.
769 */
> 770 of_device_node_request_module(layout_np);
771
772 spin_lock(&nvmem_layout_lock);
773
774 list_for_each_entry(l, &nvmem_layouts, node) {
775 if (of_match_node(l->of_match_table, layout_np)) {
776 if (try_module_get(l->owner))
777 layout = l;
778
779 break;
780 }
781 }
782
783 spin_unlock(&nvmem_layout_lock);
784 of_node_put(layout_np);
785
786 return layout;
787 }
788
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-07 23:27 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=202303080730.Qtk3lUUd-lkp@intel.com \
--to=lkp@intel.com \
--cc=miquel.raynal@bootlin.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.