From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.19-rc3
Date: Wed, 7 Jan 2015 14:24:54 +0530 [thread overview]
Message-ID: <54ACF45E.4020100@synopsys.com> (raw)
In-Reply-To: <1420536979-31149-1-git-send-email-geert@linux-m68k.org>
Hi Geert,
On Tuesday 06 January 2015 03:06 PM, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.19-rc3[1] compared to v3.18[2].
>
> Summarized:
> - build errors: +86/-19
> - build warnings: +242/-127
>
> JFYI, when comparing v3.19-rc3[1] to v3.19-rc2[3], the summaries are:
> - build errors: +64/-9
> - build warnings: +123/-75
>
> Note that there may be false regressions, as some logs are incomplete.
> Still, they're build errors/warnings.
>
> As I haven't mastered kup yet, there's no verbose summary at
> http://www.kernel.org/pub/linux/kernel/people/geert/linux-log/v3.19-rc3.summary.gz
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/head/8277/ (255 out of 262 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/head/8168/ (all 262 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/head/8257/ (all 262 configs)
How can I get the ARC tools / config added to test setup.
AFAIKR linux-next already has ARC setup as I got a build failure report from them
once [1]
[1] https://lkml.org/lkml/2014/9/25/767
Thx,
-Vineet
next prev parent reply other threads:[~2015-01-07 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 9:36 Build regressions/improvements in v3.19-rc3 Geert Uytterhoeven
2015-01-06 9:39 ` Geert Uytterhoeven
2015-01-06 16:00 ` Mathieu Poirier
2015-01-06 19:12 ` Peter Hurley
2015-01-06 19:37 ` Geert Uytterhoeven
2015-01-07 8:54 ` Vineet Gupta [this message]
2015-01-07 9:00 ` 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=54ACF45E.4020100@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--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