From: Frank Li <Frank.li@oss.nxp.com>
To: Pawel Zalewski <pzalewski@thegoodpenguin.co.uk>
Cc: Viresh Kumar <vireshk@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Binbin Zhou <zhoubinbin@loongson.cn>,
Sinan Kaya <okaya@kernel.org>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dma: dw: use designated initializers for acpi_device_id
Date: Tue, 15 Sep 2026 12:33:28 -0400 [thread overview]
Message-ID: <aqlzWNeguqifqIAZ@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260907-acpi-dma-v2-1-0ffe4a007992@thegoodpenguin.co.uk>
On Mon, Sep 07, 2026 at 04:17:43PM +0100, Pawel Zalewski wrote:
> 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.
>
> Signed-off-by: Pawel Zalewski <pzalewski@thegoodpenguin.co.uk>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> drivers/dma/dw/platform.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/dma/dw/platform.c b/drivers/dma/dw/platform.c
> index c63fa52036d7f..5c1c97eb28a4a 100644
> --- a/drivers/dma/dw/platform.c
> +++ b/drivers/dma/dw/platform.c
> @@ -141,14 +141,14 @@ MODULE_DEVICE_TABLE(of, dw_dma_of_id_table);
>
> #ifdef CONFIG_ACPI
> static const struct acpi_device_id dw_dma_acpi_id_table[] = {
> - { "INTL9C60", (kernel_ulong_t)&dw_dma_chip_pdata },
> - { "80862286", (kernel_ulong_t)&dw_dma_chip_pdata },
> - { "808622C0", (kernel_ulong_t)&dw_dma_chip_pdata },
> + { .id = "INTL9C60", .driver_data = (kernel_ulong_t)&dw_dma_chip_pdata },
> + { .id = "80862286", .driver_data = (kernel_ulong_t)&dw_dma_chip_pdata },
> + { .id = "808622C0", .driver_data = (kernel_ulong_t)&dw_dma_chip_pdata },
>
> /* Elkhart Lake iDMA 32-bit (PSE DMA) */
> - { "80864BB4", (kernel_ulong_t)&xbar_chip_pdata },
> - { "80864BB5", (kernel_ulong_t)&xbar_chip_pdata },
> - { "80864BB6", (kernel_ulong_t)&xbar_chip_pdata },
> + { .id = "80864BB4", .driver_data = (kernel_ulong_t)&xbar_chip_pdata },
> + { .id = "80864BB5", .driver_data = (kernel_ulong_t)&xbar_chip_pdata },
> + { .id = "80864BB6", .driver_data = (kernel_ulong_t)&xbar_chip_pdata },
>
> { }
> };
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-09-15 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 15:17 [PATCH v2 0/4] dma: " Pawel Zalewski
2026-09-07 15:17 ` [PATCH v2 1/4] dma: dw: " Pawel Zalewski
2026-09-15 16:33 ` Frank Li [this message]
2026-09-07 15:17 ` [PATCH v2 2/4] dma: loongson: use named " Pawel Zalewski
2026-09-07 15:17 ` [PATCH v2 3/4] dma: qcom: " Pawel Zalewski
2026-09-15 16:34 ` Frank Li
2026-09-16 7:38 ` Pawel Zalewski
2026-09-07 15:17 ` [PATCH v2 4/4] dma: xgene-dmac: " Pawel Zalewski
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=aqlzWNeguqifqIAZ@lizhi-Precision-Tower-5810 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@kernel.org \
--cc=pzalewski@thegoodpenguin.co.uk \
--cc=vireshk@kernel.org \
--cc=vkoul@kernel.org \
--cc=zhoubinbin@loongson.cn \
/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
all inboxes | Powered by JetHome®