[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169686978029.107832.8830412614471622963.b4-ty@kernel.org>
Date: Mon, 09 Oct 2023 17:43:00 +0100
From: Mark Brown <broonie@...nel.org>
To: agross@...nel.org, andersson@...nel.org, konrad.dybcio@...aro.org,
linux-arm-msm@...r.kernel.org, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org,
Vijaya Krishna Nivarthi <quic_vnivarth@...cinc.com>
Cc: quic_msavaliy@...cinc.com, dianders@...omium.org, mka@...omium.org,
swboyd@...omium.org, quic_vtanuku@...cinc.com
Subject: Re: [PATCH] spi: spi-geni-qcom: Rename the label unmap_if_dma
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
Powered by blists - more mailing lists