All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v5.4-rc2
Date: Mon, 7 Oct 2019 13:48:08 -0700	[thread overview]
Message-ID: <f0250c51-a653-6cac-9e6b-affa74d8559c@infradead.org> (raw)
In-Reply-To: <20191007071829.13325-1-geert@linux-m68k.org>

On 10/7/19 12:18 AM, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v5.4-rc2[1] compared to v5.3[2].
> 
> Summarized:
>   - build errors: +10/-3
>   - build warnings: +152/-143
> 
> JFYI, when comparing v5.4-rc2[1] to v5.4-rc1[3], the summaries are:
>   - build errors: +5/-10
>   - build warnings: +44/-133
> 
> Note that there may be false regressions, as some logs are incomplete.
> Still, they're build errors/warnings.
> 
> Happy fixing! ;-)
> 
> Thanks to the linux-next team for providing the build service.
> 
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/da0c9ea146cbe92b832f1b0f694840ea8eb33cce/ (233 out of 242 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/4d856f72c10ecb060868ed10ff1b1453943fc6c8/ (all 242 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c/ (233 out of 242 configs)
> 
> 
> *** ERRORS ***
> 
> 10 error regressions:

>   + error: "__delay" [drivers/net/phy/mdio-cavium.ko] undefined!:  => N/A

Hi Geert,

What arch & config is the above build error from?

Sorry to bug you about this.

Thanks.
-- 
~Randy

  parent reply	other threads:[~2019-10-07 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  7:18 Build regressions/improvements in v5.4-rc2 Geert Uytterhoeven
2019-10-07  7:33 ` Geert Uytterhoeven
2019-10-07 20:48 ` Randy Dunlap [this message]
2019-10-07 21:04   ` Geert Uytterhoeven
2019-10-07 23:41     ` Randy Dunlap
2019-10-08  7:28       ` Geert Uytterhoeven

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=f0250c51-a653-6cac-9e6b-affa74d8559c@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.