From: kernel test robot <lkp@intel.com>
To: Syed Saba Kareem <Syed.SabaKareem@amd.com>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev, Mark Brown <broonie@kernel.org>
Subject: [broonie-ci:asoc-7.3 14/16] kismet: WARNING: unmet direct dependencies detected for SND_SOC_TAS2783_SDW when selected by SND_SOC_AMD_LEGACY_SDW_MACH
Date: Fri, 18 Sep 2026 21:51:28 +0200 [thread overview]
Message-ID: <202609182147.gfofWIXW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git asoc-7.3
head: 174d160884199cad97413f33fe1b56027dc0d3e1
commit: 28114992dd2f03724eb3d024839b3f9f299656d3 [14/16] ASoC: amd: acp: enable TAS2783 and add RT712-VB SoundWire machine
config: x86_64-kismet-CONFIG_SND_SOC_TAS2783_SDW-CONFIG_SND_SOC_AMD_LEGACY_SDW_MACH-0-0 (https://download.01.org/0day-ci/archive/20260918/202609182147.gfofWIXW-lkp@intel.com/config)
reproduce: (https://download.01.org/0day-ci/archive/20260918/202609182147.gfofWIXW-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/202609182147.gfofWIXW-lkp@intel.com/
kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for SND_SOC_TAS2783_SDW when selected by SND_SOC_AMD_LEGACY_SDW_MACH
WARNING: unmet direct dependencies detected for SND_SOC_TAS2783_SDW
Depends on [n]: SOUND [=y] && SND [=y] && SND_SOC [=y] && SOUNDWIRE [=y] && SND_SOC_SDCA [=y] && EFI [=n]
Selected by [y]:
- SND_SOC_AMD_LEGACY_SDW_MACH [=y] && SOUND [=y] && SND [=y] && SND_SOC [=y] && SND_SOC_AMD_ACP_COMMON [=y] && X86 [=y] && PCI [=y] && ACPI [=y] && SOUNDWIRE [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-18 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202609182147.gfofWIXW-lkp@intel.com \
--to=lkp@intel.com \
--cc=Syed.SabaKareem@amd.com \
--cc=broonie@kernel.org \
--cc=fazilyildiran@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.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.