From: kernel test robot <lkp@intel.com>
To: Heiko Stuebner <heiko@sntech.de>, lee@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, jdelvare@suse.com,
linux@roeck-us.net, heiko@sntech.de, dmitry.torokhov@gmail.com,
pavel@ucw.cz, ukleinek@debian.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-input@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v5 2/7] mfd: add base driver for qnap-mcu devices
Date: Thu, 22 Aug 2024 12:06:05 +0800 [thread overview]
Message-ID: <202408221141.ZK7cre1s-lkp@intel.com> (raw)
In-Reply-To: <20240819144000.411846-3-heiko@sntech.de>
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@intel.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
next prev parent reply other threads:[~2024-08-22 4:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 14:39 [PATCH v5 0/7] Drivers to support the MCU on QNAP NAS devices Heiko Stuebner
2024-08-19 14:39 ` [PATCH v5 1/7] dt-bindings: mfd: add binding for qnap,ts433-mcu devices Heiko Stuebner
2024-08-19 14:39 ` [PATCH v5 2/7] mfd: add base driver for qnap-mcu devices Heiko Stuebner
2024-08-22 4:06 ` kernel test robot [this message]
2024-08-19 14:39 ` [PATCH v5 3/7] leds: add driver for LEDs from " Heiko Stuebner
2024-08-19 14:39 ` [PATCH v5 4/7] Input: add driver for the input part of " Heiko Stuebner
2024-08-19 14:39 ` [PATCH v5 5/7] hwmon: add driver for the hwmon parts " Heiko Stuebner
2024-08-19 14:39 ` [PATCH v5 6/7] arm64: dts: rockchip: hook up the MCU on the QNAP TS433 Heiko Stuebner
2024-08-19 14:40 ` [PATCH v5 7/7] arm64: dts: rockchip: set hdd led labels on qnap-ts433 Heiko Stuebner
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=202408221141.ZK7cre1s-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=heiko@sntech.de \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=ukleinek@debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).