From: kernel test robot <lkp@intel.com>
To: Kartik <kkartik@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-tegra@vger.kernel.org,
Thierry Reding <treding@nvidia.com>
Subject: [arm-tegra:for-6.8/soc 9/10] drivers/soc/tegra/fuse/fuse-tegra30.c:684:17: error: 'tegra30_fuse_read' undeclared here (not in a function); did you mean 'tegra_fuse_readl'?
Date: Sun, 31 Mar 2024 14:54:57 +0800 [thread overview]
Message-ID: <202403311414.xn2GkelU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git for-6.8/soc
head: f655182f9e9edda559b41a1f8b3b9c944443694a
commit: dee509eb9cd593b7bcb1c1f1f5f2d7e75e389290 [9/10] soc/tegra: fuse: Add support for Tegra241
config: arm64-randconfig-002-20240331 (https://download.01.org/0day-ci/archive/20240331/202403311414.xn2GkelU-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240331/202403311414.xn2GkelU-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/202403311414.xn2GkelU-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/soc/tegra/fuse/fuse-tegra30.c:684:17: error: 'tegra30_fuse_read' undeclared here (not in a function); did you mean 'tegra_fuse_readl'?
684 | .read = tegra30_fuse_read,
| ^~~~~~~~~~~~~~~~~
| tegra_fuse_readl
>> drivers/soc/tegra/fuse/fuse-tegra30.c:694:17: error: 'tegra30_fuse_init' undeclared here (not in a function); did you mean 'tegra_fuse_info'?
694 | .init = tegra30_fuse_init,
| ^~~~~~~~~~~~~~~~~
| tegra_fuse_info
drivers/soc/tegra/fuse/fuse-tegra30.c:698:28: error: 'tegra194_soc_attr_group' undeclared here (not in a function); did you mean 'tegra_soc_attr_group'?
698 | .soc_attr_group = &tegra194_soc_attr_group,
| ^~~~~~~~~~~~~~~~~~~~~~~
| tegra_soc_attr_group
vim +684 drivers/soc/tegra/fuse/fuse-tegra30.c
681
682 #if defined(CONFIG_ARCH_TEGRA_241_SOC)
683 static const struct tegra_fuse_info tegra241_fuse_info = {
> 684 .read = tegra30_fuse_read,
685 .size = 0x16008,
686 .spare = 0xcf0,
687 };
688
689 static const struct nvmem_keepout tegra241_fuse_keepouts[] = {
690 { .start = 0xc, .end = 0x1600c }
691 };
692
693 const struct tegra_fuse_soc tegra241_fuse_soc = {
> 694 .init = tegra30_fuse_init,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-31 6:55 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=202403311414.xn2GkelU-lkp@intel.com \
--to=lkp@intel.com \
--cc=kkartik@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).