From: Lee Jones <lee@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jiri Slaby <jirislaby@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>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] mfd: Remove node variables that are unused with CONFIG_OF=n
Date: Thu, 19 Jun 2025 11:06:27 +0100 [thread overview]
Message-ID: <20250619100627.GD587864@google.com> (raw)
In-Reply-To: <20250613160600.GA228083@ax162>
On Fri, 13 Jun 2025, Nathan Chancellor wrote:
> On Fri, Jun 13, 2025 at 02:39:05PM +0100, Lee Jones wrote:
> > On Wed, 28 May 2025, Nathan Chancellor wrote:
> >
> > > Hi Thomas,
> > >
> > > On Thu, May 08, 2025 at 04:57:24PM +0100, Nathan Chancellor wrote:
> > > > A recent cleanup introduced a few instances of -Wunused-variable in
> > > > configurations without CONFIG_OF because of_fwnode_handle() does not
> > > > reference its argument in that case:
> > > >
> > > > drivers/mfd/twl4030-irq.c: In function 'twl4030_init_irq':
> > > > drivers/mfd/twl4030-irq.c:679:46: warning: unused variable 'node' [-Wunused-variable]
> > > > 679 | struct device_node *node = dev->of_node;
> > > > | ^~~~
> > > > drivers/mfd/max8925-core.c: In function 'max8925_irq_init':
> > > > drivers/mfd/max8925-core.c:659:29: warning: unused variable 'node' [-Wunused-variable]
> > > > 659 | struct device_node *node = chip->dev->of_node;
> > > > | ^~~~
> > > > drivers/mfd/88pm860x-core.c: In function 'device_irq_init':
> > > > drivers/mfd/88pm860x-core.c:576:29: warning: unused variable 'node' [-Wunused-variable]
> > > > 576 | struct device_node *node = i2c->dev.of_node;
> > > > | ^~~~
> > >
> > > These warnings are now present in mainline after the merge of the
> > > irq/cleanups branch...
> > >
> > > > Use the value of these variables as the argument to of_fwnode_handle()
> > > > directly, clearing up the warnings.
> > > >
> > > > Fixes: e3d44f11da04 ("mfd: Switch to irq_domain_create_*()")
> > >
> > > but this hash has changed, so this should be
> > >
> > > Fixes: a36aa0f7226a ("mfd: Switch to irq_domain_create_*()")
> > >
> > > but the rest of the change is still applicable. Would you like a new
> > > change or can you adjust that when applying?
> >
> > Okay, please rebase and resubmit.
> >
> > I suspect at least one of these has been fixed by Arnd already.
>
> All of these are addressed by commit fc5f017a71d0 ("mfd: Fix building
> without CONFIG_OF") in your tree. Is that going to be merged into 6.16?
Yes, I can make that happen.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-06-19 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 15:57 [PATCH] mfd: Remove node variables that are unused with CONFIG_OF=n Nathan Chancellor
2025-05-12 8:50 ` Jiri Slaby
2025-05-13 9:47 ` Lee Jones
2025-05-13 10:45 ` Nathan Chancellor
2025-05-13 11:09 ` Lee Jones
2025-05-28 16:06 ` Nathan Chancellor
2025-06-13 13:39 ` Lee Jones
2025-06-13 16:06 ` Nathan Chancellor
2025-06-19 10:06 ` Lee Jones [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=20250619100627.GD587864@google.com \
--to=lee@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=rogerq@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).