From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the kspp-gustavo tree
Date: Mon, 17 Aug 2020 19:06:34 -0500 [thread overview]
Message-ID: <fc2ebeb2-52e1-b5a7-493a-e8529440f614@embeddedor.com> (raw)
In-Reply-To: <20200818093805.11c0c3c3@canb.auug.org.au>
Hi Stephen,
On 8/17/20 18:38, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kspp-gustavo tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> arch/powerpc/boot/inflate.c: In function 'zlib_inflate':
> arch/powerpc/boot/inflate.c:399:3: error: 'fallthrough' undeclared (first use in this function)
> 399 | fallthrough;
> | ^~~~~~~~~~~
> arch/powerpc/boot/inflate.c:399:3: note: each undeclared identifier is reported only once for each function it appears in
> In file included from ./arch/powerpc/boot/decompress_inflate.c:12,
> from /home/sfr/next/next/arch/powerpc/boot/decompress.c:33:
> ./arch/powerpc/boot/inflate.c: In function 'zlib_inflate':
> ./arch/powerpc/boot/inflate.c:399:3: error: 'fallthrough' undeclared (first use in this function)
> 399 | fallthrough;
> | ^~~~~~~~~~~
> ./arch/powerpc/boot/inflate.c:399:3: note: each undeclared identifier is reported only once for each function it appears in
>
> Caused by commit
>
> 02b894b985cb ("treewide: Use fallthrough pseudo-keyword")
>
> I have used the kspp-gustavo tree from next-20200817 for today.
>
Sorry for the inconvenience. This is a huge treewide patch and I
overlooked some erroneous conversions. I'll fix this up for
tomorrow's linux-next.
Thanks
--
Gustavo
next prev parent reply other threads:[~2020-08-18 0:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 23:38 linux-next: build failure after merge of the kspp-gustavo tree Stephen Rothwell
2020-08-18 0:06 ` Gustavo A. R. Silva [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 2:19 Stephen Rothwell
2023-11-21 16:31 ` Gustavo A. R. Silva
2023-11-21 23:15 ` Stephen Rothwell
2023-11-17 0:33 Stephen Rothwell
2023-11-17 0:39 ` Gustavo A. R. Silva
2021-10-18 8:30 Stephen Rothwell
2021-10-20 16:18 ` Gustavo A. R. Silva
2021-10-20 16:20 ` Kees Cook
2021-10-25 1:55 ` Stephen Rothwell
2021-10-25 19:19 ` Kees Cook
2021-10-25 19:31 ` Gustavo A. R. Silva
2021-10-25 19:34 ` Kees Cook
2021-10-18 7:15 Stephen Rothwell
2021-10-18 17:13 ` Gustavo A. R. Silva
2021-10-25 1:54 ` Stephen Rothwell
2021-10-25 2:11 ` Gustavo A. R. Silva
2021-10-25 2:42 ` Steven Rostedt
2021-10-25 4:30 ` Stephen Rothwell
2021-10-25 11:35 ` Steven Rostedt
2021-10-14 23:48 Stephen Rothwell
2021-10-15 0:07 ` Gustavo A. R. Silva
2021-10-15 8:02 ` Stephen Rothwell
2021-09-29 23:59 Stephen Rothwell
2021-09-30 0:11 ` Gustavo A. R. Silva
2020-08-17 23:34 Stephen Rothwell
2020-08-17 23:46 ` Gustavo A. R. Silva
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=fc2ebeb2-52e1-b5a7-493a-e8529440f614@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.