From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Pierluigi Passaro <pierluigi.p@variscite.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the gpio-brgl-fixes tree
Date: Tue, 24 Jan 2023 07:56:00 +1100 [thread overview]
Message-ID: <20230124075600.649bd7bb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
Hi all,
After merging the gpio-brgl-fixes tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from include/linux/of_gpio.h:14,
from drivers/net/phy/mdio_bus.c:27:
include/linux/gpio/driver.h:782:68: error: parameter 4 ('lflags') has incomplete type
782 | enum gpio_lookup_flags lflags,
| ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
include/linux/gpio/driver.h:779:33: error: function declaration isn't a prototype [-Werror=strict-prototypes]
779 | static inline struct gpio_desc *gpiochip_request_own_desc(struct gpio_chip *gc,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
Caused by commit
de5f701724ac ("gpiolib: fix linker errors when GPIOLIB is disabled")
I have used the gpio-brgl-fixes tree from next-20210123 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-01-23 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 20:56 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-24 0:51 linux-next: build failure after merge of the gpio-brgl-fixes tree Pierluigi Passaro
2023-01-24 1:25 ` Stephen Rothwell
2024-04-22 23:33 Stephen Rothwell
2024-04-23 7:53 ` Bartosz Golaszewski
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=20230124075600.649bd7bb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierluigi.p@variscite.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