All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Sascha Bischoff <sascha.bischoff@arm.com>,
	Timothy Hayes <timothy.hayes@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] irqchip/gic-v5: iwb: Remove module boilerplate
Date: Fri, 01 Aug 2025 13:24:57 +0100	[thread overview]
Message-ID: <86v7n76xgm.wl-maz@kernel.org> (raw)
In-Reply-To: <20250801-gic-v5-fixes-6-17-v1-2-4fcedaccf9e6@kernel.org>

On Fri, 01 Aug 2025 08:58:19 +0100,
Lorenzo Pieralisi <lpieralisi@kernel.org> wrote:
> 
> The IWB driver cannot be compiled as a module and is as matter of fact a
> builtin driver at present.

What is blocking that?

> 
> Make it explicitly so by removing useless boilerplate and by using the
> builtin_platform_driver() helper to initialize its registration
> functions.
> 
> Signed-off-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Marc Zyngier <maz@kernel.org>
> ---
>  drivers/irqchip/irq-gic-v5-iwb.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-gic-v5-iwb.c b/drivers/irqchip/irq-gic-v5-iwb.c
> index ad9fdc14d1c6..c3a3b30e9f4e 100644
> --- a/drivers/irqchip/irq-gic-v5-iwb.c
> +++ b/drivers/irqchip/irq-gic-v5-iwb.c
> @@ -263,7 +263,6 @@ static const struct of_device_id gicv5_iwb_of_match[] = {
>  	{ .compatible = "arm,gic-v5-iwb" },
>  	{ /* END */ }
>  };
> -MODULE_DEVICE_TABLE(of, gicv5_iwb_of_match);
>  
>  static struct platform_driver gicv5_iwb_platform_driver = {
>  	.driver = {
> @@ -274,4 +273,4 @@ static struct platform_driver gicv5_iwb_platform_driver = {
>  	.probe				= gicv5_iwb_device_probe,
>  };
>  
> -module_platform_driver(gicv5_iwb_platform_driver);
> +builtin_platform_driver(gicv5_iwb_platform_driver);
> 

I'd rather we make the driver buildable as a module if at all
possible, instead of forcing it as built-in for everyone. It would
definitely help pipe-cleaning the potential missing dependencies.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.


  reply	other threads:[~2025-08-01 13:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01  7:58 [PATCH 0/3] irqchip/gic-v5: Minor clean-ups/fixes Lorenzo Pieralisi
2025-08-01  7:58 ` [PATCH 1/3] irqchip/gic-v5: iwb: Fix iounmap probe failure path Lorenzo Pieralisi
2025-08-01 12:26   ` Marc Zyngier
2025-08-05  8:48   ` [tip: irq/urgent] " tip-bot2 for Lorenzo Pieralisi
2025-08-01  7:58 ` [PATCH 2/3] irqchip/gic-v5: iwb: Remove module boilerplate Lorenzo Pieralisi
2025-08-01 12:24   ` Marc Zyngier [this message]
2025-08-01 14:04     ` Lorenzo Pieralisi
2025-08-01  7:58 ` [PATCH 3/3] irqchip/gic-v5: Remove IRQD_RESEND_WHEN_IN_PROGRESS for ITS IRQs Lorenzo Pieralisi
2025-08-01 12:30   ` Marc Zyngier
2025-08-01 14:01     ` Lorenzo Pieralisi
2025-08-05  8:48   ` [tip: irq/urgent] " tip-bot2 for Lorenzo Pieralisi
2025-08-05  9:30 ` [PATCH 0/3] irqchip/gic-v5: Minor clean-ups/fixes Lorenzo Pieralisi

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=86v7n76xgm.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=sascha.bischoff@arm.com \
    --cc=tglx@linutronix.de \
    --cc=timothy.hayes@arm.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 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.