[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169031736194.1617289.5213259488916570827.b4-ty@kernel.org>
Date: Tue, 25 Jul 2023 21:36:01 +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,
dan.carpenter@...aro.org
Subject: Re: [PATCH 0/4] spi: spi-qcom-qspi: Follow-up patches to DMA mode
support
On Tue, 25 Jul 2023 17:18:05 +0530, Vijaya Krishna Nivarthi wrote:
> This patch series adds 4 follow-up changes to DMA mode support.
> 1. Handles write failure in some cases by averting a race condition
> 2. Handles static checker warning
> 3. Adds a memory barrier to avoid a possible data out of sync case
> 4. Book keeping change
>
> Vijaya Krishna Nivarthi (4):
> spi: spi-qcom-qspi: Ignore disabled interrupts' status in isr
> spi: spi-qcom-qspi: Use GFP_ATOMIC flag while allocating for
> descriptor
> spi: spi-qcom-qspi: Call dma_wmb() after setting up descriptors
> spi: spi-qcom-qspi: Add DMA_CHAIN_DONE to ALL_IRQS
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/4] spi: spi-qcom-qspi: Ignore disabled interrupts' status in isr
commit: 17aaf9ea07b656016316dc37716e987742b3e296
[2/4] spi: spi-qcom-qspi: Use GFP_ATOMIC flag while allocating for descriptor
commit: f7ba36d399c4558f36886adff9400be591b245f6
[3/4] spi: spi-qcom-qspi: Call dma_wmb() after setting up descriptors
commit: cfb81f2243b25a0d79accc6510ad66c5c5ad99ba
[4/4] spi: spi-qcom-qspi: Add DMA_CHAIN_DONE to ALL_IRQS
commit: 916a4edf3daed845b1e5d6cf0578a7e43c6f520e
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