From: kernel test robot <lkp@intel.com>
To: Dzmitry Sankouski <dsankouski@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>, Lee Jones <lee@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Dzmitry Sankouski <dsankouski@gmail.com>
Subject: Re: [PATCH] mfd: max77705: rework interrupts
Date: Sun, 31 Aug 2025 08:02:34 +0800 [thread overview]
Message-ID: <202508310735.f7Evkqz7-lkp@intel.com> (raw)
In-Reply-To: <20250831-max77705-fix_interrupt_handling-v1-1-73e078012e51@gmail.com>
Hi Dzmitry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3cace99d63192a7250461b058279a42d91075d0c]
url: https://github.com/intel-lab-lkp/linux/commits/Dzmitry-Sankouski/mfd-max77705-rework-interrupts/20250831-061657
base: 3cace99d63192a7250461b058279a42d91075d0c
patch link: https://lore.kernel.org/r/20250831-max77705-fix_interrupt_handling-v1-1-73e078012e51%40gmail.com
patch subject: [PATCH] mfd: max77705: rework interrupts
config: hexagon-randconfig-002-20250831 (https://download.01.org/0day-ci/archive/20250831/202508310735.f7Evkqz7-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250831/202508310735.f7Evkqz7-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/202508310735.f7Evkqz7-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/mfd/max77705.c:89:37: warning: unused variable 'max77705_topsys_irq_chip' [-Wunused-const-variable]
89 | static const struct regmap_irq_chip max77705_topsys_irq_chip = {
| ^~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
vim +/max77705_topsys_irq_chip +89 drivers/mfd/max77705.c
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 88
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 @89 static const struct regmap_irq_chip max77705_topsys_irq_chip = {
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 90 .name = "max77705-topsys",
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 91 .status_base = MAX77705_PMIC_REG_SYSTEM_INT,
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 92 .mask_base = MAX77705_PMIC_REG_SYSTEM_INT_MASK,
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 93 .num_regs = 1,
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 94 .irqs = max77705_topsys_irqs,
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 95 .num_irqs = ARRAY_SIZE(max77705_topsys_irqs),
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 96 };
c8d50f029748b7 Dzmitry Sankouski 2025-01-23 97
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-31 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 22:13 Dzmitry Sankouski
2025-08-31 0:02 ` kernel test robot [this message]
2025-08-31 8:29 ` Krzysztof Kozlowski
2025-09-03 12:38 ` Lee Jones
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=202508310735.f7Evkqz7-lkp@intel.com \
--to=lkp@intel.com \
--cc=cw00.choi@samsung.com \
--cc=dsankouski@gmail.com \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®