From: kernel test robot <lkp@intel.com>
To: Joy Zou <joy.zou@nxp.com>,
lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
frank.li@nxp.com, ye.li@nxp.com, ping.bai@nxp.com,
aisheng.dong@nxp.com
Subject: Re: [PATCH v1 2/2] regulator: pf0900: Add PMIC PF0900 support
Date: Wed, 18 Jun 2025 12:21:20 +0800 [thread overview]
Message-ID: <202506181134.0Hkvy7CK-lkp@intel.com> (raw)
In-Reply-To: <20250617102025.3455544-3-joy.zou@nxp.com>
Hi Joy,
kernel test robot noticed the following build warnings:
[auto build test WARNING on broonie-regulator/for-next]
[also build test WARNING on linus/master v6.16-rc2 next-20250617]
[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/Joy-Zou/dt-bindings-regulator-add-PF0900-regulator-yaml/20250617-182500
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
patch link: https://lore.kernel.org/r/20250617102025.3455544-3-joy.zou%40nxp.com
patch subject: [PATCH v1 2/2] regulator: pf0900: Add PMIC PF0900 support
config: arm-allmodconfig (https://download.01.org/0day-ci/archive/20250618/202506181134.0Hkvy7CK-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250618/202506181134.0Hkvy7CK-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/202506181134.0Hkvy7CK-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/regulator/pf0900-regulator.c:20:
>> include/linux/regulator/pf0900.h:235:9: warning: 'IRQ_MODE' redefined
235 | #define IRQ_MODE 0x04
| ^~~~~~~~
In file included from arch/arm/include/asm/ptrace.h:10,
from arch/arm/include/asm/irqflags.h:7,
from include/linux/irqflags.h:18,
from arch/arm/include/asm/bitops.h:28,
from include/linux/bitops.h:67,
from include/linux/thread_info.h:27,
from include/asm-generic/preempt.h:5,
from ./arch/arm/include/generated/asm/preempt.h:1,
from include/linux/preempt.h:79,
from include/linux/spinlock.h:56,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:7,
from include/linux/slab.h:16,
from include/linux/resource_ext.h:11,
from include/linux/acpi.h:13,
from include/linux/i2c.h:13,
from drivers/regulator/pf0900-regulator.c:10:
arch/arm/include/uapi/asm/ptrace.h:60:9: note: this is the location of the previous definition
60 | #define IRQ_MODE 0x00000012
| ^~~~~~~~
vim +/IRQ_MODE +235 include/linux/regulator/pf0900.h
227
228
229 /* PF0900_REG_STSTEM_INT bits */
230 #define IRQ_EWARN 0x80
231 #define IRQ_GPIO 0x40
232 #define IRQ_OV 0x20
233 #define IRQ_UV 0x10
234 #define IRQ_ILIM 0x08
> 235 #define IRQ_MODE 0x04
236 #define IRQ_STATUS2 0x02
237 #define IRQ_STATUS1 0x01
238
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-06-18 4:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 10:20 [PATCH v1 0/2] regulator: add new PMIC PF0900 support Joy Zou
2025-06-17 10:20 ` [PATCH v1 1/2] dt-bindings: regulator: add PF0900 regulator yaml Joy Zou
2025-06-17 11:49 ` Mark Brown
2025-06-19 9:43 ` Joy Zou
2025-06-17 13:12 ` Rob Herring (Arm)
2025-06-19 9:43 ` Joy Zou
2025-06-17 13:43 ` Rob Herring
2025-06-17 10:20 ` [PATCH v1 2/2] regulator: pf0900: Add PMIC PF0900 support Joy Zou
2025-06-17 11:44 ` Mark Brown
2025-06-18 4:21 ` 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=202506181134.0Hkvy7CK-lkp@intel.com \
--to=lkp@intel.com \
--cc=aisheng.dong@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=joy.zou@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ping.bai@nxp.com \
--cc=robh@kernel.org \
--cc=ye.li@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.