From: kernel test robot <lkp@intel.com>
To: Niranjan H Y <niranjan.hy@ti.com>, broonie@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, andriy.shevchenko@linux.intel.com,
tiwai@suse.de, alsa-devel@alsa-project.org, baojun.xu@ti.com,
shenghao-ding@ti.com, liam.r.girdwood@intel.com, navada@ti.com,
v-hampiholi@ti.com, niranjan.hy@ti.com
Subject: Re: [PATCH v2 1/4] ASoc: tac5x1x: add codec driver tac5x1x family
Date: Sun, 29 Jun 2025 04:42:03 +0800 [thread overview]
Message-ID: <202506290455.cgLfcmh1-lkp@intel.com> (raw)
In-Reply-To: <20250624153742.1507-2-niranjan.hy@ti.com>
Hi Niranjan,
kernel test robot noticed the following build errors:
[auto build test ERROR on broonie-sound/for-next]
[also build test ERROR on linus/master v6.16-rc3 next-20250627]
[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/Niranjan-H-Y/ASoc-tac5x1x-add-codec-driver-tac5x1x-family/20250628-012714
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
patch link: https://lore.kernel.org/r/20250624153742.1507-2-niranjan.hy%40ti.com
patch subject: [PATCH v2 1/4] ASoc: tac5x1x: add codec driver tac5x1x family
config: x86_64-rhel-9.4 (attached as .config)
compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250629/202506290455.cgLfcmh1-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/202506290455.cgLfcmh1-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: recursive dependency detected!
symbol REGMAP_I2C is selected by SND_SOC_TAC5X1X_I2C
symbol SND_SOC_TAC5X1X_I2C depends on REGMAP_I2C
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:[~2025-06-28 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 15:37 [PATCH v2 0/4] ASoc: tac5x1x: mixer-test report Niranjan H Y
2025-06-24 15:37 ` [PATCH v2 1/4] ASoc: tac5x1x: add codec driver tac5x1x family Niranjan H Y
2025-06-25 12:03 ` Mark Brown
2025-06-28 20:42 ` kernel test robot [this message]
2025-06-24 15:37 ` [PATCH v2 2/4] Asoc: tac5x1x: document tac5x1x codec Niranjan H Y
2025-06-25 14:30 ` Andy Shevchenko
2025-06-24 15:37 ` [PATCH v2 3/4] Asoc: pcm6240: remove support for taac5x1x family Niranjan H Y
2025-06-24 15:37 ` [PATCH v2 4/4] ASoc: pcm6240: dt-bindings device support list update Niranjan H Y
2025-06-25 14:32 ` 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=202506290455.cgLfcmh1-lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=navada@ti.com \
--cc=niranjan.hy@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
--cc=v-hampiholi@ti.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.