From: sashiko-bot@kernel.org
Cc: dmaengine@vger.kernel.org, vkoul@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v2 1/2] dmaengine: hsu: Drop unused platform driver data
Date: Thu, 11 Jun 2026 08:11:05 +0000 [thread overview]
Message-ID: <20260611081105.863831F00893@smtp.kernel.org> (raw)
In-Reply-To: <86a23025da12369034dc7444f43a7763f2e515fb.1781161455.git.ukleinek@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The commit message incorrectly states that it modifies struct pnp_device_id instead of struct pci_device_id.
--
commit 5cb66572eea17e218716d84ce22cd0b73ee38c30
Author: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
dmaengine: hsu: Drop unused platform driver data
This patch drops the unused .driver_data assignments from the
hsu_pci_id_table array. It only modifies the source code representation
and does not affect the compiled output.
> The driver explicitly sets the .driver_data member of struct
> pnp_device_id to zero without relying on that value. Drop these unused
> assignments.
[Severity: Low]
This isn't a bug, but the commit message states that the driver sets the
member of struct pnp_device_id, while the patch actually modifies an
array of struct pci_device_id in drivers/dma/hsu/pci.c. Should the
commit message be updated to reference the correct struct?
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1781161455.git.ukleinek@kernel.org?part=1
next prev parent reply other threads:[~2026-06-11 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 7:45 [PATCH v2 0/2] dmaengine: Use named initializers for arrays of pci_device_id Uwe Kleine-König (The Capable Hub)
2026-06-11 7:45 ` [PATCH v2 1/2] dmaengine: hsu: Drop unused platform driver data Uwe Kleine-König (The Capable Hub)
2026-06-11 8:11 ` sashiko-bot [this message]
2026-06-11 8:30 ` Andy Shevchenko
2026-06-11 7:45 ` [PATCH v2 2/2] dmaengine: Consistently define pci_device_ids using named initializers Uwe Kleine-König (The Capable Hub)
2026-06-11 8:33 ` Andy Shevchenko
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=20260611081105.863831F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--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.