From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
netdev@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 25 (drivers/net/dsa/b53/b53_common.c)
Date: Fri, 25 Jul 2025 14:04:08 -0700 [thread overview]
Message-ID: <679b2dc9-337f-4b48-8830-add309e2d3e5@infradead.org> (raw)
In-Reply-To: <20250725124835.53f998d0@canb.auug.org.au>
On 7/24/25 7:48 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20250724:
>
on ARCH=um SUBARCH=x86_64, when
# CONFIG_GPIOLIB is not set
../drivers/net/dsa/b53/b53_common.c: In function ‘b53_switch_reset_gpio’:
../drivers/net/dsa/b53/b53_common.c:952:9: error: implicit declaration of function ‘gpio_set_value’; did you mean ‘pte_set_val’? [-Wimplicit-function-declaration]
952 | gpio_set_value(gpio, 0);
| ^~~~~~~~~~~~~~
| pte_set_val
../drivers/net/dsa/b53/b53_common.c: In function ‘b53_switch_init’:
../drivers/net/dsa/b53/b53_common.c:3012:23: error: implicit declaration of function ‘devm_gpio_request_one’ [-Wimplicit-function-declaration]
3012 | ret = devm_gpio_request_one(dev->dev, dev->reset_gpio,
| ^~~~~~~~~~~~~~~~~~~~~
../drivers/net/dsa/b53/b53_common.c:3013:45: error: ‘GPIOF_OUT_INIT_HIGH’ undeclared (first use in this function)
3013 | GPIOF_OUT_INIT_HIGH, "robo_reset");
| ^~~~~~~~~~~~~~~~~~~
../drivers/net/dsa/b53/b53_common.c:3013:45: note: each undeclared identifier is reported only once for each function it appears in
Probably just needs "depends on GPIOLIB" or "select GPIOLIB"...
--
~Randy
next parent reply other threads:[~2025-07-25 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250725124835.53f998d0@canb.auug.org.au>
2025-07-25 21:04 ` Randy Dunlap [this message]
2025-07-25 21:12 ` linux-next: Tree for Jul 25 (nfc/nfrmrvl/ and nfc/s3fwrn5/) Randy Dunlap
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=679b2dc9-337f-4b48-8830-add309e2d3e5@infradead.org \
--to=rdunlap@infradead.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).