linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.13-rc1
Date: Sun, 16 Jul 2017 18:28:19 +0000	[thread overview]
Message-ID: <CAMuHMdVe_kb4jBBXNpNUFk8ey4zo_w4y2NQ0xKeH4NXkUDN+UA@mail.gmail.com> (raw)
In-Reply-To: <1500229392-30817-1-git-send-email-geert@linux-m68k.org>

On Sun, Jul 16, 2017 at 8:23 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> Below is the list of build error/warning regressions/improvements in
> v4.13-rc1[1] compared to v4.12[2].
>
> Summarized:
>   - build errors: +2/-

> [1] http://kisskb.ellerman.id.au/kisskb/head/5771a8c08880cdca3bfb4a3fc6d309d6bba20877/ (all 267 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/head/6f7da290413ba713f0cdd9ff1a2a9bb129ef4f6c/ (all 267 configs)

> 2 error regressions:
>   + /home/kisskb/slave/src/arch/sh/mm/cache-sh4.c: error: 'cached_to_uncached' undeclared (first use in this function):  => 99:17
>   + /home/kisskb/slave/src/arch/sh/mm/cache-sh4.c: error: implicit declaration of function 'cpu_context' [-Werror=implicit-function-declaration]:  => 192:2

sh4-randconfig, nothing new, pops up once in a while.

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:[~2017-07-16 18:28 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1500229392-30817-1-git-send-email-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=CAMuHMdVe_kb4jBBXNpNUFk8ey4zo_w4y2NQ0xKeH4NXkUDN+UA@mail.gmail.com \
    --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 NNTP newsgroup(s).