From: Fengguang Wu <fengguang.wu@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: James Hogan <james.hogan@imgtec.com>,
linux-mips@linux-mips.org, linux-arch@vger.kernel.org,
linux-kbuild@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Paul Burton <paul.burton@imgtec.com>,
Ralf Baechle <ralf@linux-mips.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
linux-kernel@vger.kernel.org, Michal Marek <mmarek@suse.com>
Subject: Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE
Date: Wed, 27 Jan 2016 17:30:18 +0800 [thread overview]
Message-ID: <20160127093018.GA21190@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <1947556.38OyJnvGS5@wuerfel>
On Wed, Jan 27, 2016 at 10:11:47AM +0100, Arnd Bergmann wrote:
> On Wednesday 27 January 2016 16:37:45 Fengguang Wu wrote:
> >
> > Thank you for the tips! I've updated the lists accordingly.
> >
> > 1st priority
> > ============
> >
> > arm-allmodconfig
> > arm-allnoconfig
> > arm-at91_dt_defconfig
> > arm-efm32_defconfig
> > arm-exynos_defconfig
> > arm-multi_v7_defconfig
> > arm-multi_v8_defconfig
> > arm-shmobile_defconfig
> > arm-sunxi_defconfig
> >
> > 2nd priority
> > ============
> >
> > arm-arm5
> > arm-arm67
> > arm-imx_v6_v7_defconfig
> > arm-ixp4xx_defconfig
> > arm-mvebu_v7_defconfig
> > arm-omap2plus_defconfig
> > arm-sa1100
> > arm-samsung
> > arm-sh
> > arm-tegra_defconfig
> >
> > 3nd priority
> > ============
> >
> > arch/*/configs/*
>
> 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.
> 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.
Thanks,
Fengguang
next prev parent reply other threads:[~2016-01-27 9:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:27 [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE kbuild test robot
2016-01-19 11:27 ` kbuild test robot
2016-01-19 14:26 ` Arnd Bergmann
2016-01-26 5:30 ` Fengguang Wu
2016-01-26 5:30 ` Fengguang Wu
2016-01-26 5:35 ` Fengguang Wu
2016-01-26 5:35 ` Fengguang Wu
2016-01-26 16:27 ` Arnd Bergmann
2016-01-26 16:27 ` Arnd Bergmann
2016-01-27 8:37 ` Fengguang Wu
2016-01-27 8:37 ` Fengguang Wu
2016-01-27 9:11 ` Arnd Bergmann
2016-01-27 9:11 ` Arnd Bergmann
2016-01-27 9:30 ` Fengguang Wu [this message]
2016-01-27 9:30 ` Fengguang Wu
2016-01-27 9:44 ` Arnd Bergmann
2016-01-27 9:44 ` Arnd Bergmann
2016-01-28 3:14 ` Fengguang Wu
2016-01-28 12:07 ` Arnd Bergmann
2016-01-28 17:42 ` Russell King - ARM Linux
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:24 ` Geert Uytterhoeven
2016-01-29 21:54 ` Arnd Bergmann
2016-01-29 23:15 ` Russell King - ARM Linux
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
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=20160127093018.GA21190@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mmarek@suse.com \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=xypron.glpk@gmx.de \
/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).