All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: dmaengine@vger.kernel.org, vkoul@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCHv2] dmaengine: bestcomm: use platform machinery to get irq
Date: Wed, 16 Sep 2026 22:52:40 +0000	[thread overview]
Message-ID: <20260916225241.3983C1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916224156.276511-1-rosenp@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] misc: commit message and code mismatch regarding devm_platform_get_and_ioremap_resource
--

commit e9aa0bc87e702e8cdbc8918ca965897d4edffc03
Author: Rosen Penev <rosenp@gmail.com>

dmaengine: bestcomm: use platform machinery to get irq

This commit updates the bestcomm driver to use platform_get_irq() for
interrupt mapping and replaces of_node references with platform_device. It
also removes the manual device tree node reference counting.

> Replace the open-coded resource lookup, request_mem_region, ioremap and
> the manual iounmap/release_mem_region cleanup in probe/remove with the
> managed devm_platform_get_and_ioremap_resource() helper. This removes the
> now-unused error-unmap/release paths and simplifies the driver.

[Severity: Medium]
Is this paragraph in the commit message accurate for this patch?

Looking at mpc52xx_bcom_probe() in drivers/dma/bestcomm/bestcomm.c around
line 374, the devm_platform_get_and_ioremap_resource() call already exists
prior to this patch (having been introduced in a prior commit,
0a8dda0a15d392).

Since this patch does not actually contain the changes described in this
paragraph, could the commit message be updated to only reflect the changes
introduced here?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260916224156.276511-1-rosenp@gmail.com?part=1

  reply	other threads:[~2026-09-16 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 22:41 [PATCHv2] dmaengine: bestcomm: use platform machinery to get irq Rosen Penev
2026-09-16 22:52 ` sashiko-bot [this message]
2026-09-17  3:25 ` Frank Li
2026-09-18  0:16   ` Rosen Penev
2026-09-18  6:16     ` Christophe Leroy (CS GROUP)

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=20260916225241.3983C1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=rosenp@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.