Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31;
From:   Mark Brown <broonie@kernel.org>
To:     agross@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org,
        linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        Vijaya Krishna Nivarthi <quic_vnivarth@quicinc.com>
Cc:     quic_msavaliy@quicinc.com, dianders@chromium.org, mka@chromium.org,
        swboyd@chromium.org, quic_vtanuku@quicinc.com
In-Reply-To: <1696614170-18969-1-git-send-email-quic_vnivarth@quicinc.com>
References: <1696614170-18969-1-git-send-email-quic_vnivarth@quicinc.com>
Subject: Re: [PATCH] spi: spi-geni-qcom: Rename the label unmap_if_dma
Message-Id: <169686978029.107832.8830412614471622963.b4-ty@kernel.org>
Date:   Mon, 09 Oct 2023 17:43:00 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 06 Oct 2023 23:12:50 +0530, Vijaya Krishna Nivarthi wrote:
> The code at unmap_if_dma label doesn't contain unmapping dma anymore but
> has only fsm reset.
> 
> Rename it to reset_if_dma accordingly.
> 
> No functional change.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-geni-qcom: Rename the label unmap_if_dma
      commit: 8a6b446d8a13673bfcf44fbd09d737ae4ccf0bfd

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