Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     yung-chuan.liao@linux.intel.com, vkoul@kernel.org,
        alsa-devel@alsa-project.org
Cc:     srinivas.kandagatla@linaro.org, bard.liao@intel.com,
        sanyog.r.kale@intel.com, pierre-louis.bossart@linux.intel.com,
        tiwai@suse.de, linux-kernel@vger.kernel.org,
        gregkh@linuxfoundation.org, vinod.koul@linaro.org
In-Reply-To: <20220708061312.25878-1-yung-chuan.liao@linux.intel.com>
References: <20220708061312.25878-1-yung-chuan.liao@linux.intel.com>
Subject: Re: [RESEND PATCH v3 0/2] ASoC/SoundWire: Intel: add sdw BE dai trigger
Message-Id: <165772760890.142759.10751775895640491241.b4-ty@kernel.org>
Date:   Wed, 13 Jul 2022 16:53:28 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 8 Jul 2022 14:13:10 +0800, Bard Liao wrote:
> For SOF IPC4, we need to set pipeline state in BE DAI trigger.
> @Mark, resending this series in case it is lost in your mailbox.
> 
> v2:
>  - Change "#if IS_ENABLED(CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE)" to
>    "if (IS_ENABLED(CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE))"
> 
> [...]

Applied to

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

Thanks!

[1/2] soundwire: Intel: add trigger callback
      commit: 6d1c1a73e1126572de0a8b063fe62fe43786ed59
[2/2] ASoC: SOF: Intel: add trigger callback into sdw_callback
      commit: 2a1be12c4d77d4f7b122568383382e006a60381b

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