Received-SPF: pass (google.com: domain of linux-kernel+bounces-137623-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Precedence: bulk
MIME-Version: 1.0
Date: Tue, 09 Apr 2024 22:51:05 +0200
From: Dragan Simic <dsimic@manjaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, lgirdwood@gmail.com, perex@perex.cz,
 tiwai@suse.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: pcm: perform power-down delay checks a bit faster
In-Reply-To: <171269542042.178415.9248384379060261944.b4-ty@kernel.org>
References: <90ae761a5b99640ece48363a7099ac2cf402bd37.1712684592.git.dsimic@manjaro.org>
 <171269542042.178415.9248384379060261944.b4-ty@kernel.org>
Message-ID: <772a45aeefeb0e63b85d9af17c971e2c@manjaro.org>
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit

On 2024-04-09 22:43, Mark Brown wrote:
> On Tue, 09 Apr 2024 19:56:36 +0200, Dragan Simic wrote:
>> When checking whether the power-down delay should be ignored for a 
>> specific
>> PCM runtime, there's no need to keep going through all DAI link 
>> components
>> after any of them is found to be configured to use the power-down 
>> delay.
>> 
>> While there, fix a small typo in one of the comment blocks.
>> 
>> 
>> [...]
> 
> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git 
> for-next
> 
> Thanks!
> 
> [1/1] ASoC: pcm: perform power-down delay checks a bit faster
>       commit: f78bf2c933c9cb3b61215378664f83c5abd25374

Great, thanks!

> 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