From: kernel test robot <lkp@intel.com>
To: Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, git@amd.com,
Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
Ajay Neeli <ajay.neeli@amd.com>
Subject: [xilinx-xlnx:lkp_test 3/4] drivers/ufs/host/ufs-amd-versal2.c:561:34: warning: 'ufs_versal2_pltfm_match' defined but not used
Date: Thu, 7 Aug 2025 18:36:19 +0800 [thread overview]
Message-ID: <202508071848.2WeD4IMd-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx lkp_test
head: bf02b5ab30f349d173dd098be46a5a01493670b3
commit: 2a574c8da24fba5d98b9b6c5adc266ef3e3f2c2e [3/4] ufs: amd-versal2: Add AMD Versal Gen 2 UFS support
config: sh-randconfig-002-20250807 (https://download.01.org/0day-ci/archive/20250807/202508071848.2WeD4IMd-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250807/202508071848.2WeD4IMd-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/202508071848.2WeD4IMd-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/ufs/host/ufs-amd-versal2.c: In function 'ufs_versal2_phy_init':
drivers/ufs/host/ufs-amd-versal2.c:251:9: error: implicit declaration of function 'zynqmp_pm_sec_read_reg'; did you mean 'zynqmp_pm_read_pggs'? [-Werror=implicit-function-declaration]
251 | ret = zynqmp_pm_sec_read_reg(PM_REGNODE_PMC_IOU_SLCR, TXRX_CFGRDY_OFFSET, ®);
| ^~~~~~~~~~~~~~~~~~~~~~
| zynqmp_pm_read_pggs
drivers/ufs/host/ufs-amd-versal2.c: In function 'ufs_versal2_hce_enable_notify':
drivers/ufs/host/ufs-amd-versal2.c:388:9: error: implicit declaration of function 'zynqmp_pm_sec_mask_write_reg' [-Werror=implicit-function-declaration]
388 | ret = zynqmp_pm_sec_mask_write_reg(PM_REGNODE_PMC_IOU_SLCR, SRAM_CSR_OFFSET,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/ufs/host/ufs-amd-versal2.c: At top level:
drivers/ufs/host/ufs-amd-versal2.c:558:23: error: initialization of 'int (*)(struct ufs_hba *, enum ufs_notify_change_status, const struct ufs_pa_layer_attr *, struct ufs_pa_layer_attr *)' from incompatible pointer type 'int (*)(struct ufs_hba *, enum ufs_notify_change_status, struct ufs_pa_layer_attr *, struct ufs_pa_layer_attr *)' [-Werror=incompatible-pointer-types]
558 | .pwr_change_notify = ufs_versal2_pwr_change_notify,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/ufs/host/ufs-amd-versal2.c:558:23: note: (near initialization for 'ufs_versal2_hba_vops.pwr_change_notify')
>> drivers/ufs/host/ufs-amd-versal2.c:561:34: warning: 'ufs_versal2_pltfm_match' defined but not used [-Wunused-const-variable=]
561 | static const struct of_device_id ufs_versal2_pltfm_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/ufs_versal2_pltfm_match +561 drivers/ufs/host/ufs-amd-versal2.c
560
> 561 static const struct of_device_id ufs_versal2_pltfm_match[] = {
562 {
563 .compatible = "amd,versal2-ufs",
564 .data = &ufs_versal2_hba_vops,
565 },
566 { },
567 };
568 MODULE_DEVICE_TABLE(of, ufs_versal2_pltfm_match);
569
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-07 10:36 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=202508071848.2WeD4IMd-lkp@intel.com \
--to=lkp@intel.com \
--cc=ajay.neeli@amd.com \
--cc=git@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=radhey.shyam.pandey@amd.com \
--cc=sai.krishna.potthuri@amd.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.