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.3-rc4
Date: Mon, 12 Aug 2019 13:33:53 -0700 [thread overview]
Message-ID: <a74dd048-8501-a973-5b03-eefbc83d7f79@infradead.org> (raw)
In-Reply-To: <20190812102049.27836-1-geert@linux-m68k.org>
On 8/12/19 3:20 AM, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v5.3-rc4[1] compared to v5.2[2].
>
> Summarized:
> - build errors: +5/-1
> - build warnings: +137/-136
>
> JFYI, when comparing v5.3-rc4[1] to v5.3-rc3[3], the summaries are:
> - build errors: +0/-4
> - build warnings: +105/-69
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/d45331b00ddb179e291766617259261c112db872/ (all 242 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/0ecfebd2b52404ae0c54a878c872bb93363ada36/ (all 242 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/e21a712a9685488f5ce80495b37b9fdbe96c230d/ (all 242 configs)
> *** WARNINGS ***
>
> 137 warning regressions:
> + warning: unmet direct dependencies detected for MTD_COMPLEX_MAPPINGS: => N/A
It would be Really Good if there was some automated way to know which
of the 242 configs this is from (instead of you having to grep and reply to
email or someone/me having to download up to 242 log files).
--
~Randy
next prev parent reply other threads:[~2019-08-12 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 10:20 Build regressions/improvements in v5.3-rc4 Geert Uytterhoeven
2019-08-12 20:33 ` Randy Dunlap [this message]
2019-08-12 21:09 ` Geert Uytterhoeven
2019-08-13 23:07 ` Randy Dunlap
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=a74dd048-8501-a973-5b03-eefbc83d7f79@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 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).