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 v5 1/5] serial: 8250_omap: separate locked TX DMA completion processing
Date: Sat, 24 Oct 2026 06:45:32 +0000	[thread overview]
Message-ID: <sashiko-outbox-183572@kernel.org> (raw)
In-Reply-To: <20261024-submit-serial-8250-dma-cancel-v1-v5-1-9e52968928d2@gmail.com>

> Separate the port-locked completion processing from the DMA callback
> wrapper. Keep the shutdown check and locking in the callback, and retain
> the existing FIFO accounting, delayed register restore and THRI handling
> in the helper.
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261024-submit-serial-8250-dma-cancel-v1-v5-0-9e52968928d2@gmail.com?part=1


  reply	other threads:[~2026-10-24  6:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  6:40 [PATCH v5 0/5] serial: 8250: serialize DMA cancellation with buffer reuse James Hilliard
2026-10-24  6:40 ` [PATCH v5 1/5] serial: 8250_omap: separate locked TX DMA completion processing James Hilliard
2026-10-24  6:45   ` sashiko-bot [this message]
2026-10-24  6:40 ` [PATCH v5 2/5] serial: serialize asynchronous write wakeups with the port lock James Hilliard
2026-10-24  6:50   ` sashiko-bot
2026-10-25  5:10   ` Maciej W. Rozycki
2026-10-25 15:09     ` Andy Shevchenko
2026-10-25 20:25       ` James Hilliard
2026-10-25 20:44         ` Andy Shevchenko
2026-10-25 22:11           ` James Hilliard
2026-10-26  9:31             ` Andy Shevchenko
2026-10-26 16:45               ` James Hilliard
2026-10-26 19:53                 ` Andy Shevchenko
2026-10-26 19:59                   ` James Hilliard
2026-10-26 20:17                     ` Greg Kroah-Hartman
2026-10-26 20:24                       ` James Hilliard
2026-10-26 20:40                         ` Greg Kroah-Hartman
2026-10-26 20:49                           ` James Hilliard
2026-10-26 21:23                             ` Andy Shevchenko
2026-10-26 21:36                             ` Maciej W. Rozycki
2026-10-26 20:18                     ` Andy Shevchenko
2026-10-25 18:47     ` James Hilliard
2026-10-24  6:40 ` [PATCH v5 3/5] serial: core: allow drivers to reserve flushed transmit storage James Hilliard
2026-10-24  7:26   ` sashiko-bot
2026-10-24  6:40 ` [PATCH v5 4/5] serial: 8250: drain canceled TX DMA before reusing its buffer James Hilliard
2026-10-24  6:55   ` sashiko-bot
2026-10-24  6:40 ` [PATCH v5 5/5] serial: 8250: retire canceled RX DMA before reusing the receive buffer James Hilliard
2026-10-24  7:24   ` sashiko-bot

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-183572@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