Hi Komal, kernel test robot noticed the following build warnings: [auto build test WARNING on robh/for-next] [also build test WARNING on linus/master v6.4-rc7 next-20230623] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Komal-Bajaj/dt-bindings-nvmem-sec-qfprom-Add-bindings-for-secure-qfprom/20230623-222054 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20230623141806.13388-4-quic_kbajaj%40quicinc.com patch subject: [PATCH v4 3/6] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support. config: arm-allmodconfig (https://download.01.org/0day-ci/archive/20230624/202306240837.Keyvmt2I-lkp@xxxxxxxxx/config) compiler: arm-linux-gnueabi-gcc (GCC) 12.3.0 reproduce: (https://download.01.org/0day-ci/archive/20230624/202306240837.Keyvmt2I-lkp@xxxxxxxxx/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@xxxxxxxxx> | Closes: https://lore.kernel.org/oe-kbuild-all/202306240837.Keyvmt2I-lkp@xxxxxxxxx/ All warnings (new ones prefixed by >>): >> drivers/nvmem/sec-qfprom.c:31: warning: expecting prototype for struct sec_sec_qfprom_priv. Prototype was for struct sec_qfprom_priv instead vim +31 drivers/nvmem/sec-qfprom.c 20 21 22 /** 23 * struct sec_sec_qfprom_priv - structure holding secure qfprom attributes 24 * 25 * @qfpseccorrected: iomapped memory space for secure qfprom corrected address space. 26 * @dev: qfprom device structure. 27 */ 28 struct sec_qfprom_priv { 29 phys_addr_t qfpseccorrected; 30 struct device *dev; > 31 }; 32 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
