The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Pandey, Radhey Shyam" <radheys@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Zhou Wang <wangzhou1@hisilicon.com>,
	Longfang Liu <liulongfang@huawei.com>,
	Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: Move MODULE_DEVICE_TABLE next to the table itself
Date: Fri, 8 May 2026 16:57:47 +0530	[thread overview]
Message-ID: <2bae4897-7d94-4daa-ade8-7d858e1c25e1@amd.com> (raw)
In-Reply-To: <20260505102932.190219-2-krzysztof.kozlowski@oss.qualcomm.com>

On 5/5/2026 3:59 PM, Krzysztof Kozlowski wrote:
> By convention MODULE_DEVICE_TABLE() immediately follows the ID table it
> exports, because this is easier to read and verify.  It also makes more
> sense since #ifdef for ACPI or OF could hide both of them.
> 
> Most of the privers already have this correctly placed, so adjust
> the missing ones.  No functional impact.

Nit - drivers

With that fixed .
Reviewed-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>

> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
>   drivers/dma/hisi_dma.c | 2 +-
>   drivers/dma/pch_dma.c  | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/dma/hisi_dma.c b/drivers/dma/hisi_dma.c
> index 32a0e95c6a20..28bf818f9aa6 100644
> --- a/drivers/dma/hisi_dma.c
> +++ b/drivers/dma/hisi_dma.c
> @@ -1037,6 +1037,7 @@ static const struct pci_device_id hisi_dma_pci_tbl[] = {
>   	{ PCI_DEVICE(PCI_VENDOR_ID_HUAWEI, 0xa122) },
>   	{ 0, }
>   };
> +MODULE_DEVICE_TABLE(pci, hisi_dma_pci_tbl);
>   
>   static struct pci_driver hisi_dma_pci_driver = {
>   	.name		= "hisi_dma",
> @@ -1050,4 +1051,3 @@ MODULE_AUTHOR("Zhou Wang <wangzhou1@hisilicon.com>");
>   MODULE_AUTHOR("Zhenfa Qiu <qiuzhenfa@hisilicon.com>");
>   MODULE_DESCRIPTION("HiSilicon Kunpeng DMA controller driver");
>   MODULE_LICENSE("GPL v2");
> -MODULE_DEVICE_TABLE(pci, hisi_dma_pci_tbl);
> diff --git a/drivers/dma/pch_dma.c b/drivers/dma/pch_dma.c
> index e9fbfd5a3d51..bf805f1024f6 100644
> --- a/drivers/dma/pch_dma.c
> +++ b/drivers/dma/pch_dma.c
> @@ -970,6 +970,7 @@ static const struct pci_device_id pch_dma_id_table[] = {
>   	{ PCI_VDEVICE(ROHM, PCI_DEVICE_ID_ML7831_DMA2_4CH), 4}, /* SPI */
>   	{ 0, },
>   };
> +MODULE_DEVICE_TABLE(pci, pch_dma_id_table);
>   
>   static SIMPLE_DEV_PM_OPS(pch_dma_pm_ops, pch_dma_suspend, pch_dma_resume);
>   
> @@ -987,4 +988,3 @@ MODULE_DESCRIPTION("Intel EG20T PCH / LAPIS Semicon ML7213/ML7223/ML7831 IOH "
>   		   "DMA controller driver");
>   MODULE_AUTHOR("Yong Wang <yong.y.wang@intel.com>");
>   MODULE_LICENSE("GPL v2");
> -MODULE_DEVICE_TABLE(pci, pch_dma_id_table);


      parent reply	other threads:[~2026-05-08 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 10:29 [PATCH] dmaengine: Move MODULE_DEVICE_TABLE next to the table itself Krzysztof Kozlowski
2026-05-06 19:01 ` Frank Li
2026-05-08 11:27 ` Pandey, Radhey Shyam [this message]

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=2bae4897-7d94-4daa-ade8-7d858e1c25e1@amd.com \
    --to=radheys@amd.com \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liulongfang@huawei.com \
    --cc=vkoul@kernel.org \
    --cc=wangzhou1@hisilicon.com \
    /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