From: kernel test robot <lkp@intel.com>
To: Romain Gantois <romain.gantois@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Romain Gantois <romain.gantois@bootlin.com>
Subject: Re: [PATCH 2/2] misc: ti_fpc202: Support special-purpose GPIO lines with LED features
Date: Tue, 27 Jan 2026 23:42:36 +0100 [thread overview]
Message-ID: <202601272312.EmjoBjHO-lkp@intel.com> (raw)
In-Reply-To: <20260127-fpc202-leds-v1-2-ebd0cfb9f9a1@bootlin.com>
Hi Romain,
kernel test robot noticed the following build warnings:
[auto build test WARNING on a8a6d9b4da001a84dd715d92f034d2bf777199c8]
url: https://github.com/intel-lab-lkp/linux/commits/Romain-Gantois/dt-bindings-misc-Describe-FPC202-LED-features/20260127-215935
base: a8a6d9b4da001a84dd715d92f034d2bf777199c8
patch link: https://lore.kernel.org/r/20260127-fpc202-leds-v1-2-ebd0cfb9f9a1%40bootlin.com
patch subject: [PATCH 2/2] misc: ti_fpc202: Support special-purpose GPIO lines with LED features
config: parisc-kismet-CONFIG_LEDS_TRIGGERS-CONFIG_CHASSIS_LCD_LED-0-0 (https://download.01.org/0day-ci/archive/20260127/202601272312.EmjoBjHO-lkp@intel.com/config)
reproduce: (https://download.01.org/0day-ci/archive/20260127/202601272312.EmjoBjHO-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/202601272312.EmjoBjHO-lkp@intel.com/
kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for LEDS_TRIGGERS when selected by CHASSIS_LCD_LED
WARNING: unmet direct dependencies detected for LEDS_CLASS
Depends on [n]: NEW_LEDS [=n]
Selected by [y]:
- TI_FPC202 [=y] && I2C [=y]
WARNING: unmet direct dependencies detected for LEDS_TRIGGERS
Depends on [n]: NEW_LEDS [=n] && LEDS_CLASS [=y]
Selected by [y]:
- CHASSIS_LCD_LED [=y] && LEDS_CLASS [=y]=y [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-27 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 13:51 [PATCH 0/2] misc: ti_fpc202: Add LED support Romain Gantois
2026-01-27 13:51 ` [PATCH 1/2] dt-bindings: misc: Describe FPC202 LED features Romain Gantois
2026-01-27 19:45 ` Conor Dooley
2026-01-27 13:51 ` [PATCH 2/2] misc: ti_fpc202: Support special-purpose GPIO lines with " Romain Gantois
2026-01-27 14:03 ` Arnd Bergmann
2026-01-27 22:40 ` kernel test robot
2026-01-27 22:42 ` kernel test robot [this message]
2026-01-27 22:43 ` kernel test robot
2026-01-28 0:30 ` kernel test robot
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=202601272312.EmjoBjHO-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fazilyildiran@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.com \
--cc=robh@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=thomas.petazzoni@bootlin.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