From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: kernel test robot <lkp@intel.com>
Cc: <broonie@kernel.org>, Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
<oe-kbuild-all@lists.linux.dev>, <lgirdwood@gmail.com>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH] ASoC: wm8994: Add depends on MFD core
Date: Tue, 7 Jan 2025 10:27:50 +0000 [thread overview]
Message-ID: <Z30BpixgkmEG5iTY@opensource.cirrus.com> (raw)
In-Reply-To: <202501071530.UwIXs7OL-lkp@intel.com>
On Tue, Jan 07, 2025 at 03:39:31PM +0800, kernel test robot wrote:
> Hi Charles,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on broonie-sound/for-next]
> [also build test WARNING on linus/master v6.13-rc6 next-20250106]
> [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/Charles-Keepax/ASoC-wm8994-Add-depends-on-MFD-core/20250106-235153
> base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
> patch link: https://lore.kernel.org/r/20250106154639.3999553-1-ckeepax%40opensource.cirrus.com
> patch subject: [PATCH] ASoC: wm8994: Add depends on MFD core
> config: alpha-kismet-CONFIG_SND_SOC_WM8994-CONFIG_SND_SOC_SAMSUNG_MIDAS_WM1811-0-0 (https://download.01.org/0day-ci/archive/20250107/202501071530.UwIXs7OL-lkp@intel.com/config)
> reproduce: (https://download.01.org/0day-ci/archive/20250107/202501071530.UwIXs7OL-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/202501071530.UwIXs7OL-lkp@intel.com/
>
> kismet warnings: (new ones prefixed by >>)
> >> kismet: WARNING: unmet direct dependencies detected for SND_SOC_WM8994 when selected by SND_SOC_SAMSUNG_MIDAS_WM1811
> WARNING: unmet direct dependencies detected for SND_SOC_WM8994
> Depends on [n]: SOUND [=y] && SND [=y] && SND_SOC [=y] && MFD_WM8994 [=n]
> Selected by [y]:
> - SND_SOC_SAMSUNG_MIDAS_WM1811 [=y] && SOUND [=y] && SND [=y] && SND_SOC [=y] && SND_SOC_SAMSUNG [=y] && IIO [=y]
>
Well I guess this is maybe an argument in favour of adding the
depends since unlike that issue these are actual things one
might hit in practice. Both Aries and Midas appear to be missing
selects for the MFD part of 8994, fine as long as it gets manually
selected but will blow up if it doesn't. Will send a patch for this,
but it needed not block this patch, its a separate issue.
Thanks,
Charles
next prev parent reply other threads:[~2025-01-07 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 15:46 [PATCH] ASoC: wm8994: Add depends on MFD core Charles Keepax
2025-01-07 7:39 ` kernel test robot
2025-01-07 10:27 ` Charles Keepax [this message]
2025-01-07 15:32 ` Mark Brown
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=Z30BpixgkmEG5iTY@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=fazilyildiran@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=patches@opensource.cirrus.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox