Linux Serial subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v11 0/7] dmaengine: dw: serialize completion and termination
Date: Fri, 20 Nov 2026 20:24:46 +0000	[thread overview]
Message-ID: <sashiko-outbox-226064@kernel.org> (raw)
In-Reply-To: <20261120-submit-dw-dma-synchronize-v1-v11-0-9b9166bc2cc7@gmail.com>

Sashiko has finished reviewing this 7-patch series:

- Patches 1-3 and 5-7: no issues found.
- Patch 4 ("dmaengine: dw: use virt-dma for descriptor and callb..."): 1
  potential issue (1 Low)

A detailed review has been sent as a separate reply to patch 4.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261120-submit-dw-dma-synchronize-v1-v11-0-9b9166bc2cc7@gmail.com

      parent reply	other threads:[~2026-11-20 20:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 19:29 [PATCH v11 0/7] dmaengine: dw: serialize completion and termination James Hilliard
2026-11-20 19:29 ` [PATCH v11 1/7] dmaengine: dw: Fix XFER bit set, but channel not idle error James Hilliard
2026-11-20 19:29 ` [PATCH v11 2/7] dmaengine: dw: serialize error recovery with channel termination James Hilliard
2026-11-20 19:29 ` [PATCH v11 3/7] dmaengine: dw: embed a virt-dma channel James Hilliard
2026-11-20 19:29 ` [PATCH v11 4/7] dmaengine: dw: use virt-dma for descriptor and callback ownership James Hilliard
2026-11-20 20:08   ` sashiko-bot
2026-11-20 19:29 ` [PATCH v11 5/7] dmaengine: dw: extract hardware-LLP residue calculation James Hilliard
2026-11-20 19:29 ` [PATCH v11 6/7] dmaengine: dw: calculate residue in the status getter James Hilliard
2026-11-20 19:29 ` [PATCH v11 7/7] dmaengine: dw: report residue for queued transfers James Hilliard
2026-11-20 20:24 ` sashiko-bot [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=sashiko-outbox-226064@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=james.hilliard1@gmail.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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