Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Mark Brown <broonie@kernel.org>
To:     tiwai@suse.com, arnaud.pouliquen@foss.st.com,
        tangbin@cmss.chinamobile.com, alexandre.torgue@foss.st.com,
        lgirdwood@gmail.com, olivier.moysan@foss.st.com,
        mcoquelin.stm32@gmail.com, perex@perex.cz
Cc:     linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        linux-stm32@st-md-mailman.stormreply.com
In-Reply-To: <20220525135023.6792-1-tangbin@cmss.chinamobile.com>
References: <20220525135023.6792-1-tangbin@cmss.chinamobile.com>
Subject: Re: [PATCH] ASoC: stm32: sai: Remove useless define
Message-Id: <165459873158.301808.10178152616958894169.b4-ty@kernel.org>
Date:   Tue, 07 Jun 2022 11:45:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 25 May 2022 21:50:23 +0800, Tang Bin wrote:
> STM_SAI_IS_SUB_B(x) and STM_SAI_BLOCK_NAME(x) are
> not being used, so remove them.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: stm32: sai: Remove useless define
      commit: bf1ebcddcb19a1b6d6d8b75b75626197a5a76d4f

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