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:     james.schulman@cirrus.com, cristian.ciocaltea@collabora.com,
        tiwai@suse.com, lgirdwood@gmail.com, david.rhodes@cirrus.com,
        rf@opensource.cirrus.com, tanureal@opensource.cirrus.com,
        perex@perex.cz
Cc:     kernel@collabora.com, alsa-devel@alsa-project.org,
        patches@opensource.cirrus.com, linux-kernel@vger.kernel.org
In-Reply-To: <20220621213819.262537-1-cristian.ciocaltea@collabora.com>
References: <20220621213819.262537-1-cristian.ciocaltea@collabora.com>
Subject: Re: [PATCH] ASoC: cs35l41: Add support for CLSA3541 ACPI device ID
Message-Id: <165608133945.445804.16792879989339290449.b4-ty@kernel.org>
Date:   Fri, 24 Jun 2022 15:35:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 22 Jun 2022 00:38:19 +0300, Cristian Ciocaltea wrote:
> Add support for the CLSA3541 ACPI device ID used on Valve's Steam Deck.
> The driver is fully compatible with the indicated hardware, hence no
> additional changes are required.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: cs35l41: Add support for CLSA3541 ACPI device ID
      commit: 658e95953075ca781ef8712d0a3203e485888c7f

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