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:     Tommaso Merciai <tommaso.merciai@amarulasolutions.com>
Cc:     linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
        linuxfancy@googlegroups.com, Liam Girdwood <lgirdwood@gmail.com>,
        alsa-devel@alsa-project.org, linux-amarula@amarulasolutions.com,
        Jaroslav Kysela <perex@perex.cz>, Stephen Kitt <steve@sk2.org>
In-Reply-To: <20220825101714.81580-1-tommaso.merciai@amarulasolutions.com>
References: <20220825101714.81580-1-tommaso.merciai@amarulasolutions.com>
Subject: Re: [PATCH] ASoC: max98088: add support for noise gate reg
Message-Id: <166143151246.98448.3045084214547332329.b4-ty@kernel.org>
Date:   Thu, 25 Aug 2022 13:45:12 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 25 Aug 2022 12:17:13 +0200, Tommaso Merciai wrote:
> Add support for Noise Gate Threshold reg (ANTH reg 0x40 bit 4 to 7)
> 
> References:
>  - https://datasheets.maximintegrated.com/en/ds/MAX98089.pdf, p75
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: max98088: add support for noise gate reg
      commit: 671d119e75c8dfbf25c1813a167eeb2616c8acd5

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