linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Marco Elver <elver@google.com>,
	Steen Hegelund <Steen.Hegelund@microchip.com>,
	linux-um <linux-um@lists.infradead.org>,
	scsi <linux-scsi@vger.kernel.org>,
	kasan-dev <kasan-dev@googlegroups.com>,
	netdev <netdev@vger.kernel.org>
Subject: Re: Build regressions/improvements in v5.14-rc1
Date: Wed, 14 Jul 2021 16:44:05 +0200	[thread overview]
Message-ID: <CAMuHMdWv8-6fBDLb8cFvvLxsb7RkEVkLNUBeCm-9yN9_iJkg-g@mail.gmail.com> (raw)
In-Reply-To: <20210714143239.2529044-1-geert@linux-m68k.org>

On Wed, Jul 14, 2021 at 4:35 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Below is the list of build error/warning regressions/improvements in
> v5.14-rc1[1] compared to v5.13+[2].
>
> Summarized:
>   - build errors: +24/-4
>   - build warnings: +71/-65
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/e73f0f0ee7541171d89f2e2491130c7771ba58d3/ (all 189 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/66d9282523b3228183b14d9f812872dd2620704d/ (all 189 configs)
>
>
> *** ERRORS ***
>
> 24 error regressions:

  + /kisskb/src/drivers/dma/idxd/init.c: error: implicit declaration
of function 'cpu_feature_enabled'
[-Werror=implicit-function-declaration]:  => 805:7
  + /kisskb/src/drivers/dma/idxd/perfmon.h: error: 'struct perf_event'
has no member named 'pmu':  => 24:13, 35:13
  + /kisskb/src/drivers/dma/ioat/dca.c: error: implicit declaration of
function 'boot_cpu_has' [-Werror=implicit-function-declaration]:  =>
74:6
  + /kisskb/src/drivers/dma/ioat/dca.c: error: implicit declaration of
function 'cpuid_eax' [-Werror=implicit-function-declaration]:  =>
64:18
  + /kisskb/src/drivers/dma/ioat/dca.c: error: implicit declaration of
function 'cpuid_ebx' [-Werror=implicit-function-declaration]:  =>
17:31
  + /kisskb/src/drivers/pci/controller/vmd.c: error:
'X86_MSI_BASE_ADDRESS_HIGH' undeclared (first use in this function):
=> 150:20
  + /kisskb/src/drivers/pci/controller/vmd.c: error:
'X86_MSI_BASE_ADDRESS_LOW' undeclared (first use in this function):
=> 151:35
  + /kisskb/src/drivers/pci/controller/vmd.c: error:
'arch_msi_msg_addr_lo_t {aka struct arch_msi_msg_addr_lo}' has no
member named 'base_address':  => 151:19
  + /kisskb/src/drivers/pci/controller/vmd.c: error:
'arch_msi_msg_addr_lo_t {aka struct arch_msi_msg_addr_lo}' has no
member named 'destid_0_7':  => 152:19
  + /kisskb/src/drivers/pci/controller/vmd.c: error: control reaches
end of non-void function [-Werror=return-type]:  => 127:1
  + /kisskb/src/drivers/pci/controller/vmd.c: error: dereferencing
pointer to incomplete type 'struct pci_sysdata':  => 700:4
  + /kisskb/src/drivers/pci/controller/vmd.c: error: field 'sysdata'
has incomplete type:  => 116:21

um-x86_64/um-all{mod,yes}config

  + /kisskb/src/drivers/scsi/arm/fas216.c: error: 'GOOD' undeclared
(first use in this function):  => 2013:47

arm-gcc4.9/rpc_defconfig

  + /kisskb/src/drivers/tty/synclink_gt.c: error: conflicting types
for 'set_signals':  => 442:13

um-x86_64/um-allmodconfig

  + /kisskb/src/include/linux/compiler_attributes.h: error:
"__GCC4_has_attribute___no_sanitize_coverage__" is not defined
[-Werror=undef]:  => 29:29

mips-gcc4.9/mips-allmodconfig
s390x-gcc4.9/s390-allyesconfig

  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_1857' declared with attribute error: FIELD_PREP:
value too large for the field:  => 328:38
  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_1864' declared with attribute error: FIELD_PREP:
value too large for the field:  => 328:38

arm64-gcc5.4/arm64-allmodconfig
arm64-gcc8/arm64-allmodconfig

  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_399' declared with attribute error: Unsupported
width, must be <= 40:  => 328:38
  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_417' declared with attribute error: Unsupported
width, must be <= 40:  => 328:38
  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_418' declared with attribute error: Unsupported
width, must be <= 40:  => 328:38
  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_431' declared with attribute error: Unsupported
width, must be <= 40:  => 328:38
  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_433' declared with attribute error: Unsupported
width, must be <= 40:  => 328:38
  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_450' declared with attribute error: Unsupported
width, must be <= 40:  => 328:38
  + /kisskb/src/include/linux/compiler_types.h: error: call to
'__compiletime_assert_517' declared with attribute error: Unsupported
width, must be <= 40:  => 328:38

arm64-gcc5.4/arm64-allmodconfig
mipsel/mips-allmodconfig
mips-gcc4.9/mips-allmodconfig
powerpc-gcc4.9/allmodconfig+64K_PAGES
powerpc-gcc4.9/powerpc-allmodconfig
powerpc-gcc4.9/powerpc-allyesconfig
powerpc-gcc4.9/ppc64_book3e_allmodconfig
s390x-gcc4.9/s390-allyesconfig
sparc64/sparc64-allmodconfig
sparc64/sparc-allmodconfig
xtensa/xtensa-allmodconfig

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-07-14 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 14:32 Build regressions/improvements in v5.14-rc1 Geert Uytterhoeven
2021-07-14 14:44 ` Geert Uytterhoeven [this message]
2021-07-14 15:06   ` Marco Elver
2021-07-14 15:58   ` Randy Dunlap
2021-07-18 12:20 ` Pavel Machek

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=CAMuHMdWv8-6fBDLb8cFvvLxsb7RkEVkLNUBeCm-9yN9_iJkg-g@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=Steen.Hegelund@microchip.com \
    --cc=elver@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    /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).