On Tue, Nov 15, 2022 at 11:13 AM Sudeep Holla <sudeep.holla@xxxxxxx> wrote: > > Hi Rafael, > > On Tue, Nov 15, 2022 at 09:44:13AM +0800, kernel test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge > > head: 8992b8d17e6c314a528a5bce386de28701f2a2ef > > commit: 1d280ce099db396e092cac1aa9bf2ea8beee6d76 [67/68] arm64: Add architecture specific ACPI FFH Opregion callbacks > > config: arm64-allyesconfig > > compiler: aarch64-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://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?id=1d280ce099db396e092cac1aa9bf2ea8beee6d76 > > git remote add rafael-pm https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git > > git fetch --no-tags rafael-pm bleeding-edge > > git checkout 1d280ce099db396e092cac1aa9bf2ea8beee6d76 > > # 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=arm64 SHELL=/bin/bash arch/arm64/kernel/ > > > > If you fix the issue, kindly add following tag where applicable > > | Reported-by: kernel test robot <lkp@xxxxxxxxx> > > > > All warnings (new ones prefixed by >>): > > > > arch/arm64/kernel/acpi.c:422:30: error: field 'info' has incomplete type > > 422 | struct acpi_ffh_info info; > > | ^~~~ > > >> arch/arm64/kernel/acpi.c:433:5: warning: no previous prototype for 'acpi_ffh_address_space_arch_setup' [-Wmissing-prototypes] > > 433 | int acpi_ffh_address_space_arch_setup(void *handler_ctxt, void **region_ctxt) > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > >> arch/arm64/kernel/acpi.c:476:5: warning: no previous prototype for 'acpi_ffh_address_space_arch_handler' [-Wmissing-prototypes] > > 476 | int acpi_ffh_address_space_arch_handler(acpi_integer *value, void *region_context) > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > I am aware of these warnings and left it unaddressed for consistency. There > are few(6-8) such instance with similar warnings upstream as well. Let me know > if you prefer to get them fixed, I can fix them all in one go if you are fine > with that. Well, it would be good to fix those, at least for the sake of reducing noise if nothing else.
