From: kernel test robot <lkp@intel.com>
To: Alim Akhtar <alim.akhtar@samsung.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Chanho Park <chanho61.park@samsung.com>,
Bharat Uppal <bharat.uppal@samsung.com>
Subject: [mkp-scsi:for-next 31/41] drivers/phy/samsung/phy-fsd-ufs.c:50:3: error: field designator 'cfgs' does not refer to any field in type 'const struct samsung_ufs_phy_drvdata'; did you mean 'cfg'?
Date: Sun, 12 Jun 2022 07:33:03 +0800 [thread overview]
Message-ID: <202206120755.03gKC0ne-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
head: b9f50e3cfd13687279f2170ff6ef5d71f6c7db11
commit: f678ce49991950e4964cd82d3f3a8adfb63a9a70 [31/41] scsi: phy: samsung-ufs: Add support for FSD UFS PHY driver
config: hexagon-randconfig-r045-20220612 (https://download.01.org/0day-ci/archive/20220612/202206120755.03gKC0ne-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project ff4abe755279a3a47cc416ef80dbc900d9a98a19)
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://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=f678ce49991950e4964cd82d3f3a8adfb63a9a70
git remote add mkp-scsi https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git
git fetch --no-tags mkp-scsi for-next
git checkout f678ce49991950e4964cd82d3f3a8adfb63a9a70
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/phy/samsung/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/phy/samsung/phy-fsd-ufs.c:50:3: error: field designator 'cfgs' does not refer to any field in type 'const struct samsung_ufs_phy_drvdata'; did you mean 'cfg'?
.cfgs = fsd_ufs_phy_cfgs,
^~~~
cfg
drivers/phy/samsung/phy-samsung-ufs.h:104:37: note: 'cfg' declared here
const struct samsung_ufs_phy_cfg **cfg;
^
1 error generated.
vim +50 drivers/phy/samsung/phy-fsd-ufs.c
48
49 const struct samsung_ufs_phy_drvdata fsd_ufs_phy = {
> 50 .cfgs = fsd_ufs_phy_cfgs,
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-06-11 23:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220611233355epcas5p1970bae9647eae17e20d330775b584695@epcas5p1.samsung.com>
2022-06-11 23:33 ` kernel test robot [this message]
2022-06-12 4:13 ` [mkp-scsi:for-next 31/41] drivers/phy/samsung/phy-fsd-ufs.c:50:3: error: field designator 'cfgs' does not refer to any field in type 'const struct samsung_ufs_phy_drvdata'; did you mean 'cfg'? Alim Akhtar
2022-06-12 4:13 ` Alim Akhtar
2022-06-14 1:45 ` Martin K. Petersen
2022-06-14 1:45 ` Martin K. Petersen
2022-06-14 1:49 ` Martin K. Petersen
2022-06-14 1:49 ` Martin K. Petersen
2022-06-14 1:53 ` Alim Akhtar
2022-06-14 1:53 ` Alim Akhtar
2022-06-14 1:56 ` Martin K. Petersen
2022-06-14 1:56 ` Martin K. Petersen
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=202206120755.03gKC0ne-lkp@intel.com \
--to=lkp@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=bharat.uppal@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.petersen@oracle.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.