From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE
Date: Wed, 27 Jan 2016 10:44:01 +0100 [thread overview]
Message-ID: <3596300.IYfzmako0c@wuerfel> (raw)
In-Reply-To: <20160127093018.GA21190@wfg-t540p.sh.intel.com>
On Wednesday 27 January 2016 17:30:18 Fengguang Wu wrote:
> > Looks good, I'm just unsure about "multi_v8_defconfig", this does not
> > exist. Do you mean multi_v5_defconfig?
> Ah yes, multi_v8_defconfig does not exist actually.
Ok, can you include multi_v5_defconfig than?
I see you have one named "arm-arm5", which may be the same.
> > I also wonder if you include 'randconfig' builds for some architectures.
> > I have patches for all remaining errors and warnings that I see with
> > ARM randconfig builds today. Not all of them are merged yet, but I could
> > probably come up with a file to be used as input to KCONFIG_ALLCONFIG
> > to eliminate the known-broken configurations, if you are interested.
>
> If the are mostly ready for upstream, it may be easier to wait until
> upstream randconfig works just fine for ARM.
I have around 130 patches for warnings that I'm submitting at the moment, but
there are a couple of really tricky ones that I don't currently have
a good plan for:
- in some configurations, you end up without any boards selected, hitting
an #error in the final link
- ARMv3 support in gcc is rather broken and causes internal compiler errors
among other things
- the old ELF format (OABI) doesn't work in some cases
- GCOV_PROFILE_ALL causes problems that need to be debugged
- XIP_KERNEL sometimes causes kallsyms to fail
- not all platforms implement the complete clk API, if they don't
use CONFIG_COMMON_CLK (I have patch for that we can probably merge)
- CONFIG_PHYS_OFFSET needs to be entered manually to be a number
in 'make config'
- same for DEBUG_LL
Arnd
next parent reply other threads:[~2016-01-27 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <569e1dbb.MgLv8OaZwklOxxtU%fengguang.wu@intel.com>
[not found] ` <1947556.38OyJnvGS5@wuerfel>
[not found] ` <20160127093018.GA21190@wfg-t540p.sh.intel.com>
2016-01-27 9:44 ` Arnd Bergmann [this message]
2016-01-28 3:14 ` [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Fengguang Wu
2016-01-28 12:07 ` Arnd Bergmann
2016-01-28 17:42 ` Russell King - ARM Linux
2016-01-28 23:07 ` Arnd Bergmann
2016-01-29 8:01 ` Geert Uytterhoeven
2016-01-29 20:44 ` Arnd Bergmann
2016-01-29 21:24 ` Geert Uytterhoeven
2016-01-29 21:54 ` Arnd Bergmann
2016-01-29 23:15 ` Russell King - ARM Linux
2016-01-29 21:46 ` Russell King - ARM Linux
2016-01-28 18: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=3596300.IYfzmako0c@wuerfel \
--to=arnd@arndb.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox