linux-kernel - Re: [PATCH v5 2/7] mfd: add base driver for qnap-mcu devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <202408221141.ZK7cre1s-lkp@intel.com>
Date: Thu, 22 Aug 2024 12:06:05 +0800
From: kernel test robot <lkp@...el.com>
To: Heiko Stuebner <heiko@...ech.de>, lee@...nel.org
Cc: oe-kbuild-all@...ts.linux.dev, robh@...nel.org, krzk+dt@...nel.org,
	conor+dt@...nel.org, jdelvare@...e.com, linux@...ck-us.net,
	heiko@...ech.de, dmitry.torokhov@...il.com, pavel@....cz,
	ukleinek@...ian.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-hwmon@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	linux-rockchip@...ts.infradead.org, linux-input@...r.kernel.org,
	linux-leds@...r.kernel.org
Subject: Re: [PATCH v5 2/7] mfd: add base driver for qnap-mcu devices

Hi Heiko,

kernel test robot noticed the following build warnings:

[auto build test WARNING on next-20240819]
[also build test WARNING on v6.11-rc4]
[cannot apply to groeck-staging/hwmon-next lee-leds/for-leds-next lee-mfd/for-mfd-next lee-mfd/for-mfd-fixes linus/master v6.11-rc4 v6.11-rc3 v6.11-rc2]
[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/Heiko-Stuebner/dt-bindings-mfd-add-binding-for-qnap-ts433-mcu-devices/20240819-224312
base:   next-20240819
patch link:    https://lore.kernel.org/r/20240819144000.411846-3-heiko%40sntech.de
patch subject: [PATCH v5 2/7] mfd: add base driver for qnap-mcu devices
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20240822/202408221141.ZK7cre1s-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240822/202408221141.ZK7cre1s-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202408221141.ZK7cre1s-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/mfd/qnap-mcu.c:64: warning: Excess struct member 'reply_lock' description in 'qnap_mcu'


vim +64 drivers/mfd/qnap-mcu.c

    47	
    48	/**
    49	 * struct qnap_mcu - QNAP NAS embedded controller
    50	 *
    51	 * @serdev:	Pointer to underlying serdev
    52	 * @bus_lock:	Lock to serialize access to the device
    53	 * @reply_lock:	Lock protecting @reply
    54	 * @reply:	Pointer to memory to store reply payload
    55	 * @variant:	Device variant specific information
    56	 * @version:	MCU firmware version
    57	 */
    58	struct qnap_mcu {
    59		struct serdev_device *serdev;
    60		struct mutex bus_lock;
    61		struct qnap_mcu_reply reply;
    62		const struct qnap_mcu_variant *variant;
    63		u8 version[QNAP_MCU_VERSION_LEN];
  > 64	};
    65	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki