From: kernel test robot <lkp@intel.com>
To: Siratul Islam <email@sirat.me>,
andy@kernel.org, geert@linux-m68k.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, Siratul Islam <email@sirat.me>
Subject: Re: [PATCH 3/4] auxdisplay: tm1637: Add driver for TM1637
Date: Tue, 13 Jan 2026 22:57:52 +0800 [thread overview]
Message-ID: <202601132253.Up9189vT-lkp@intel.com> (raw)
In-Reply-To: <20260113040242.19156-4-email@sirat.me>
Hi Siratul,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on linus/master v6.19-rc5 next-20260113]
[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/Siratul-Islam/dt-bindings-vendor-prefixes-Add-titanmec/20260113-161216
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20260113040242.19156-4-email%40sirat.me
patch subject: [PATCH 3/4] auxdisplay: tm1637: Add driver for TM1637
config: riscv-randconfig-002-20260113 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260113/202601132253.Up9189vT-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/202601132253.Up9189vT-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: recursive dependency detected!
symbol AUXDISPLAY is selected by TM1637
symbol TM1637 depends on AUXDISPLAY
For a resolution refer to Documentation/kbuild/kconfig-language.rst
subsection "Kconfig recursive dependency limitations"
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-13 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 4:02 [PATCH 0/4] auxdisplay: Add support for TM1637 7-segment display driver Siratul Islam
2026-01-13 4:02 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Add titanmec Siratul Islam
2026-01-13 16:22 ` Krzysztof Kozlowski
2026-01-13 4:02 ` [PATCH 2/4] dt-bindings: auxdisplay: Add titanmec,tm1637 Siratul Islam
2026-01-13 16:24 ` Krzysztof Kozlowski
2026-01-13 4:02 ` [PATCH 3/4] auxdisplay: tm1637: Add driver for TM1637 Siratul Islam
2026-01-13 7:52 ` Andy Shevchenko
2026-01-13 9:42 ` Sirat
2026-01-13 9:47 ` Andy Shevchenko
2026-01-13 14:57 ` kernel test robot [this message]
2026-01-13 4:02 ` [PATCH 4/4] MAINTAINERS: Add entry " Siratul Islam
2026-01-13 6:54 ` [PATCH 0/4] auxdisplay: Add support for TM1637 7-segment display driver Andy Shevchenko
2026-01-13 6:56 ` Andy Shevchenko
[not found] ` <CANn+LWLECPY-F_fsDg1VxbjJdN-pLnkRpQn4OEFSa6yiARoU9A@mail.gmail.com>
2026-01-13 9:41 ` Andy Shevchenko
2026-01-13 9:46 ` Andy Shevchenko
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=202601132253.Up9189vT-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=email@sirat.me \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.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