From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, Arnd Bergmann <arnd@kernel.org>, vkoul@kernel.org
Subject: Re: [PATCH 0/2] ASoC: SOF: partial fix to Kconfig issues
Date: Mon, 25 Jan 2021 14:17:22 +0000 [thread overview]
Message-ID: <161158424213.32959.2931023496403408589.b4-ty@kernel.org> (raw)
In-Reply-To: <20210122005725.94163-1-pierre-louis.bossart@linux.intel.com>
On Thu, 21 Jan 2021 18:57:23 -0600, Pierre-Louis Bossart wrote:
> We've had several reports of broken dependencies. The 'right' fix is
> to revisit the module dependencies as suggested by Arnd Bergmann. This
> is WIP at https://github.com/thesofproject/linux/pull/2683. Since this
> is taking longer than expected, I am only sharing quick fixes for now.
>
> Pierre-Louis Bossart (2):
> ASoC: SOF: Intel: soundwire: fix select/depend unmet dependencies
> ASoC: SOF: SND_INTEL_DSP_CONFIG dependency
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: SOF: Intel: soundwire: fix select/depend unmet dependencies
commit: bd9038faa9d7f162b47e1577e35ec5eac39f9d90
[2/2] ASoC: SOF: SND_INTEL_DSP_CONFIG dependency
commit: 8a3fea95fab14dd19487d1e499eee3b3d1050d70
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
prev parent reply other threads:[~2021-01-25 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 0:57 [PATCH 0/2] ASoC: SOF: partial fix to Kconfig issues Pierre-Louis Bossart
2021-01-22 0:57 ` [PATCH 1/2] ASoC: SOF: Intel: soundwire: fix select/depend unmet dependencies Pierre-Louis Bossart
2021-01-22 0:57 ` [PATCH 2/2] ASoC: SOF: SND_INTEL_DSP_CONFIG dependency Pierre-Louis Bossart
2021-01-22 5:26 ` Vinod Koul
2021-01-22 8:58 ` Takashi Iwai
2021-01-22 15:38 ` Pierre-Louis Bossart
2021-01-22 18:33 ` Arnd Bergmann
2021-01-23 8:08 ` Takashi Iwai
2021-01-25 14:17 ` 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=161158424213.32959.2931023496403408589.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
--cc=vkoul@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 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.