Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: mario.limonciello@amd.com, lgirdwood@gmail.com,
	 peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
	 ranjani.sridharan@linux.intel.com, daniel.baluta@nxp.com,
	perex@perex.cz,  tiwai@suse.com,
	Mario Limonciello <superm1@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
	sound-open-firmware@alsa-project.org,
	 linux-sound@vger.kernel.org
Subject: Re: [PATCH] ASoC: SOF: amd: Move depends on AMD_NODE to consumers
Date: Tue, 25 Feb 2025 13:38:40 +0000	[thread overview]
Message-ID: <174049072070.42497.4513505959055428564.b4-ty@kernel.org> (raw)
In-Reply-To: <20250221181840.2639793-1-superm1@kernel.org>

On Fri, 21 Feb 2025 12:18:12 -0600, Mario Limonciello wrote:
> CONFIG_SND_SOC_SOF_AMD_COMMON is a hidden option that is only selected by
> other options.  It can't have a direct depends on AMD_NODE because select
> can't pick another option automatically.
> 
> This was attempted to be fixed in commit b47834ee4485b ("ASoC: SOF: amd:
> Add depends on CPU_SUP_AMD") but this just masked the issue as it was found
> in another config.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: SOF: amd: Move depends on AMD_NODE to consumers
      commit: 91b75129149429bb16927cda8b5642c04c59e6b0

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      reply	other threads:[~2025-02-25 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 18:18 [PATCH] ASoC: SOF: amd: Move depends on AMD_NODE to consumers Mario Limonciello
2025-02-25 13:38 ` Mark Brown [this message]

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=174049072070.42497.4513505959055428564.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mario.limonciello@amd.com \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=superm1@kernel.org \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@linux.intel.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