Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>, Thomas Gleixner <tglx@linutronix.de>
Cc: "Arnd Bergmann" <arnd@arndb.de>, "Lee Jones" <lee@kernel.org>,
	"Aaro Koskinen" <aaro.koskinen@iki.fi>,
	"Andreas Kemnade" <andreas@kemnade.info>,
	"Kevin Hilman" <khilman@baylibre.com>,
	"Roger Quadros" <rogerq@kernel.org>,
	"Tony Lindgren" <tony@atomide.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Chen Ni" <nichen@iscas.ac.cn>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] mfd: fix building without CONFIG_OF
Date: Thu, 22 May 2025 07:57:45 +0200	[thread overview]
Message-ID: <b43fea90-2406-4c8a-a499-4da276883a68@kernel.org> (raw)
In-Reply-To: <20250520154106.2019525-1-arnd@kernel.org>

On 20. 05. 25, 17:40, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> Using the of_fwnode_handle() means that local 'node' variables are unused
> whenever CONFIG_OF is disabled for compile testing:
> 
> drivers/mfd/88pm860x-core.c: In function 'device_irq_init':
> drivers/mfd/88pm860x-core.c:576:29: error: unused variable 'node' [-Werror=unused-variable]
>    576 |         struct device_node *node = i2c->dev.of_node;
>        |                             ^~~~
> drivers/mfd/max8925-core.c: In function 'max8925_irq_init':
> drivers/mfd/max8925-core.c:659:29: error: unused variable 'node' [-Werror=unused-variable]
>    659 |         struct device_node *node = chip->dev->of_node;
>        |                             ^~~~
> drivers/mfd/twl4030-irq.c: In function 'twl4030_init_irq':
> drivers/mfd/twl4030-irq.c:679:46: error: unused variable 'node' [-Werror=unused-variable]
>    679 |         struct                  device_node *node = dev->of_node;
>        |                                              ^~~~
> 
> Replace these with the corresponding dev_fwnode() lookups that
> keep the code simpler in addition to avoiding the warnings.

Reviewed-by: Jiri Slaby <jirislaby@kernel.org>

Exactly the same as I have, except:

...
> --- a/drivers/mfd/max8925-core.c
> +++ b/drivers/mfd/max8925-core.c

> @@ -682,8 +681,9 @@ static int max8925_irq_init(struct max8925_chip *chip, int irq,
>   		return -EBUSY;
>   	}
>   
> -	irq_domain_create_legacy(of_fwnode_handle(node), MAX8925_NR_IRQS, chip->irq_base, 0,
> -				 &max8925_irq_domain_ops, chip);
> +	irq_domain_create_legacy(dev_fwnode(chip->dev), MAX8925_NR_IRQS,
> +				 chip->irq_base, 0, &max8925_irq_domain_ops,
> +				 chip);

I used 100 columns -- without actually adding a line break and reflowing.

thanks,
-- 
js
suse labs

  reply	other threads:[~2025-05-22  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 15:40 [PATCH] mfd: fix building without CONFIG_OF Arnd Bergmann
2025-05-22  5:57 ` Jiri Slaby [this message]
2025-06-12 10:01 ` (subset) " Lee Jones

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=b43fea90-2406-4c8a-a499-4da276883a68@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=khilman@baylibre.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nichen@iscas.ac.cn \
    --cc=rogerq@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony@atomide.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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