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:     alsa-devel@alsa-project.org,
        Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Cc:     Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
        Sunil-kumar.Dommati@amd.com, Jaroslav Kysela <perex@perex.cz>,
        Alexander.Deucher@amd.com, dan.carpenter@oracle.com,
        Takashi Iwai <tiwai@suse.com>,
        Liam Girdwood <lgirdwood@gmail.com>, krisman@collabora.com,
        open list <linux-kernel@vger.kernel.org>
In-Reply-To: <20220225193054.24916-1-Vijendar.Mukunda@amd.com>
References: <20220225193054.24916-1-Vijendar.Mukunda@amd.com>
Subject: Re: [PATCH V2 1/4] ASoC: amd: vg: fix for pm resume callback sequence
Message-Id: <164607575019.3538791.4372801541502826813.b4-ty@kernel.org>
Date:   Mon, 28 Feb 2022 19:15:50 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sat, 26 Feb 2022 01:00:22 +0530, Vijendar Mukunda wrote:
> The previous condition is used to cross check only the active
> stream status for I2S HS instance playback and capture use cases.
> 
> Modified logic to invoke sequence for two i2s controller instances.
> 
> This also fixes warnings reported by kernel robot:
> "warning: variable 'frmt_val' set but not used"
> "warning: variable 'reg_val' set but not used"
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: amd: vg: fix for pm resume callback sequence
      commit: 83b713619ee1b15e09eae11a92a7f3305534223d
[2/4] ASoC: amd: vg: update DAI link name
      commit: 5363d7304e31692f8f6da86ed7a49d3c28a2e32a
[3/4] ASoC: amd: vg: remove warnings and errors pointed out by checkpatch pl
      commit: 728a592619cfb9be8b66600d04ef9fee9237fe7e
[4/4] ASoC: amd: vangogh: fix uninitialized symbol warning in machine driver
      commit: 6f989800639a7a29ab9a02e165b04dc144dd4f2b

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