From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: Build regressions/improvements in v4.3-rc7
Date: Sun, 25 Oct 2015 23:07:01 +0100 [thread overview]
Message-ID: <20151025220701.GA5635@debian> (raw)
In-Reply-To: <20151025190318.GA3320@afzalpc>
On Mon, Oct 26, 2015 at 12:33:18AM +0530, Afzal Mohammed wrote:
> On Sun, Oct 25, 2015 at 06:38:18PM +0100, Geert Uytterhoeven wrote:
> > I think we should have at least one arm-nommu platform in the upstream kernel,
> > with a suitable defconfig, so 0build will catch regressions.
>
> afaik, there are 4 arm-nommu defconfig's. Has been recently playing
> with Vybrid nommu platform, did not notice any build error w/ it's
> defconfig (vf610m4) and able to boot too. Just now tried -rc7, it too
> was success.
vf610m4 won't use patch.c since it has CONFIG_XIP_KERNEL=y. The failing
config is a randconfig[1], but the error can be triggered by, for
example, enabling CONFIG_JUMP_LABEL=y on lpc18xx_defconfig.
[1] http://kisskb.ellerman.id.au/kisskb/buildresult/12531538/
WARNING: multiple messages have this Message-ID (diff)
From: Rabin Vincent <rabin@rab.in>
To: Afzal Mohammed <afzal.mohd.ma@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Kees Cook <keescook@chromium.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.3-rc7
Date: Sun, 25 Oct 2015 23:07:01 +0100 [thread overview]
Message-ID: <20151025220701.GA5635@debian> (raw)
In-Reply-To: <20151025190318.GA3320@afzalpc>
On Mon, Oct 26, 2015 at 12:33:18AM +0530, Afzal Mohammed wrote:
> On Sun, Oct 25, 2015 at 06:38:18PM +0100, Geert Uytterhoeven wrote:
> > I think we should have at least one arm-nommu platform in the upstream kernel,
> > with a suitable defconfig, so 0build will catch regressions.
>
> afaik, there are 4 arm-nommu defconfig's. Has been recently playing
> with Vybrid nommu platform, did not notice any build error w/ it's
> defconfig (vf610m4) and able to boot too. Just now tried -rc7, it too
> was success.
vf610m4 won't use patch.c since it has CONFIG_XIP_KERNEL=y. The failing
config is a randconfig[1], but the error can be triggered by, for
example, enabling CONFIG_JUMP_LABEL=y on lpc18xx_defconfig.
[1] http://kisskb.ellerman.id.au/kisskb/buildresult/12531538/
next prev parent reply other threads:[~2015-10-25 22:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 10:12 Build regressions/improvements in v4.3-rc7 Geert Uytterhoeven
2015-10-25 10:18 ` Geert Uytterhoeven
2015-10-25 10:18 ` Geert Uytterhoeven
2015-10-25 10:39 ` Geert Uytterhoeven
2015-10-25 10:39 ` Geert Uytterhoeven
2015-10-25 14:08 ` Russell King - ARM Linux
2015-10-25 14:08 ` Russell King - ARM Linux
2015-10-25 17:38 ` Geert Uytterhoeven
2015-10-25 17:38 ` Geert Uytterhoeven
2015-10-25 18:23 ` Russell King - ARM Linux
2015-10-25 18:23 ` Russell King - ARM Linux
2015-10-25 19:03 ` Afzal Mohammed
2015-10-25 19:03 ` Afzal Mohammed
2015-10-25 22:07 ` Rabin Vincent [this message]
2015-10-25 22:07 ` Rabin Vincent
2015-10-25 22:32 ` Rabin Vincent
2015-10-25 22:32 ` Rabin Vincent
2015-10-26 7:56 ` Geert Uytterhoeven
2015-10-26 7:56 ` Geert Uytterhoeven
2015-10-25 17:34 ` Geert Uytterhoeven
2015-10-25 17:34 ` 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=20151025220701.GA5635@debian \
--to=rabin@rab.in \
--cc=linux-arm-kernel@lists.infradead.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.