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:     festevam@gmail.com, alsa-devel@alsa-project.org,
        lgirdwood@gmail.com, nicoleotsuka@gmail.com, perex@perex.cz,
        shengjiu.wang@gmail.com, Xiubo.Lee@gmail.com, tiwai@suse.com,
        shengjiu.wang@nxp.com
Cc:     linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
In-Reply-To: <1653284661-18964-1-git-send-email-shengjiu.wang@nxp.com>
References: <1653284661-18964-1-git-send-email-shengjiu.wang@nxp.com>
Subject: Re: [PATCH] ASoC: fsl_sai: Fix FSL_SAI_xDR/xFR definition
Message-Id: <165332675410.2124944.12107532437710717569.b4-ty@kernel.org>
Date:   Mon, 23 May 2022 18:25:54 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 23 May 2022 13:44:21 +0800, Shengjiu Wang wrote:
> There are multiple xDR and xFR registers, the index is
> from 0 to 7. FSL_SAI_xDR and FSL_SAI_xFR is abandoned,
> replace them with FSL_SAI_xDR0 and FSL_SAI_xFR0.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: fsl_sai: Fix FSL_SAI_xDR/xFR definition
      commit: e4dd748dc87cf431af7b3954963be0d9f6150217

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