From: Vinod Koul <vkoul@kernel.org>
To: Christian Lugnberg <christian.lugnberg@soundtrack.io>
Cc: Frank.Li@kernel.org, wens@kernel.org, jernej.skrabec@gmail.com,
samuel@sholland.org, dmaengine@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] dmaengine: sun6i: Fix two bugs in the DMA status path
Date: Thu, 10 Sep 2026 19:36:51 +0530 [thread overview]
Message-ID: <178904921191.109109.5746892619101559603.b4-ty@kernel.org> (raw)
In-Reply-To: <20260817135723.12807-1-christian.lugnberg@soundtrack.io>
On Mon, 17 Aug 2026 15:51:21 +0200, Christian Lugnberg wrote:
> Thank you for the review, Frank.
>
> Changes in v3:
> - Patch 1: trim commit message to the root-cause explanation and fix
> description, dropping the debug/reproduction part per feedback
> - Patch 2: unchanged since v2
>
> [...]
Applied, thanks!
[1/2] dmaengine: sun6i: fix non-atomic read of DMA position registers
commit: c90b6973daa37f4c283342dff881ae001dea4fe6
[2/2] dmaengine: sun6i: fix undefined behaviour in sun6i_dma_tx_status
commit: 9096bdc8d930147f7c39a493a859acbd3a8485d8
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-09-10 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 13:51 [PATCH v3 0/2] dmaengine: sun6i: Fix two bugs in the DMA status path Christian Lugnberg
2026-08-17 13:51 ` [PATCH v3 1/2] dmaengine: sun6i: fix non-atomic read of DMA position registers Christian Lugnberg
2026-08-17 14:30 ` Frank Li
2026-08-17 13:51 ` [PATCH v3 2/2] dmaengine: sun6i: fix undefined behaviour in sun6i_dma_tx_status Christian Lugnberg
2026-08-17 14:32 ` Frank Li
2026-09-10 14:06 ` Vinod Koul [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178904921191.109109.5746892619101559603.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=christian.lugnberg@soundtrack.io \
--cc=dmaengine@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=wens@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox