Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Mark Brown <broonie@kernel.org>
To:     tiwai@suse.com, quic_srivasam@quicinc.com,
        srinivas.kandagatla@linaro.org, robh+dt@kernel.org,
        judyhsiao@chromium.org, bjorn.andersson@linaro.org,
        swboyd@chromium.org, perex@perex.cz, linux-kernel@vger.kernel.org,
        bgoswami@quicinc.com, alsa-devel@alsa-project.org,
        devicetree@vger.kernel.org, quic_plai@quicinc.com,
        lgirdwood@gmail.com, quic_rohkumar@quicinc.com,
        linux-arm-msm@vger.kernel.org, agross@kernel.org
In-Reply-To: <1653660608-27245-1-git-send-email-quic_srivasam@quicinc.com>
References: <1653660608-27245-1-git-send-email-quic_srivasam@quicinc.com>
Subject: Re: [PATCH] ASoC: qcom: lpass-platform: Update VMA access permissions in mmap callback
Message-Id: <165408713769.3032499.9376939250680150345.b4-ty@kernel.org>
Date:   Wed, 01 Jun 2022 14:38:57 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 27 May 2022 19:40:08 +0530, Srinivasa Rao Mandadapu wrote:
> Replace page protection permissions from noncashed to writecombine,
> in lpass codec DMA path mmp callabck, to support 64 bit chromeOS.
> Avoid SIGBUS error in userspace caused by noncached permissions in
> 64 bit chromeOS.
> 
> 

Applied to

   broonie/sound.git for-linus

Thanks!

[1/1] ASoC: qcom: lpass-platform: Update VMA access permissions in mmap callback
      commit: ef8d89b83bf453ea9cc3c4873a84b50ff334f797

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