Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     matthias.bgg@gmail.com, Trevor Wu <trevor.wu@mediatek.com>,
        tiwai@suse.com
Cc:     Mark Brown <broonie@kernel.org>,
        linux-arm-kernel@lists.infradead.org, dan.carpenter@oracle.com,
        linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
        bicycle.tsai@mediatek.com, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: common: handle NULL case in suspend/resume function
Date:   Fri, 10 Sep 2021 17:08:44 +0100
Message-Id: <163128974013.2897.10752321808133485674.b4-ty@kernel.org>
In-Reply-To: <20210902082111.9287-1-trevor.wu@mediatek.com>
References: <20210902082111.9287-1-trevor.wu@mediatek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 2 Sep 2021 16:21:11 +0800, Trevor Wu wrote:
> When memory allocation for afe->reg_back_up fails, reg_back_up can't
> be used.
> Keep the suspend/resume flow but skip register backup when
> afe->reg_back_up is NULL, in case illegal memory access happens.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: mediatek: common: handle NULL case in suspend/resume function
      commit: 1dd038522615b70f5f8945c5631e9e2fa5bd58b1

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