From: Arnd Bergmann <arnd@arndb.de>
To: kbuild test robot <fengguang.wu@intel.com>
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: Tue, 19 Jan 2016 15:26:16 +0100 [thread overview]
Message-ID: <1534543.eobSKFEFfp@wuerfel> (raw)
In-Reply-To: <569e1dbb.MgLv8OaZwklOxxtU%fengguang.wu@intel.com>
On Tuesday 19 January 2016 19:27:55 kbuild test robot wrote:
> arm allnoconfig
> arm at91_dt_defconfig
> arm at_hdmac
> arm ep93xx
> arm imx_v6_v7_defconfig
> arm iop-adma
> arm marzen_defconfig
> arm prima2_defconfig
> arm sa1100
> arm samsung
> arm sh
> arm spear13xx_defconfig
>
Hi Fengguang,
Sorry for hijacking this thread. I have never seen the list of arm defconfigs
you are building before, and it seems to be a surprising selection, as a number
of platforms (ep93xx, iop, sa1100, spear13xx) are rather obscure, but the
configurations that I tend to use most (multi_v7_defconfig, multi_v5_defconfig,
allmodconfig) are not included.
Do you always build the same set of configurations, or is this a different
each time?
Can you always include the three I mentioned?
Arnd
next prev parent reply other threads:[~2016-01-19 14:26 UTC|newest]
Thread overview: 35+ 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 11:27 ` kbuild test robot
2016-01-19 14:26 ` Arnd Bergmann [this message]
2016-01-26 5:30 ` Fengguang Wu
2016-01-26 5:35 ` Fengguang Wu
2016-01-26 16:27 ` Arnd Bergmann
2016-01-27 8:37 ` Fengguang Wu
2016-01-27 9:11 ` Arnd Bergmann
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 3:14 ` Fengguang Wu
2016-01-28 12:07 ` Arnd Bergmann
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-28 23:07 ` Arnd Bergmann
2016-01-29 8:01 ` Geert Uytterhoeven
2016-01-29 8:01 ` Geert Uytterhoeven
2016-01-29 20:44 ` Arnd Bergmann
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:24 ` Geert Uytterhoeven
2016-01-29 21:54 ` Arnd Bergmann
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-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=1534543.eobSKFEFfp@wuerfel \
--to=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=fengguang.wu@intel.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 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.