From: Damien Le Moal <dlemoal@kernel.org>
To: sashiko-reviews@lists.linux.dev, Rosen Penev <rosenp@gmail.com>
Cc: cassel@kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: pata_pxa: use devres for DMA channel management
Date: Tue, 21 Jul 2026 08:58:25 +0900 [thread overview]
Message-ID: <7b68dcb2-9b52-42cc-9524-debcb01185d0@kernel.org> (raw)
In-Reply-To: <20260720020148.7A2DA1F000E9@smtp.kernel.org>
On 7/20/26 11:01, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The commit message falsely claims that `ata_host_activate()` registers a managed host detach and that the patch preserves the previous teardown ordering.
> --
>
> --- Patch [1]: [PATCH] ata: pata_pxa: use devres for DMA channel management ---
> commit d581effc5d41a82779ae2b411de235a8efbfb017
> Author: Rosen Penev <rosenp@gmail.com>
>
> ata: pata_pxa: use devres for DMA channel management
>
> Convert the DMA channel request to devm_dma_request_chan() so the
> channel is released automatically on device teardown. This removes
> the explicit dma_release_channel() calls in the probe error paths
> and in pxa_ata_remove().
>
>> Devres releases in LIFO order, so the managed host detach registered
>> by ata_host_activate() runs before the DMA channel is released, which
>> preserves the previous teardown ordering.
>
> [Severity: Medium]
> Is this description accurate regarding the managed host detach and teardown
> ordering?
Rosen,
Can you resend with a fixed up commit message?
Thanks.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2026-07-20 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 1:50 [PATCH] ata: pata_pxa: use devres for DMA channel management Rosen Penev
2026-07-20 2:01 ` sashiko-bot
2026-07-20 23:58 ` Damien Le Moal [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=7b68dcb2-9b52-42cc-9524-debcb01185d0@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=rosenp@gmail.com \
--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