From: kernel test robot <lkp@intel.com>
To: a0282524688@gmail.com, tmyu0@nuvoton.com, lee@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Ming Yu <a0282524688@gmail.com>
Subject: Re: [PATCH v3 1/1] mfd: Add Host Interface (HIF) support for Nuvoton NCT6694
Date: Mon, 27 Apr 2026 00:42:25 +0800 [thread overview]
Message-ID: <202604270032.OVoX7km0-lkp@intel.com> (raw)
In-Reply-To: <20260422035307.2065172-2-a0282524688@gmail.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on lee-mfd/for-mfd-next]
[also build test WARNING on lee-leds/for-leds-next linus/master lee-mfd/for-mfd-fixes v7.0 next-20260424]
[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/a0282524688-gmail-com/mfd-Add-Host-Interface-HIF-support-for-Nuvoton-NCT6694/20260424-201531
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
patch link: https://lore.kernel.org/r/20260422035307.2065172-2-a0282524688%40gmail.com
patch subject: [PATCH v3 1/1] mfd: Add Host Interface (HIF) support for Nuvoton NCT6694
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20260427/202604270032.OVoX7km0-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260427/202604270032.OVoX7km0-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/202604270032.OVoX7km0-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpio/gpio-nct6694.c:21:9: warning: 'NCT6694_GPIO_MOD' macro redefined [-Wmacro-redefined]
21 | #define NCT6694_GPIO_MOD 0xFF
| ^
include/linux/mfd/nct6694.h:27:9: note: previous definition is here
27 | #define NCT6694_GPIO_MOD NCT6694_RPT_MOD
| ^
1 warning generated.
vim +/NCT6694_GPIO_MOD +21 drivers/gpio/gpio-nct6694.c
611a995e8ae1a5 Ming Yu 2025-09-12 15
611a995e8ae1a5 Ming Yu 2025-09-12 16 /*
611a995e8ae1a5 Ming Yu 2025-09-12 17 * USB command module type for NCT6694 GPIO controller.
611a995e8ae1a5 Ming Yu 2025-09-12 18 * This defines the module type used for communication with the NCT6694
611a995e8ae1a5 Ming Yu 2025-09-12 19 * GPIO controller over the USB interface.
611a995e8ae1a5 Ming Yu 2025-09-12 20 */
611a995e8ae1a5 Ming Yu 2025-09-12 @21 #define NCT6694_GPIO_MOD 0xFF
611a995e8ae1a5 Ming Yu 2025-09-12 22
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-26 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 3:53 [PATCH v3 0/1] mfd: nct6694: Refactor transport layer and add HIF (eSPI) support a0282524688
2026-04-22 3:53 ` [PATCH v3 1/1] mfd: Add Host Interface (HIF) support for Nuvoton NCT6694 a0282524688
2026-04-26 4:38 ` kernel test robot
2026-04-26 16:42 ` kernel test robot [this message]
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=202604270032.OVoX7km0-lkp@intel.com \
--to=lkp@intel.com \
--cc=a0282524688@gmail.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tmyu0@nuvoton.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox