From: Calvin Owens <calvin@wbinvd.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-bluetooth@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
pmenzel@molgen.mpg.de,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: next-20250901 drivers bluetooth bpa10x.c:77:33: error: array type has incomplete element type 'struct h4_recv_pkt'
Date: Tue, 2 Sep 2025 07:56:58 -0700 [thread overview]
Message-ID: <aLcFuqRuB2NFu-ZE@mozart.vkv.me> (raw)
In-Reply-To: <CA+G9fYsgiqTo7t3e36P5cysc+jEX5Fub1quTj+fuKGM8jkxbFA@mail.gmail.com>
On Tuesday 09/02 at 15:00 +0530, Naresh Kamboju wrote:
> The following build warnings / errors are noticed on powerpc ppc6xx_defconfig
> with gcc-13 toolchain running on Linux next-20250901 and next-20250902.
>
> Regression Analysis:
> - New regression? yes
> - Reproducibility? yes
>
> First seen on next-20250901
> Bad: next-20250901 and next-20250902
> Good: next-20250829
>
> Build regression: next-20250901 drivers bluetooth bpa10x.c:77:33:
> error: array type has incomplete element type 'struct h4_recv_pkt'
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Powerpc:
> build:
> * gcc-13-ppc6xx_defconfig
> * gcc-8-ppc6xx_defconfig
Hi Naresh,
This should fix it:
https://lore.kernel.org/all/aLNRvzXE4O9dKZoN@mozart.vkv.me/
Thanks,
Calvin
> Build error:
> drivers/bluetooth/bpa10x.c:77:33: error: array type has incomplete
> element type 'struct h4_recv_pkt'
> 77 | static const struct h4_recv_pkt bpa10x_recv_pkts[] = {
> | ^~~~~~~~~~~~~~~~
> drivers/bluetooth/bpa10x.c:78:11: error: 'H4_RECV_ACL' undeclared here
> (not in a function)
> 78 | { H4_RECV_ACL, .recv = hci_recv_frame },
> | ^~~~~~~~~~~
> drivers/bluetooth/bpa10x.c:79:11: error: 'H4_RECV_SCO' undeclared here
> (not in a function)
> 79 | { H4_RECV_SCO, .recv = hci_recv_frame },
> | ^~~~~~~~~~~
> drivers/bluetooth/bpa10x.c:80:11: error: 'H4_RECV_EVENT' undeclared
> here (not in a function)
> 80 | { H4_RECV_EVENT, .recv = hci_recv_frame },
> | ^~~~~~~~~~~~~
> drivers/bluetooth/bpa10x.c: In function 'bpa10x_rx_complete':
> drivers/bluetooth/bpa10x.c:99:37: error: implicit declaration of
> function 'h4_recv_buf' [-Werror=implicit-function-declaration]
> 99 | data->rx_skb[idx] = h4_recv_buf(hdev, data->rx_skb[idx],
> | ^~~~~~~~~~~
> In file included from include/linux/array_size.h:5,
> from include/linux/kernel.h:16,
> from drivers/bluetooth/bpa10x.c:9:
> include/linux/compiler.h:197:82: error: expression in static assertion
> is not an integer
> 197 | #define __BUILD_BUG_ON_ZERO_MSG(e, msg, ...)
> ((int)sizeof(struct {_Static_assert(!(e), msg);}))
> |
> ^
> include/linux/compiler.h:202:33: note: in expansion of macro
> '__BUILD_BUG_ON_ZERO_MSG'
> 202 | #define __must_be_array(a)
> __BUILD_BUG_ON_ZERO_MSG(!__is_array(a), \
> | ^~~~~~~~~~~~~~~~~~~~~~~
> include/linux/array_size.h:11:59: note: in expansion of macro '__must_be_array'
> 11 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) +
> __must_be_array(arr))
> |
> ^~~~~~~~~~~~~~~
> drivers/bluetooth/bpa10x.c:103:49: note: in expansion of macro 'ARRAY_SIZE'
> 103 |
> ARRAY_SIZE(bpa10x_recv_pkts));
> | ^~~~~~~~~~
> drivers/bluetooth/bpa10x.c: At top level:
> drivers/bluetooth/bpa10x.c:77:33: warning: 'bpa10x_recv_pkts' defined
> but not used [-Wunused-variable]
> 77 | static const struct h4_recv_pkt bpa10x_recv_pkts[] = {
> | ^~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
>
>
> ## Source
> * Kernel version: 6.17.0-rc4
> * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
> * Git describe: next-20250902
> * Git commit: 3db46a82d467bd23d9ebc473d872a865785299d8
> * Architectures: powerpc
> * Toolchains: gcc-13
> * Kconfigs: ppc6xx_defconfig
>
> ## Build
> * Build log: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20250902/testrun/29725581/suite/build/test/gcc-13-ppc6xx_defconfig/log
> * Build details:
> https://regressions.linaro.org/lkft/linux-next-master/next-20250901/log-parser-build-gcc/gcc-compiler-drivers_bluetooth_bpax_c-error-array-type-has-incomplete-element-type-struct-h_recv_pkt/
> * Build plan: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/builds/328DwMMwNOpSAj0qnRpJavgtz9C
> * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/328DwMMwNOpSAj0qnRpJavgtz9C/
> * Kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/328DwMMwNOpSAj0qnRpJavgtz9C/config
>
> --
> Linaro LKFT
> https://lkft.linaro.org
prev parent reply other threads:[~2025-09-02 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 9:30 Naresh Kamboju
2025-09-02 14:56 ` Calvin Owens [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=aLcFuqRuB2NFu-ZE@mozart.vkv.me \
--to=calvin@wbinvd.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkft-triage@lists.linaro.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=naresh.kamboju@linaro.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
/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
all inboxes | Powered by JetHome®