Linux-sh Archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: linux-sh@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.9-rc3
Date: Mon, 8 Apr 2024 10:54:00 +0200 (CEST)	[thread overview]
Message-ID: <2d5f2edd-217-d2e-925b-7d9b186072d3@linux-m68k.org> (raw)
In-Reply-To: <20240408075342.2495918-1-geert@linux-m68k.org>

On Mon, 8 Apr 2024, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.9-rc3[1] to v6.9-rc2[3], the summaries are:
>  - build errors: +4/-1

   + /kisskb/src/arch/sh/mm/nommu.c: error: no previous prototype for 'kmap_coherent' [-Werror=missing-prototypes]:  => 80:7
   + /kisskb/src/arch/sh/mm/nommu.c: error: no previous prototype for 'kmap_coherent_init' [-Werror=missing-prototypes]:  => 76:13
   + /kisskb/src/arch/sh/mm/nommu.c: error: no previous prototype for 'kunmap_coherent' [-Werror=missing-prototypes]:  => 86:6
   + {standard input}: Error: invalid operands for opcode: 1099 => 610, 1099

sh4-gcc13/sh-allyesconfig (seen before)

> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/fec50db7033ea478773b159e0e2efb135270e3b7/ (all 138 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/39cd87c4eb2b893354f3b850f916353f2658ae6f/ (all 138 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

           reply	other threads:[~2024-04-08  8:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240408075342.2495918-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=2d5f2edd-217-d2e-925b-7d9b186072d3@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@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 read-only IMAP folder(s) and NNTP newsgroup(s).