From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: cassel@kernel.org, linux-ide@vger.kernel.org, dlemoal@kernel.org
Subject: Re: [PATCHv3 1/5] ata: sata_dwc_460ex: use platform_get_irq()
Date: Thu, 09 Jul 2026 02:47:12 +0000 [thread overview]
Message-ID: <20260709024713.58EC71F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260709023202.2132165-2-rosenp@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch removes the local variable `np` from `sata_dwc_probe()`, causing a build failure when `CONFIG_SATA_DWC_OLD_DMA` is enabled.
--
--- Patch [1]: [PATCHv3 1/5] ata: sata_dwc_460ex: use platform_get_irq() ---
commit 74bc1be9c4385029a4079d000bf78ff4452fc266
Author: Rosen Penev <rosenp@gmail.com>
ata: sata_dwc_460ex: use platform_get_irq()
This commit replaces irq_of_parse_and_map() with platform_get_irq() in both
sata_dwc_dma_init_old() and sata_dwc_probe(). It improves error handling for
IRQs and removes the unnecessary include of of_irq.h.
> diff --git a/drivers/ata/sata_dwc_460ex.c b/drivers/ata/sata_dwc_460ex.c
> index 4fc22ce4bd9aa..442c6e9d06e0a 100644
> --- a/drivers/ata/sata_dwc_460ex.c
> +++ b/drivers/ata/sata_dwc_460ex.c
[ ... ]
> @@ -1126,7 +1122,6 @@ static const struct ata_port_info sata_dwc_port_info[] = {
> static int sata_dwc_probe(struct platform_device *ofdev)
> {
> struct device *dev = &ofdev->dev;
> - struct device_node *np = dev->of_node;
> struct sata_dwc_device *hsdev;
> u32 idr, versionr;
> char *ver = (char *)&versionr;
[ ... ]
> @@ -1173,11 +1168,9 @@ static int sata_dwc_probe(struct platform_device *ofdev)
> sata_dwc_enable_interrupts(hsdev);
>
> /* Get SATA interrupt number */
> - irq = irq_of_parse_and_map(np, 0);
> - if (!irq) {
> - dev_err(dev, "no SATA DMA irq\n");
> - return -ENODEV;
> - }
> + irq = platform_get_irq(ofdev, 0);
> + if (irq < 0)
> + return irq;
>
> #ifdef CONFIG_SATA_DWC_OLD_DMA
> if (!of_property_present(np, "dmas")) {
[Severity: Low]
Will this cause a build failure when compiling with CONFIG_SATA_DWC_OLD_DMA
enabled?
The earlier hunk removes the declaration of the np variable, but it appears
to still be referenced here in sata_dwc_probe(). Could dev->of_node be passed
to of_property_present() instead to avoid an undeclared identifier error?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260709023202.2132165-2-rosenp@gmail.com?part=1
next prev parent reply other threads:[~2026-07-09 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 2:31 [PATCHv3 0/5] ata: sata_dwc_460ex: cleanups and interrupt ordering fix Rosen Penev
2026-07-09 2:31 ` [PATCHv3 1/5] ata: sata_dwc_460ex: use platform_get_irq() Rosen Penev
2026-07-09 2:47 ` sashiko-bot [this message]
2026-07-09 5:23 ` Rosen Penev
2026-07-09 2:31 ` [PATCHv3 2/5] ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered Rosen Penev
2026-07-09 2:32 ` [PATCHv3 3/5] ata: sata_dwc_460ex: fix clear_interrupt_bit() clearing all pending interrupts Rosen Penev
2026-07-09 2:32 ` [PATCHv3 4/5] ata: sata_dwc_460ex: fix infinite loop in NCQ tag completion bit-scanning Rosen Penev
2026-07-09 2:32 ` [PATCHv3 5/5] ata: sata_dwc_460ex: disable SATA interrupts on device removal Rosen Penev
2026-07-09 2:55 ` 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=20260709024713.58EC71F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=cassel@kernel.org \
--cc=dlemoal@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