From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Pierluigi Passaro <pierluigi.p@variscite•com>
Cc: Bartosz Golaszewski <brgl@bgdev•pl>,
Bartosz Golaszewski <bartosz.golaszewski@linaro•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the gpio-brgl-fixes tree
Date: Tue, 24 Jan 2023 12:25:41 +1100 [thread overview]
Message-ID: <20230124122541.0e310a1f@canb.auug.org.au> (raw)
In-Reply-To: <AM6PR08MB43769CCE04DA7C624CA3028AFFC99@AM6PR08MB4376.eurprd08.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2706 bytes --]
Hi Pierluigi,
On Tue, 24 Jan 2023 00:51:48 +0000 Pierluigi Passaro <pierluigi.p@variscite•com> wrote:
>
> On 1/23/23 21:56, Stephen Rothwell wrote:
> >
> > 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.
>
> please provide detailed build instructions.
> Building with
> - commit id de5f701724ac
> - defconfig arch/powerpc/configs/ppc64_defconfig
> - powerpc64-linux-gnu-gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
> The build fails almost immediately as follow
> arch/powerpc/kernel/trace/ftrace.c:839:7: error: no previous prototype for ‘arch_ftrace_match_adjust’ [-Werror=missing-prototypes]
> 839 | char *arch_ftrace_match_adjust(char *str, const char *search)
> | ^~~~~~~~~~~~~~~~~~~~~~~~
> However, the same happens rolling back de5f701724ac.
What I actually built to get the above error was what is now the
pending-fixes branch in
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git but
with the gpio-brgl-fixes tree
(git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git branch
gpio/for-current (commit de5f701724ac1) merged in.
but after removing that commit (and its parent), what I built was commit
83784b157e44 ("Merge branch 'riscv-soc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git")
(which is in the pending-fixes branch above) which did not fail.
gcc (Debian 12.2.0-10) 12.2.0
enum gpio_lookup_flags is defined in include/linux/gpio/machine.h which
is not directly included by include/linux/gpio/driver.h or
drivers/net/phy/mdio_bus.c.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-01-24 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-22 23:33 Stephen Rothwell
2024-04-23 7:53 ` Bartosz Golaszewski
2023-01-23 20:56 Stephen Rothwell
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=20230124122541.0e310a1f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bartosz.golaszewski@linaro$(echo .)org \
--cc=brgl@bgdev$(echo .)pl \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pierluigi.p@variscite$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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