DMA Engine development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Pawel Zalewski" <pzalewski@thegoodpenguin.co.uk>
Cc: vkoul@kernel.org, Frank.Li@kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH v3 2/4] dmaengine: loongson: use named initializers for acpi_device_id
Date: Wed, 16 Sep 2026 15:35:01 +0000	[thread overview]
Message-ID: <20260916153501.9CFC51F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916-acpi-dma-v3-2-0dac05654967@thegoodpenguin.co.uk>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dmaengine: loongson: incomplete unification of list terminators
--

commit 4321a78607f15fa601095e26975f8fbd9cdea572
Author: Pawel Zalewski <pzalewski@thegoodpenguin.co.uk>

dmaengine: loongson: use named initializers for acpi_device_id

Use a named initializer for the acpi_device_id fields which makes the code
more readable and consistent with how lists are initialized in the rest of
the kernel code base.

Unify the list terminator to have a single space between the brackets and
no trailing comma.

> diff --git a/drivers/dma/loongson/loongson2-apb-cmc-dma.c b/drivers/dma/loongson/loongson2-apb-cmc-dma.c
> index 1c9a542edc859..70880625c6e92 100644
> --- a/drivers/dma/loongson/loongson2-apb-cmc-dma.c
> +++ b/drivers/dma/loongson/loongson2-apb-cmc-dma.c
> @@ -709,8 +709,8 @@ static const struct of_device_id loongson2_cmc_dma_of_match[] = {
>  MODULE_DEVICE_TABLE(of, loongson2_cmc_dma_of_match);
>  
>  static const struct acpi_device_id loongson2_cmc_dma_acpi_match[] = {
> -	{ "LOON0014", .driver_data = (kernel_ulong_t)&ls2k3000_cmc_dma_config },
> -	{ /* sentinel */ }
> +	{ .id = "LOON0014", .driver_data = (kernel_ulong_t)&ls2k3000_cmc_dma_config },
> +	{ }

[Severity: Low]
The commit message mentions unifying the list terminator, but does this miss
the OF match table located immediately above?

drivers/dma/loongson/loongson2-apb-cmc-dma.c:
static const struct of_device_id loongson2_cmc_dma_of_match[] = {
	...
	{ .compatible = "loongson,ls2k3000-dma", .data = &ls2k3000_cmc_dma_config },
	{ /* sentinel */ }
};

Should the list terminator here also be updated for consistency?

>  };
>  MODULE_DEVICE_TABLE(acpi, loongson2_cmc_dma_acpi_match);

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260916-acpi-dma-v3-0-0dac05654967@thegoodpenguin.co.uk?part=2

  reply	other threads:[~2026-09-16 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 15:27 [PATCH v3 0/4] dmaengine: use designated initializers for acpi_device_id Pawel Zalewski
2026-09-16 15:27 ` [PATCH v3 1/4] dmaengine: dw: " Pawel Zalewski
2026-09-16 15:27 ` [PATCH v3 2/4] dmaengine: loongson: use named " Pawel Zalewski
2026-09-16 15:35   ` sashiko-bot [this message]
2026-09-16 19:12   ` Frank Li
2026-09-16 15:27 ` [PATCH v3 3/4] dmaengine: qcom: " Pawel Zalewski
2026-09-16 15:33   ` sashiko-bot
2026-09-16 19:12   ` Frank Li
2026-09-16 15:27 ` [PATCH v3 4/4] dmaengine: xgene-dma: " Pawel Zalewski
2026-09-16 19:13   ` Frank Li
2026-10-05 15:43 ` [PATCH v3 0/4] dmaengine: use designated " Vinod Koul

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=20260916153501.9CFC51F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=pzalewski@thegoodpenguin.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox