Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1312134 > unrolled thread
| Started by | kbuild test robot <fengguang.wu@intel.com> |
|---|---|
| First post | 2016-01-19 12:30 +0100 |
| Last post | 2016-01-26 06:40 +0100 |
| Articles | 9 — 3 participants |
Back to article view | Back to linux.kernel
[linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE kbuild test robot <fengguang.wu@intel.com> - 2016-01-19 12:30 +0100
Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Arnd Bergmann <arnd@arndb.de> - 2016-01-19 15:30 +0100
Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Fengguang Wu <fengguang.wu@intel.com> - 2016-01-26 06:40 +0100
Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Arnd Bergmann <arnd@arndb.de> - 2016-01-26 17:30 +0100
Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Fengguang Wu <fengguang.wu@intel.com> - 2016-01-27 09:40 +0100
Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Arnd Bergmann <arnd@arndb.de> - 2016-01-27 10:20 +0100
Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Fengguang Wu <fengguang.wu@intel.com> - 2016-01-27 10:40 +0100
Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Arnd Bergmann <arnd@arndb.de> - 2016-01-27 10:50 +0100
Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Fengguang Wu <fengguang.wu@intel.com> - 2016-01-26 06:40 +0100
| From | kbuild test robot <fengguang.wu@intel.com> |
|---|---|
| Date | 2016-01-19 12:30 +0100 |
| Subject | [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE |
| Message-ID | <qSCE1-730-1@gated-at.bofh.it> |
https://github.com/0day-ci/linux James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642
d979f99e9cc14e2667e9b6e268db695977e4197a kbuild: Remove stale asm-generic wrappers
arch/x86/include/asm/unistd.h:15:29: fatal error: asm/unistd_32.h: No such file or directory
arch/x86/kernel/asm-offsets_32.c:12:29: fatal error: asm/syscalls_32.h: No such file or directory
arch/x86/kernel/asm-offsets_64.c:15:29: fatal error: asm/syscalls_64.h: No such file or directory
/bin/sh: line 0: [: -ge: unary operator expected
Error ids grouped by kconfigs:
recent_errors
├── i386-alldefconfig
│ └── arch-x86-include-asm-unistd.h:fatal-error:asm-unistd_32.h:No-such-file-or-directory
├── i386-allmodconfig
│ └── arch-x86-include-asm-unistd.h:fatal-error:asm-unistd_32.h:No-such-file-or-directory
├── i386-allyesconfig
│ └── arch-x86-include-asm-unistd.h:fatal-error:asm-unistd_32.h:No-such-file-or-directory
├── i386-defconfig
│ └── arch-x86-include-asm-unistd.h:fatal-error:asm-unistd_32.h:No-such-file-or-directory
├── i386-randconfig-a0-201603
│ └── arch-x86-kernel-asm-offsets_32.c:fatal-error:asm-syscalls_32.h:No-such-file-or-directory
├── i386-randconfig-b0-01191831
│ └── arch-x86-kernel-asm-offsets_32.c:fatal-error:asm-syscalls_32.h:No-such-file-or-directory
├── i386-randconfig-i0-201603
│ └── arch-x86-include-asm-unistd.h:fatal-error:asm-unistd_32.h:No-such-file-or-directory
├── i386-randconfig-i1-201603
│ └── arch-x86-include-asm-unistd.h:fatal-error:asm-unistd_32.h:No-such-file-or-directory
├── i386-randconfig-r0-201603
│ └── arch-x86-kernel-asm-offsets_32.c:fatal-error:asm-syscalls_32.h:No-such-file-or-directory
├── i386-randconfig-s1-201603
│ └── arch-x86-kernel-asm-offsets_32.c:fatal-error:asm-syscalls_32.h:No-such-file-or-directory
├── i386-randconfig-x002-01181631
│ └── bin-sh:line::ge:unary-operator-expected
├── i386-tinyconfig
│ └── arch-x86-kernel-asm-offsets_32.c:fatal-error:asm-syscalls_32.h:No-such-file-or-directory
└── x86_64-randconfig-s3-01191831
└── arch-x86-kernel-asm-offsets_64.c:fatal-error:asm-syscalls_64.h:No-such-file-or-directory
elapsed time: 50m
configs tested: 118
i386 randconfig-a0-201603
x86_64 acpi-redef
x86_64 allyesdebian
x86_64 nfsroot
blackfin BF526-EZBRD_defconfig
blackfin BF533-EZKIT_defconfig
blackfin BF561-EZKIT-SMP_defconfig
blackfin TCM-BF537_defconfig
cris etrax-100lx_v2_defconfig
sh allnoconfig
sh rsk7269_defconfig
sh sh7785lcr_32bit_defconfig
sh titan_defconfig
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
powerpc allnoconfig
powerpc defconfig
powerpc ppc64_defconfig
m32r m32104ut_defconfig
m32r mappi3.smp_defconfig
m32r opsput_defconfig
m32r usrv_defconfig
xtensa common_defconfig
xtensa iss_defconfig
alpha defconfig
parisc allnoconfig
parisc b180_defconfig
parisc c3000_defconfig
parisc defconfig
avr32 hammerhead_defconfig
m32r m32700ut.up_defconfig
mips bcm47xx_defconfig
mips capcella_defconfig
powerpc bluestone_defconfig
i386 alldefconfig
i386 allnoconfig
i386 defconfig
m68k m5475evb_defconfig
m68k multi_defconfig
m68k sun3_defconfig
i386 randconfig-s0-201603
i386 randconfig-s1-201603
x86_64 randconfig-s0-01191831
x86_64 randconfig-s1-01191831
x86_64 randconfig-s2-01191831
x86_64 allmodconfig
x86_64 randconfig-s3-01191831
x86_64 randconfig-s4-01191831
x86_64 randconfig-s5-01191831
avr32 atngw100_defconfig
avr32 atstk1006_defconfig
frv defconfig
mn10300 asb2364_defconfig
openrisc or1ksim_defconfig
tile tilegx_defconfig
um i386_defconfig
um x86_64_defconfig
m68k alldefconfig
mips db1xxx_defconfig
mips malta_qemu_32r6_defconfig
sh landisk_defconfig
mips allnoconfig
mips fuloong2e_defconfig
mips jz4740
mips txx9
x86_64 randconfig-i0-201603
i386 randconfig-b0-01191831
sparc defconfig
sparc64 allnoconfig
sparc64 defconfig
microblaze mmu_defconfig
microblaze nommu_defconfig
i386 randconfig-i0-201603
i386 randconfig-i1-201603
i386 allyesconfig
x86_64 randconfig-b0-01191744
i386 tinyconfig
i386 randconfig-n0-201603
ia64 alldefconfig
ia64 allnoconfig
ia64 defconfig
x86_64 rhel
ia64 tiger_defconfig
x86_64 randconfig-x000-201603
x86_64 randconfig-x001-201603
x86_64 randconfig-x002-201603
x86_64 randconfig-x003-201603
x86_64 randconfig-x004-201603
x86_64 randconfig-x005-201603
x86_64 randconfig-x006-201603
x86_64 randconfig-x007-201603
x86_64 randconfig-x008-201603
x86_64 randconfig-x009-201603
i386 randconfig-r0-201603
i386 allmodconfig
m68k sun3x_defconfig
mips mips_paravirt_defconfig
powerpc ppa8548_defconfig
i386 randconfig-x000-01181631
i386 randconfig-x001-01181631
i386 randconfig-x002-01181631
i386 randconfig-x003-01181631
i386 randconfig-x004-01181631
i386 randconfig-x005-01181631
i386 randconfig-x006-01181631
i386 randconfig-x007-01181631
i386 randconfig-x008-01181631
i386 randconfig-x009-01181631
Thanks,
Fengguang
[toc] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2016-01-19 15:30 +0100 |
| Message-ID | <qSFsd-Eb-3@gated-at.bofh.it> |
| In reply to | #1312134 |
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
[toc] | [prev] | [next] | [standalone]
| From | Fengguang Wu <fengguang.wu@intel.com> |
|---|---|
| Date | 2016-01-26 06:40 +0100 |
| Subject | Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE |
| Message-ID | <qV4wa-71M-3@gated-at.bofh.it> |
| In reply to | #1312278 |
On Tue, Jan 26, 2016 at 01:30:50PM +0800, Fengguang Wu wrote: > Hi Arnd, > > Sorry for the delay! I lost access to my email account for some week. > > On Tue, Jan 19, 2016 at 03:26:16PM +0100, Arnd Bergmann wrote: > > 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? > > There are a fixed set of config files for fast build tests (which I > selected randomly, feel free to ask me to change the list to more > reasonable ones): > > 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 And there is another set of best effort configs whose priority is in-between the above list and the arch/*/configs/* ones. arm-arm5 arm-arm67 arm-mmp arm-omap2plus_defconfig arm-s3c2410_defconfig arm-tegra_defconfig Thanks, Fengguang > The more configs included in arch/*/configs will be tested in a more > slow pace. So not included in this email does not mean they are not > tested -- they are likely not quick enough to catch this notification > email. > > > Can you always include the three I mentioned? > > Sure. > > Thanks, > Fengguang
[toc] | [prev] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2016-01-26 17:30 +0100 |
| Message-ID | <qVeFc-6F7-15@gated-at.bofh.it> |
| In reply to | #1317544 |
On Tuesday 26 January 2016 13:35:04 Fengguang Wu wrote: > > There are a fixed set of config files for fast build tests (which I > > selected randomly, feel free to ask me to change the list to more > > reasonable ones): > > > > 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 > > And there is another set of best effort configs whose priority is > in-between the above list and the arch/*/configs/* ones. > > arm-arm5 > arm-arm67 > arm-mmp > arm-omap2plus_defconfig > arm-s3c2410_defconfig > arm-tegra_defconfig > I think we want at least one ARMv7-M NOMMU target in the list, I'd pick efm32_defconfig as it has the least overlap with the drivers in the other configs. I don't know what arm-sh is, but I assume it's a superset of marzen, so you can probably drop marzen or move it down to the low-prio set. Similarly, the at_hdmac is likely a subset of at91_dt_defconfig and could be dropped. prima2, ep93xx and spear13xx, mmp and s3c2410 are all slow-moving platforms, I would not expect to see much results from running those compared to the more active platforms. The platforms with the most changes these days are omap2plus, sunxi, shmobile, and exynos (samsung), followed by some that are widely used but not changed as much including tegra, imx_v6_v7, mvebu_v7, and qcom (previously msm). iop and sa1100 are rather old and won't change much, but it can be good to keep them in there because they are for older CPU architectures and behave a little different from the modern ones. It might be better to replace iop with ixp4xx, as this one is the only big-endian defconfig build we have, and that sometimes catches build-time bugs. Arnd
[toc] | [prev] | [next] | [standalone]
| From | Fengguang Wu <fengguang.wu@intel.com> |
|---|---|
| Date | 2016-01-27 09:40 +0100 |
| Subject | Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE |
| Message-ID | <qVtNU-J7-11@gated-at.bofh.it> |
| In reply to | #1318114 |
Hi Arnd, 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/* Thanks, Fengguang On Tue, Jan 26, 2016 at 05:27:46PM +0100, Arnd Bergmann wrote: > On Tuesday 26 January 2016 13:35:04 Fengguang Wu wrote: > > > There are a fixed set of config files for fast build tests (which I > > > selected randomly, feel free to ask me to change the list to more > > > reasonable ones): > > > > > > 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 > > > > And there is another set of best effort configs whose priority is > > in-between the above list and the arch/*/configs/* ones. > > > > arm-arm5 > > arm-arm67 > > arm-mmp > > arm-omap2plus_defconfig > > arm-s3c2410_defconfig > > arm-tegra_defconfig > > > > I think we want at least one ARMv7-M NOMMU target in the list, > I'd pick efm32_defconfig as it has the least overlap with the > drivers in the other configs. > > I don't know what arm-sh is, but I assume it's a superset of > marzen, so you can probably drop marzen or move it down to the > low-prio set. Similarly, the at_hdmac is likely a subset of > at91_dt_defconfig and could be dropped. > > prima2, ep93xx and spear13xx, mmp and s3c2410 are all > slow-moving platforms, I would not expect to see much > results from running those compared to the more active > platforms. > > The platforms with the most changes these days are omap2plus, > sunxi, shmobile, and exynos (samsung), followed by some > that are widely used but not changed as much including > tegra, imx_v6_v7, mvebu_v7, and qcom (previously msm). > > iop and sa1100 are rather old and won't change much, but it > can be good to keep them in there because they are for older > CPU architectures and behave a little different from the > modern ones. It might be better to replace iop with ixp4xx, > as this one is the only big-endian defconfig build we have, > and that sometimes catches build-time bugs. > > Arnd
[toc] | [prev] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2016-01-27 10:20 +0100 |
| Message-ID | <qVuqB-1hZ-1@gated-at.bofh.it> |
| In reply to | #1318749 |
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? 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. Thanks! Arnd
[toc] | [prev] | [next] | [standalone]
| From | Fengguang Wu <fengguang.wu@intel.com> |
|---|---|
| Date | 2016-01-27 10:40 +0100 |
| Subject | Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE |
| Message-ID | <qVuJY-1sr-3@gated-at.bofh.it> |
| In reply to | #1318765 |
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
[toc] | [prev] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2016-01-27 10:50 +0100 |
| Message-ID | <qVuTF-1ws-19@gated-at.bofh.it> |
| In reply to | #1318787 |
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
[toc] | [prev] | [next] | [standalone]
| From | Fengguang Wu <fengguang.wu@intel.com> |
|---|---|
| Date | 2016-01-26 06:40 +0100 |
| Subject | Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE |
| Message-ID | <qV4wa-71M-5@gated-at.bofh.it> |
| In reply to | #1312278 |
Hi Arnd, Sorry for the delay! I lost access to my email account for some week. On Tue, Jan 19, 2016 at 03:26:16PM +0100, Arnd Bergmann wrote: > 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? There are a fixed set of config files for fast build tests (which I selected randomly, feel free to ask me to change the list to more reasonable ones): 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 The more configs included in arch/*/configs will be tested in a more slow pace. So not included in this email does not mean they are not tested -- they are likely not quick enough to catch this notification email. > Can you always include the three I mentioned? Sure. Thanks, Fengguang
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web