linux-um archives
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: linux-um@lists.infradead.org,
	Taras Chornyi <tchornyi@marvell.com>,
	 netdev@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.1-rc7
Date: Mon, 28 Nov 2022 14:52:03 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2211281451020.453065@ramsan.of.borg> (raw)
In-Reply-To: <20221128134525.3580246-1-geert@linux-m68k.org>

On Mon, 28 Nov 2022, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.1-rc7[1] to v6.1-rc6[3], the summaries are:
>  - build errors: +6/-0

   + /kisskb/src/arch/um/include/asm/processor-generic.h: error: called object is not a function or function pointer: 94:18 => 94:19, 94:18

um-x86_64-gcc12/um-all{mod,yes}config (in kfd_cpumask_to_apic_id(), seen
before with um-x86_64/um-all{mod,yes}config)

   + /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: 'struct cpuinfo_um' has no member named 'x86_cache_size':  => 88:22
   + /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: control reaches end of non-void function [-Werror=return-type]:  => 89:1
   + /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: implicit declaration of function '__copy_user_nocache' [-Werror=implicit-function-declaration]:  => 100:2

um-x86_64/um-all{mod,yes}config (seen before on v6.1-rc4)

   + /kisskb/src/drivers/net/ethernet/marvell/prestera/prestera_flower.c: error: 'rule' is used uninitialized [-Werror=uninitialized]:  => 480:34
   + /kisskb/src/drivers/spi/spi-stm32-qspi.c: error: 'op' is used uninitialized [-Werror=uninitialized]:  => 523:27, 564:27

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

The latter looks completely bogus to me, unless there's a bug in the UML
implementation of memcpy() and memset(), which are used to initialize
"op".

> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/b7b275e60bcd5f89771e865a8239325f86d9927d/ (all 152 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/eb7081409f94a9a8608593d0fb63a1aa3d6f95d8/ (149 out of 152 configs)

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

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

           reply	other threads:[~2022-11-28 13:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20221128134525.3580246-1-geert@linux-m68k.org>]

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=alpine.DEB.2.22.394.2211281451020.453065@ramsan.of.borg \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=tchornyi@marvell.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