linux-next: Tree for Oct 3
Hi all,
Changes since 20191002:
New tree: tomoyo
My fixes tree contains:
04e6dac68d9b ("powerpc/64s/radix: fix for "tidy up TLB flushing code" and
!CONFIG_PPC_RADIX_MMU")
The amdgpu tree gained a conflict against Linus' tree.
The keys tree with gained a conflict against mips-fixes tree.
Non-merge commits (relative to Linus' tree): 1484
1654 files changed, 44635 insertions(+), 19751 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log
files in the Next directory. Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).
Below is a summary of the state of the merge.
I am currently merging 314 trees (counting Linus' and 78 trees of bug
fix patches pending for the current merge release).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
Gortmaker for triage and bug fixes.
--
Cheers,
Stephen Rothwell
$ git checkout master
$ git reset --hard stable
Merging origin/master (65aa35c93cc0 Merge tag 'erofs-for-5.4-rc2-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs)
Merging fixes/master (04e6dac68d9b powerpc/64s/radix: fix for "tidy up TLB
flushing code" and !CONFIG_PPC_RADIX_MMU)
Merging kbuild-current/fixes (d159d87700e9 namespace: fix namespace.pl script
to support relative paths)
Merging arc-current/for-curr (41277ba7eb4e ARC: mm: tlb flush optim: elide
redundant uTLB invalidates for MMUv3)
Merging arm-current/fixes (5b3efa4f1479 ARM: 8901/1: add a criteria for
pfn_valid of arm)
Merging arm-soc-fixes/arm/fixes (cdee3b60af59 ARM: dts: ux500: Fix up the CPU
thermal zone)
Merging arm64-fixes/for-next/fixes (a2b99dcac36c docs: arm64: Fix indentation
and doc formatting)
Merging m68k-current/for-linus (0f1979b402df m68k: Remove ioremap_fullcache())
Merging powerpc-fixes/fixes (253c892193ab powerpc/eeh: Fix eeh
eeh_debugfs_break_device() with SRIOV devices)
Merging s390-fixes/fixes (9f494438d4bc s390/qdio: clarify size of the QIB parm
area)
Merging sparc/master (038029c03e21 sparc: remove unneeded uapi/asm/statfs.h)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (53de429f4e88 net: hisilicon: Fix usage of uninitialized
variable in function mdio_sc_cfg_reg_write())
Merging bpf/master (a2d074e4c6e8 selftests/bpf: test_progs: Don't leak
server_fd in test_sockopt_inherit)
Merging ipsec/master (68ce6688a5ba net: sched: taprio: Fix potential integer
overflow in taprio_set_picos_per_byte)
Merging netfilter/master (34a4c95abd25 netfilter: nft_connlimit: disable bh on
garbage collection)
Merging ipvs/master (02dc96ef6c25 Merge
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net)
Merging wireless-drivers/master (c91a9cfe9f6d rt2x00: initialize last_reset)
Merging mac80211/master (569aad4fcd82 net: ag71xx: fix mdio subnode support)
Merging rdma-fixes/for-rc (b66f31efbdad RDMA/iwcm: Fix a lock inversion issue)
Merging sound-current/for-linus (f41f900568d9 ALSA: usb-audio: Add DSD support
for EVGA NU Audio)
Merging sound-asoc-fixes/for-linus (bbb90c4ed03b Merge branch 'asoc-5.4' into
asoc-linus)
Merging regmap-fixes/for-linus (54ecb8f7028c Linux 5.4-rc1)
Merging regulator-fixes/for-linus (c3f1e312854c Merge branch 'regulator-5.4'
into regulator-linus)
Merging spi-fixes/for-linus (6efab62559b1 Merge branch 'spi-5.4' into spi-linus)
Merging pci-current/for-linus (54ecb8f7028c Linux 5.4-rc1)
Merging driver-core.current/driver-core-linus (82af5b660967 sysfs: Fixes
__BIN_ATTR_WO() macro)
Merging tty.current/tty-linus (54ecb8f7028c Linux 5.4-rc1)
Merging usb.current/usb-linus (54ecb8f7028c Linux 5.4-rc1)
Merging usb-gadget-fixes/fixes (4a56a478a525 usb: gadget: mass_storage: Fix
races between fsg_disable
linux-next: Tree for Oct 3
Hi all, Changes since 20181002: The vfs tree gained conflicts against the f2fs tree. The net-next tree gained a conflict against the net tree. The bpf-next tree gained a build failure so I used the version from next-20181002. The devicetree tree gained a conflict against the c6x tree. The xarray tree gained a conflict against the f2fs tree. Non-merge commits (relative to Linus' tree): 7748 7535 files changed, 353115 insertions(+), 159195 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And finally, a simple boot test of the powerpc pseries_le_defconfig kernel in qemu (with and without kvm enabled). Below is a summary of the state of the merge. I am currently merging 290 trees (counting Linus' and 66 trees of bug fix patches pending for the current merge release). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (1d2ba7fee28b Merge tag 'fbdev-v4.19-rc7' of https://github.com/bzolnier/linux) Merging fixes/master (72358c0b59b7 linux-next: build warnings from the build of Linus' tree) Merging kbuild-current/fixes (ef8c4ed9db80 kbuild: allow to use GCC toolchain not in Clang search path) Merging arc-current/for-curr (40660f1fcee8 ARC: build: Don't set CROSS_COMPILE in arch's Makefile) Merging arm-current/fixes (3a58ac65e2d7 ARM: 8799/1: mm: fix pci_ioremap_io() offset check) Merging arm64-fixes/for-next/fixes (2a3f93459d68 arm64: KVM: Sanitize PSTATE.M when being set from userspace) Merging m68k-current/for-linus (0986b16ab49b m68k/mac: Use correct PMU response format) Merging powerpc-fixes/fixes (7e0cf1c983b5 selftests/powerpc: Fix Makefiles for headers_install change) Merging sparc/master (df2def49c57b Merge tag 'acpi-4.19-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (ff58e2df62ce nfp: avoid soft lockups under control message storm) Merging bpf/master (b0584ea66d73 bpf: don't accept cgroup local storage with zero value size) Merging ipsec/master (92d7c74b6f72 Merge branch 'for-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth) Merging netfilter/master (1ad98e9d1bdf tcp/dccp: fix lockdep issue when SYN is backlogged) Merging ipvs/master (feb9f55c33e5 netfilter: nft_dynset: allow dynamic updates of non-anonymous set) Merging wireless-drivers/master (3baafeffa48a iwlwifi: 1000: set the TFD queue size) Merging mac80211/master (848e616e66d4 cfg80211: fix wext-compat memory leak) Merging rdma-fixes/for-rc (5c5702e259dc RDMA/core: Set right entry state before releasing reference) Merging sound-current/for-linus (b3a5402cbceb ALSA: hda: Fix the audio-component completion timeout) Merging sound-asoc-fixes/for-linus (6f450574b28f Merge branch 'asoc-4.19' into asoc-linus) Merging regmap-fixes/for-linus (7876320f8880 Linux 4.19-rc4) Merging regulator-fixes/for-linus (17b57b1883c1 Linux 4.19-rc6) Merging spi-fixes/for-linus (17b57b1883c1 Linux 4.19-rc6) Merging pci-current/for-linus (95375f2ab296 PCI: mvebu: Fix PCI I/O mapping creation sequence) Merging driver-core.current/driver-core-linus (7876320f8880 Linux 4.19-rc4) Merging tty.current/tty-linus (17b57b1883c1 Linux 4.19-rc6) Merging usb.current/usb-linus (555df5820e73 usb: xhci-mtk: resume USB3 roothub first) Merging usb-gadget-fixes/fixes (d9707490077b usb: dwc2: Fix call location of dwc2_check_core_endianness) Merging usb-serial-fixes/usb-linus (f5fad711c06e USB: serial: simple: add Motorola Tetra MTP6550 id) Merging
linux-next: Tree for Oct 3
Hi all, Changes since 20181002: The vfs tree gained conflicts against the f2fs tree. The net-next tree gained a conflict against the net tree. The bpf-next tree gained a build failure so I used the version from next-20181002. The devicetree tree gained a conflict against the c6x tree. The xarray tree gained a conflict against the f2fs tree. Non-merge commits (relative to Linus' tree): 7748 7535 files changed, 353115 insertions(+), 159195 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And finally, a simple boot test of the powerpc pseries_le_defconfig kernel in qemu (with and without kvm enabled). Below is a summary of the state of the merge. I am currently merging 290 trees (counting Linus' and 66 trees of bug fix patches pending for the current merge release). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (1d2ba7fee28b Merge tag 'fbdev-v4.19-rc7' of https://github.com/bzolnier/linux) Merging fixes/master (72358c0b59b7 linux-next: build warnings from the build of Linus' tree) Merging kbuild-current/fixes (ef8c4ed9db80 kbuild: allow to use GCC toolchain not in Clang search path) Merging arc-current/for-curr (40660f1fcee8 ARC: build: Don't set CROSS_COMPILE in arch's Makefile) Merging arm-current/fixes (3a58ac65e2d7 ARM: 8799/1: mm: fix pci_ioremap_io() offset check) Merging arm64-fixes/for-next/fixes (2a3f93459d68 arm64: KVM: Sanitize PSTATE.M when being set from userspace) Merging m68k-current/for-linus (0986b16ab49b m68k/mac: Use correct PMU response format) Merging powerpc-fixes/fixes (7e0cf1c983b5 selftests/powerpc: Fix Makefiles for headers_install change) Merging sparc/master (df2def49c57b Merge tag 'acpi-4.19-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (ff58e2df62ce nfp: avoid soft lockups under control message storm) Merging bpf/master (b0584ea66d73 bpf: don't accept cgroup local storage with zero value size) Merging ipsec/master (92d7c74b6f72 Merge branch 'for-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth) Merging netfilter/master (1ad98e9d1bdf tcp/dccp: fix lockdep issue when SYN is backlogged) Merging ipvs/master (feb9f55c33e5 netfilter: nft_dynset: allow dynamic updates of non-anonymous set) Merging wireless-drivers/master (3baafeffa48a iwlwifi: 1000: set the TFD queue size) Merging mac80211/master (848e616e66d4 cfg80211: fix wext-compat memory leak) Merging rdma-fixes/for-rc (5c5702e259dc RDMA/core: Set right entry state before releasing reference) Merging sound-current/for-linus (b3a5402cbceb ALSA: hda: Fix the audio-component completion timeout) Merging sound-asoc-fixes/for-linus (6f450574b28f Merge branch 'asoc-4.19' into asoc-linus) Merging regmap-fixes/for-linus (7876320f8880 Linux 4.19-rc4) Merging regulator-fixes/for-linus (17b57b1883c1 Linux 4.19-rc6) Merging spi-fixes/for-linus (17b57b1883c1 Linux 4.19-rc6) Merging pci-current/for-linus (95375f2ab296 PCI: mvebu: Fix PCI I/O mapping creation sequence) Merging driver-core.current/driver-core-linus (7876320f8880 Linux 4.19-rc4) Merging tty.current/tty-linus (17b57b1883c1 Linux 4.19-rc6) Merging usb.current/usb-linus (555df5820e73 usb: xhci-mtk: resume USB3 roothub first) Merging usb-gadget-fixes/fixes (d9707490077b usb: dwc2: Fix call location of dwc2_check_core_endianness) Merging usb-serial-fixes/usb-linus (f5fad711c06e USB: serial: simple: add Motorola Tetra MTP6550 id) Merging
linux-next: Tree for Oct 3
Hi all, Changes since 20160930: The net-next tree gained conflicts against Linus' tree. The mac80211-next tree gained conflicts against Linus' tree. The xen-tip tree gained conflicts againt the tip tree. The tty tree lost its build failure. Non-merge commits (relative to Linus' tree): 13450 9993 files changed, 554934 insertions(+), 300943 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig (with CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig (this fails its final link) and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 243 trees (counting Linus' and 34 trees of patches pending for Linus' tree). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (be67d60ba944 Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip) Merging fixes/master (d3396e1e4ec4 Merge tag 'fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc) Merging kbuild-current/rc-fixes (d3e2773c4ede builddeb: Skip gcc-plugins when not configured) Merging arc-current/for-curr (3eab887a5542 Linux 4.8-rc4) Merging arm-current/fixes (d248220f0465 ARM: 8617/1: dma: fix dma_max_pfn()) Merging m68k-current/for-linus (6bd80f372371 m68k/defconfig: Update defconfigs for v4.7-rc2) Merging metag-fixes/fixes (97b1d23f7bcb metag: Drop show_mem() from mem_init()) Merging powerpc-fixes/fixes (b79331a5eb9f powerpc/powernv/pci: Fix m64 checks for SR-IOV and window alignment) Merging sparc/master (2a0100d7beeb sparc64: Fix non-SMP build.) Merging net/master (1cceda784980 sctp: fix the issue sctp_diag uses lock_sock in rcu_read_lock) Merging ipsec/master (b1f2beb87bb0 Merge tag 'media/v4.8-7' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media) Merging netfilter/master (440f895aa97f drivers: net: phy: xgene: Fix 'remove' function) Merging ipvs/master (ea43f860d984 Merge branch 'ethoc-fixes') Merging wireless-drivers/master (db64c5fa590b Merge tag 'iwlwifi-for-kalle-2016-09-15' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes) Merging mac80211/master (7ac327318e09 Merge tag 'mac80211-for-davem-2016-09-16' of git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211) Merging sound-current/for-linus (eeea8b40cd28 Merge tag 'asoc-v4.9' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-next) Merging pci-current/for-linus (035ee288ae7a PCI: Fix bridge_d3 update on device removal) Merging driver-core.current/driver-core-linus (c6935931c189 Linux 4.8-rc5) Merging tty.current/tty-linus (c6935931c189 Linux 4.8-rc5) Merging usb.current/usb-linus (3be7988674ab Linux 4.8-rc7) Merging usb-gadget-fixes/fixes (d8a4100ddc75 usb: gadget: udc: atmel: fix endpoint name) Merging usb-serial-fixes/usb-linus (f190fd92458d USB: serial: simple: add support for another Infineon flashloader) Merging usb-chipidea-fixes/ci-for-usb-stable (6f3c4fb6d05e usb: chipidea: udc: fix NULL ptr dereference in isr_setup_status_phase) Merging staging.current/staging-linus (9395452b4aab Linux 4.8-rc6) Merging char-misc.current/char-misc-linus (c6935931c189 Linux 4.8-rc5) Merging input-current/for-linus (9fb6de1b0bf4 Input: joydev - recognize devices with Z axis as joysticks) Merging crypto-current/master (80da44c29d99 crypto: vmx - Fix memory corruption caused by p8_ghash) Merging ide/master (797cee982eef Merge branch 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit) Merging rr-fixes/fixes (8244062ef1e5 modules: fix longstanding /proc/kallsyms vs module insertion race.) Merging vfio-fixes/for-linus
linux-next: Tree for Oct 3
Hi all, Changes since 20160930: The net-next tree gained conflicts against Linus' tree. The mac80211-next tree gained conflicts against Linus' tree. The xen-tip tree gained conflicts againt the tip tree. The tty tree lost its build failure. Non-merge commits (relative to Linus' tree): 13450 9993 files changed, 554934 insertions(+), 300943 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig (with CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig (this fails its final link) and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 243 trees (counting Linus' and 34 trees of patches pending for Linus' tree). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (be67d60ba944 Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip) Merging fixes/master (d3396e1e4ec4 Merge tag 'fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc) Merging kbuild-current/rc-fixes (d3e2773c4ede builddeb: Skip gcc-plugins when not configured) Merging arc-current/for-curr (3eab887a5542 Linux 4.8-rc4) Merging arm-current/fixes (d248220f0465 ARM: 8617/1: dma: fix dma_max_pfn()) Merging m68k-current/for-linus (6bd80f372371 m68k/defconfig: Update defconfigs for v4.7-rc2) Merging metag-fixes/fixes (97b1d23f7bcb metag: Drop show_mem() from mem_init()) Merging powerpc-fixes/fixes (b79331a5eb9f powerpc/powernv/pci: Fix m64 checks for SR-IOV and window alignment) Merging sparc/master (2a0100d7beeb sparc64: Fix non-SMP build.) Merging net/master (1cceda784980 sctp: fix the issue sctp_diag uses lock_sock in rcu_read_lock) Merging ipsec/master (b1f2beb87bb0 Merge tag 'media/v4.8-7' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media) Merging netfilter/master (440f895aa97f drivers: net: phy: xgene: Fix 'remove' function) Merging ipvs/master (ea43f860d984 Merge branch 'ethoc-fixes') Merging wireless-drivers/master (db64c5fa590b Merge tag 'iwlwifi-for-kalle-2016-09-15' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes) Merging mac80211/master (7ac327318e09 Merge tag 'mac80211-for-davem-2016-09-16' of git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211) Merging sound-current/for-linus (eeea8b40cd28 Merge tag 'asoc-v4.9' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-next) Merging pci-current/for-linus (035ee288ae7a PCI: Fix bridge_d3 update on device removal) Merging driver-core.current/driver-core-linus (c6935931c189 Linux 4.8-rc5) Merging tty.current/tty-linus (c6935931c189 Linux 4.8-rc5) Merging usb.current/usb-linus (3be7988674ab Linux 4.8-rc7) Merging usb-gadget-fixes/fixes (d8a4100ddc75 usb: gadget: udc: atmel: fix endpoint name) Merging usb-serial-fixes/usb-linus (f190fd92458d USB: serial: simple: add support for another Infineon flashloader) Merging usb-chipidea-fixes/ci-for-usb-stable (6f3c4fb6d05e usb: chipidea: udc: fix NULL ptr dereference in isr_setup_status_phase) Merging staging.current/staging-linus (9395452b4aab Linux 4.8-rc6) Merging char-misc.current/char-misc-linus (c6935931c189 Linux 4.8-rc5) Merging input-current/for-linus (9fb6de1b0bf4 Input: joydev - recognize devices with Z axis as joysticks) Merging crypto-current/master (80da44c29d99 crypto: vmx - Fix memory corruption caused by p8_ghash) Merging ide/master (797cee982eef Merge branch 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit) Merging rr-fixes/fixes (8244062ef1e5 modules: fix longstanding /proc/kallsyms vs module insertion race.) Merging vfio-fixes/for-linus
linux-next: Tree for Oct 3
Hi all, There will be no linux-next release on Monday. Changes since 20141002: The arm-soc tree lost its build failures. The staging tree lost its build failure. The target-updates gained a build failure for which I reverted a commit. Non-merge commits (relative to Linus' tree): 9295 7875 files changed, 366489 insertions(+), 270149 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a multi_v7_defconfig for arm. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm defconfig. Below is a summary of the state of the merge. I am currently merging 227 trees (counting Linus' and 32 trees of patches pending for Linus' tree). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (b601ce0fe3aa Merge tag 'media/v3.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media) Merging fixes/master (b94d525e58dc Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging kbuild-current/rc-fixes (7d1311b93e58 Linux 3.17-rc1) Merging arc-current/for-curr (2ce7598c9a45 Linux 3.17-rc4) Merging arm-current/fixes (ad684dce87fa ARM: 8179/1: kprobes-test: Fix compile error "bad immediate value for offset") Merging m68k-current/for-linus (4ed7800987b1 m68k: Wire up memfd_create) Merging metag-fixes/fixes (ffe6902b66aa asm-generic: remove _STK_LIM_MAX) Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5) Merging powerpc-merge/merge (396a34340cdf powerpc: Fix endianness of flash_block_list in rtas_flash) Merging powerpc-merge-mpe/for-linus (7d59deb50aaf powerpc: Wire up sys_seccomp(), sys_getrandom() and sys_memfd_create()) Merging sparc/master (ca605b7dd740 sparc64: Add vio_set_intr() to enable/disable Rx interrupts) Merging net/master (50dddff3cb9a Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging ipsec/master (b8c203b2d2fc xfrm: Generate queueing routes only from route lookup functions) Merging sound-current/for-linus (b7c2dc8e684a Merge tag 'asoc-v3.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus) Merging pci-current/for-linus (7cbeb9f90db8 PCI: pciehp: Fix pcie_wait_cmd() timeout) Merging wireless/master (f8adaf0ae978 brcmfmac: Fix off by one bug in brcmf_count_20mhz_channels()) Merging driver-core.current/driver-core-linus (9e82bf014195 Linux 3.17-rc5) Merging tty.current/tty-linus (9e82bf014195 Linux 3.17-rc5) Merging usb.current/usb-linus (0f33be009b89 Linux 3.17-rc6) Merging usb-gadget-fixes/fixes (0b93a4c838fa usb: dwc3: fix TRB completion when multiple TRBs are started) Merging usb-serial-fixes/usb-linus (dee80ad12d2b USB: cp210x: add support for Seluxit USB dongle) Merging staging.current/staging-linus (0f33be009b89 Linux 3.17-rc6) Merging char-misc.current/char-misc-linus (9e82bf014195 Linux 3.17-rc5) Merging input-current/for-linus (3049683eafdb Input: i8042 - fix Asus X450LCP touchpad detection) Merging md-current/for-linus (d47648fcf061 raid5: avoid finding "discard" stripe) Merging crypto-current/master (7da4b29d496b crypto: aesni - disable "by8" AVX CTR optimization) Merging ide/master (a53dae49b2fe ide: use module_platform_driver()) Merging dwmw2/master (5950f0803ca9 pcmcia: remove RPX board stuff) Merging devicetree-current/devicetree/merge (e66c98c7a0ea of: Fix NULL dereference in selftest removal code) Merging rr-fixes/fixes (f49819560f53 virtio-rng: skip reading when we start to remove the device) Merging vfio-fixes/for-linus (239a87020b26 Merge branch 'for-joerg/arm-smmu/fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/will/linux into for-linus) Merging kselftest-fixes/fixes (ce6a144a0d01 selftests/memfd: Run test on all architectures) Merging
linux-next: Tree for Oct 3
Hi all, There will be no linux-next release on Monday. Changes since 20141002: The arm-soc tree lost its build failures. The staging tree lost its build failure. The target-updates gained a build failure for which I reverted a commit. Non-merge commits (relative to Linus' tree): 9295 7875 files changed, 366489 insertions(+), 270149 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use git pull to do so as that will try to merge the new linux-next release with the old one. You should use git fetch and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a multi_v7_defconfig for arm. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm defconfig. Below is a summary of the state of the merge. I am currently merging 227 trees (counting Linus' and 32 trees of patches pending for Linus' tree). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (b601ce0fe3aa Merge tag 'media/v3.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media) Merging fixes/master (b94d525e58dc Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging kbuild-current/rc-fixes (7d1311b93e58 Linux 3.17-rc1) Merging arc-current/for-curr (2ce7598c9a45 Linux 3.17-rc4) Merging arm-current/fixes (ad684dce87fa ARM: 8179/1: kprobes-test: Fix compile error bad immediate value for offset) Merging m68k-current/for-linus (4ed7800987b1 m68k: Wire up memfd_create) Merging metag-fixes/fixes (ffe6902b66aa asm-generic: remove _STK_LIM_MAX) Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5) Merging powerpc-merge/merge (396a34340cdf powerpc: Fix endianness of flash_block_list in rtas_flash) Merging powerpc-merge-mpe/for-linus (7d59deb50aaf powerpc: Wire up sys_seccomp(), sys_getrandom() and sys_memfd_create()) Merging sparc/master (ca605b7dd740 sparc64: Add vio_set_intr() to enable/disable Rx interrupts) Merging net/master (50dddff3cb9a Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging ipsec/master (b8c203b2d2fc xfrm: Generate queueing routes only from route lookup functions) Merging sound-current/for-linus (b7c2dc8e684a Merge tag 'asoc-v3.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus) Merging pci-current/for-linus (7cbeb9f90db8 PCI: pciehp: Fix pcie_wait_cmd() timeout) Merging wireless/master (f8adaf0ae978 brcmfmac: Fix off by one bug in brcmf_count_20mhz_channels()) Merging driver-core.current/driver-core-linus (9e82bf014195 Linux 3.17-rc5) Merging tty.current/tty-linus (9e82bf014195 Linux 3.17-rc5) Merging usb.current/usb-linus (0f33be009b89 Linux 3.17-rc6) Merging usb-gadget-fixes/fixes (0b93a4c838fa usb: dwc3: fix TRB completion when multiple TRBs are started) Merging usb-serial-fixes/usb-linus (dee80ad12d2b USB: cp210x: add support for Seluxit USB dongle) Merging staging.current/staging-linus (0f33be009b89 Linux 3.17-rc6) Merging char-misc.current/char-misc-linus (9e82bf014195 Linux 3.17-rc5) Merging input-current/for-linus (3049683eafdb Input: i8042 - fix Asus X450LCP touchpad detection) Merging md-current/for-linus (d47648fcf061 raid5: avoid finding discard stripe) Merging crypto-current/master (7da4b29d496b crypto: aesni - disable by8 AVX CTR optimization) Merging ide/master (a53dae49b2fe ide: use module_platform_driver()) Merging dwmw2/master (5950f0803ca9 pcmcia: remove RPX board stuff) Merging devicetree-current/devicetree/merge (e66c98c7a0ea of: Fix NULL dereference in selftest removal code) Merging rr-fixes/fixes (f49819560f53 virtio-rng: skip reading when we start to remove the device) Merging vfio-fixes/for-linus (239a87020b26 Merge branch 'for-joerg/arm-smmu/fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/will/linux into for-linus) Merging kselftest-fixes/fixes (ce6a144a0d01 selftests/memfd: Run test on all architectures) Merging
Re: linux-next: Tree for Oct 3
On 10/04/2013 10:04 AM, Olof Johansson wrote: On Fri, Oct 4, 2013 at 6:44 AM, Guenter Roeck wrote: On 10/03/2013 10:41 PM, Olof Johansson wrote: On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck wrote: On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? ARM is pretty well-covered by my builds, I post results at: http://lists.linaro.org/mailman/listinfo/kernel-build-reports Great summaries. Do you have a single builder, or several builders and collect the results ? Either case, any chance sharing the buildbot scripts ? My buildbot scripts are some pretty ugly hacks that I don't particularly feel like publishing to the world. I can send you a copy though. Not much different to the quality of mine :). Would be great if you can send me a copy. For my scripts, I still have some secrets in there like my gmail password in the clear. I'll have to make sure it is removed before I can publish it. The builder is one single beefy machine that i have on loan. It wouldn't be hard to make it distributed instead though; I've toyed around with prototypes for that in the past. I would love to have something like that .. mine essentially consists of four PCs with quad-core CPUs, plus two smaller systems which are not always online. Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 04, 2013 at 11:28:39AM +0100, Mark Brown wrote: > On Thu, Oct 03, 2013 at 10:23:39PM -0700, Guenter Roeck wrote: > > On 10/03/2013 06:02 PM, Mark Brown wrote: > > > >Due to the length of time taken to run all the allmodconfigs I skipped > > >the defconfig tests; I know Olof has the ARM stuff covered in his > > >autobuilder. I'm going to use allyesconfig tomorrow since that should > > >run faster so hopefully I can cover the ARM, i386 and x86_64 configs > > >again. > > > I could try to set up the buildbot farm I am using for -stable candidates > > to also test the -next tree. Would that help ? > > Yes, that'd be great. Like Olof said ARM is pretty well covered but > adding more platforms would be very helpful. Ok, here are the results based on v3.12-rc3-3771-gedc72f7. Build summary: total: 110 pass: 86 skipped: 4 fail: 20 'skipped' means the configuration does not (or no longer) exist. Failed builds: arm:allmodconfig arm:ape6evm_defconfig arm:marzen_defconfig arm:armadillo800eva_defconfig arm:mackerel_defconfig blackfin:defconfig metag:defconfig metag:meta1_defconfig metag:meta2_defconfig metag:meta2_smp_defconfig mips:defconfig mips:bcm63xx_defconfig mips:nlm_xlp_defconfig mips:fuloong2e_defconfig mips:e55_defconfig mips:malta_defconfig powerpc:ppc64e_defconfig powerpc:chroma_defconfig powerpc:mpc85xx_smp_defconfig sparc64:allmodconfig mips and mips64 qemu tests fail as well. mips test builds but hangs early in boot, mips64 fails to build. On the plus side, the sh qemu warning (WARNING traceback during boot) is no longer observed. Details are at http://server.roeck-us.net:8010/builders. If everything works as intended, updates to the repository should trigger an automatic re-build. No guarantees, though - I had some trouble with the initial checkout. Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 04, 2013 at 10:00:20AM -0700, Olof Johansson wrote: > On Fri, Oct 4, 2013 at 7:34 AM, Mark Brown wrote: > > On Fri, Oct 04, 2013 at 06:44:56AM -0700, Guenter Roeck wrote: > > > >> Great summaries. Do you have a single builder, or several builders and > >> collect the results ? Either case, any chance sharing the buildbot scripts > >> ? > > > > There's a repo at: > > > > git://git.linaro.org/people/khilman/build-scripts.git > > A git url is frustrating, especially when the gitweb isn't configured > to use the same paths. > > https://git.linaro.org/gitweb?p=people/khilman/build-scripts.git;a=summary > I was able to clone it, though. > > (Olof and Kevin have been collaborating on them). > > What I use is quite different from that, but the origins are more or > less the same. > No problem. I'll see if there is anything I can use to improve my buildbot scripts. My key problem is that I have not figured out how to merge results from multiple builders into a single summary e-mail. Hope I can solve that problem at some point. Time is always the problem. Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 4, 2013 at 6:44 AM, Guenter Roeck wrote: > On 10/03/2013 10:41 PM, Olof Johansson wrote: >> >> On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck wrote: >>> >>> On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. >>> >>> I could try to set up the buildbot farm I am using for -stable candidates >>> to also test the -next tree. Would that help ? >> >> >> ARM is pretty well-covered by my builds, I post results at: >> >> http://lists.linaro.org/mailman/listinfo/kernel-build-reports >> > > Great summaries. Do you have a single builder, or several builders and > collect the results ? Either case, any chance sharing the buildbot scripts ? My buildbot scripts are some pretty ugly hacks that I don't particularly feel like publishing to the world. I can send you a copy though. The builder is one single beefy machine that i have on loan. It wouldn't be hard to make it distributed instead though; I've toyed around with prototypes for that in the past. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 4, 2013 at 7:34 AM, Mark Brown wrote: > On Fri, Oct 04, 2013 at 06:44:56AM -0700, Guenter Roeck wrote: > >> Great summaries. Do you have a single builder, or several builders and >> collect the results ? Either case, any chance sharing the buildbot scripts ? > > There's a repo at: > > git://git.linaro.org/people/khilman/build-scripts.git A git url is frustrating, especially when the gitweb isn't configured to use the same paths. https://git.linaro.org/gitweb?p=people/khilman/build-scripts.git;a=summary > (Olof and Kevin have been collaborating on them). What I use is quite different from that, but the origins are more or less the same. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 04, 2013 at 06:44:56AM -0700, Guenter Roeck wrote: > Great summaries. Do you have a single builder, or several builders and > collect the results ? Either case, any chance sharing the buildbot scripts ? There's a repo at: git://git.linaro.org/people/khilman/build-scripts.git (Olof and Kevin have been collaborating on them). signature.asc Description: Digital signature
Re: linux-next: Tree for Oct 3
On 10/03/2013 10:41 PM, Olof Johansson wrote: On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck wrote: On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? ARM is pretty well-covered by my builds, I post results at: http://lists.linaro.org/mailman/listinfo/kernel-build-reports Great summaries. Do you have a single builder, or several builders and collect the results ? Either case, any chance sharing the buildbot scripts ? Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Thu, Oct 03, 2013 at 10:23:39PM -0700, Guenter Roeck wrote: > On 10/03/2013 06:02 PM, Mark Brown wrote: > >Due to the length of time taken to run all the allmodconfigs I skipped > >the defconfig tests; I know Olof has the ARM stuff covered in his > >autobuilder. I'm going to use allyesconfig tomorrow since that should > >run faster so hopefully I can cover the ARM, i386 and x86_64 configs > >again. > I could try to set up the buildbot farm I am using for -stable candidates > to also test the -next tree. Would that help ? Yes, that'd be great. Like Olof said ARM is pretty well covered but adding more platforms would be very helpful. signature.asc Description: Digital signature
Re: linux-next: Tree for Oct 3
On Thu, Oct 03, 2013 at 10:23:39PM -0700, Guenter Roeck wrote: On 10/03/2013 06:02 PM, Mark Brown wrote: Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? Yes, that'd be great. Like Olof said ARM is pretty well covered but adding more platforms would be very helpful. signature.asc Description: Digital signature
Re: linux-next: Tree for Oct 3
On 10/03/2013 10:41 PM, Olof Johansson wrote: On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck li...@roeck-us.net wrote: On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? ARM is pretty well-covered by my builds, I post results at: http://lists.linaro.org/mailman/listinfo/kernel-build-reports Great summaries. Do you have a single builder, or several builders and collect the results ? Either case, any chance sharing the buildbot scripts ? Thanks, Guenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 04, 2013 at 06:44:56AM -0700, Guenter Roeck wrote: Great summaries. Do you have a single builder, or several builders and collect the results ? Either case, any chance sharing the buildbot scripts ? There's a repo at: git://git.linaro.org/people/khilman/build-scripts.git (Olof and Kevin have been collaborating on them). signature.asc Description: Digital signature
Re: linux-next: Tree for Oct 3
On Fri, Oct 4, 2013 at 7:34 AM, Mark Brown broo...@kernel.org wrote: On Fri, Oct 04, 2013 at 06:44:56AM -0700, Guenter Roeck wrote: Great summaries. Do you have a single builder, or several builders and collect the results ? Either case, any chance sharing the buildbot scripts ? There's a repo at: git://git.linaro.org/people/khilman/build-scripts.git A git url is frustrating, especially when the gitweb isn't configured to use the same paths. https://git.linaro.org/gitweb?p=people/khilman/build-scripts.git;a=summary (Olof and Kevin have been collaborating on them). What I use is quite different from that, but the origins are more or less the same. -Olof -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 4, 2013 at 6:44 AM, Guenter Roeck li...@roeck-us.net wrote: On 10/03/2013 10:41 PM, Olof Johansson wrote: On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck li...@roeck-us.net wrote: On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? ARM is pretty well-covered by my builds, I post results at: http://lists.linaro.org/mailman/listinfo/kernel-build-reports Great summaries. Do you have a single builder, or several builders and collect the results ? Either case, any chance sharing the buildbot scripts ? My buildbot scripts are some pretty ugly hacks that I don't particularly feel like publishing to the world. I can send you a copy though. The builder is one single beefy machine that i have on loan. It wouldn't be hard to make it distributed instead though; I've toyed around with prototypes for that in the past. -Olof -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 04, 2013 at 10:00:20AM -0700, Olof Johansson wrote: On Fri, Oct 4, 2013 at 7:34 AM, Mark Brown broo...@kernel.org wrote: On Fri, Oct 04, 2013 at 06:44:56AM -0700, Guenter Roeck wrote: Great summaries. Do you have a single builder, or several builders and collect the results ? Either case, any chance sharing the buildbot scripts ? There's a repo at: git://git.linaro.org/people/khilman/build-scripts.git A git url is frustrating, especially when the gitweb isn't configured to use the same paths. https://git.linaro.org/gitweb?p=people/khilman/build-scripts.git;a=summary I was able to clone it, though. (Olof and Kevin have been collaborating on them). What I use is quite different from that, but the origins are more or less the same. No problem. I'll see if there is anything I can use to improve my buildbot scripts. My key problem is that I have not figured out how to merge results from multiple builders into a single summary e-mail. Hope I can solve that problem at some point. Time is always the problem. Thanks, Guenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Fri, Oct 04, 2013 at 11:28:39AM +0100, Mark Brown wrote: On Thu, Oct 03, 2013 at 10:23:39PM -0700, Guenter Roeck wrote: On 10/03/2013 06:02 PM, Mark Brown wrote: Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? Yes, that'd be great. Like Olof said ARM is pretty well covered but adding more platforms would be very helpful. Ok, here are the results based on v3.12-rc3-3771-gedc72f7. Build summary: total: 110 pass: 86 skipped: 4 fail: 20 'skipped' means the configuration does not (or no longer) exist. Failed builds: arm:allmodconfig arm:ape6evm_defconfig arm:marzen_defconfig arm:armadillo800eva_defconfig arm:mackerel_defconfig blackfin:defconfig metag:defconfig metag:meta1_defconfig metag:meta2_defconfig metag:meta2_smp_defconfig mips:defconfig mips:bcm63xx_defconfig mips:nlm_xlp_defconfig mips:fuloong2e_defconfig mips:e55_defconfig mips:malta_defconfig powerpc:ppc64e_defconfig powerpc:chroma_defconfig powerpc:mpc85xx_smp_defconfig sparc64:allmodconfig mips and mips64 qemu tests fail as well. mips test builds but hangs early in boot, mips64 fails to build. On the plus side, the sh qemu warning (WARNING traceback during boot) is no longer observed. Details are at http://server.roeck-us.net:8010/builders. If everything works as intended, updates to the repository should trigger an automatic re-build. No guarantees, though - I had some trouble with the initial checkout. Guenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On 10/04/2013 10:04 AM, Olof Johansson wrote: On Fri, Oct 4, 2013 at 6:44 AM, Guenter Roeck li...@roeck-us.net wrote: On 10/03/2013 10:41 PM, Olof Johansson wrote: On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck li...@roeck-us.net wrote: On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? ARM is pretty well-covered by my builds, I post results at: http://lists.linaro.org/mailman/listinfo/kernel-build-reports Great summaries. Do you have a single builder, or several builders and collect the results ? Either case, any chance sharing the buildbot scripts ? My buildbot scripts are some pretty ugly hacks that I don't particularly feel like publishing to the world. I can send you a copy though. Not much different to the quality of mine :). Would be great if you can send me a copy. For my scripts, I still have some secrets in there like my gmail password in the clear. I'll have to make sure it is removed before I can publish it. The builder is one single beefy machine that i have on loan. It wouldn't be hard to make it distributed instead though; I've toyed around with prototypes for that in the past. I would love to have something like that .. mine essentially consists of four PCs with quad-core CPUs, plus two smaller systems which are not always online. Thanks, Guenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck wrote: > On 10/03/2013 06:02 PM, Mark Brown wrote: >> >> Hi all, >> >> Better late than never I've uploaded today's linux-next tree to the >> master branch of the repository below: >> >> git://gitorious.org/thierryreding/linux-next.git >> >> A next-20131003 tag is also provided for convenience. >> >> A few new conflicts today caused by the removal of the h8300 >> architecture which I didn't report for triviality. Several new build >> failures were found as a result of running allmodconfig tests between >> merges all of which have been reported and I'm still carrying the i.MX >> fix that Thierry has been carrying. >> >> Due to the length of time taken to run all the allmodconfigs I skipped >> the defconfig tests; I know Olof has the ARM stuff covered in his >> autobuilder. I'm going to use allyesconfig tomorrow since that should >> run faster so hopefully I can cover the ARM, i386 and x86_64 configs >> again. >> > > I could try to set up the buildbot farm I am using for -stable candidates > to also test the -next tree. Would that help ? ARM is pretty well-covered by my builds, I post results at: http://lists.linaro.org/mailman/listinfo/kernel-build-reports But I'm sure others would be useful. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
linux-next: Tree for Oct 3
Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. Thanks, Mark signature.asc Description: Digital signature
linux-next: Tree for Oct 3
Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. Thanks, Mark signature.asc Description: Digital signature
Re: linux-next: Tree for Oct 3
On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? Thanks, Guenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3
On Thu, Oct 3, 2013 at 10:23 PM, Guenter Roeck li...@roeck-us.net wrote: On 10/03/2013 06:02 PM, Mark Brown wrote: Hi all, Better late than never I've uploaded today's linux-next tree to the master branch of the repository below: git://gitorious.org/thierryreding/linux-next.git A next-20131003 tag is also provided for convenience. A few new conflicts today caused by the removal of the h8300 architecture which I didn't report for triviality. Several new build failures were found as a result of running allmodconfig tests between merges all of which have been reported and I'm still carrying the i.MX fix that Thierry has been carrying. Due to the length of time taken to run all the allmodconfigs I skipped the defconfig tests; I know Olof has the ARM stuff covered in his autobuilder. I'm going to use allyesconfig tomorrow since that should run faster so hopefully I can cover the ARM, i386 and x86_64 configs again. I could try to set up the buildbot farm I am using for -stable candidates to also test the -next tree. Would that help ? ARM is pretty well-covered by my builds, I post results at: http://lists.linaro.org/mailman/listinfo/kernel-build-reports But I'm sure others would be useful. -Olof -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3 (mfd/syscon)
Hi Randy, On 4 October 2012 07:31, Randy Dunlap wrote: > On 10/03/2012 12:30 AM, Stephen Rothwell wrote: > >> Hi all, >> >> Do not add stuff destined for v3.8 to your linux-next included branches >> until after v3.7-rc1 is released. >> >> Changes since 201201002: >> > > > on i386: > > CC drivers/mfd/syscon.o > drivers/mfd/syscon.c:94:15: error: variable 'syscon_regmap_config' has > initializer but incomplete type > drivers/mfd/syscon.c:95:2: error: unknown field 'reg_bits' specified in > initializer > drivers/mfd/syscon.c:95:2: warning: excess elements in struct initializer > drivers/mfd/syscon.c:95:2: warning: (near initialization for > 'syscon_regmap_config') > drivers/mfd/syscon.c:96:2: error: unknown field 'val_bits' specified in > initializer > drivers/mfd/syscon.c:96:2: warning: excess elements in struct initializer > drivers/mfd/syscon.c:96:2: warning: (near initialization for > 'syscon_regmap_config') > drivers/mfd/syscon.c:97:2: error: unknown field 'reg_stride' specified in > initializer > drivers/mfd/syscon.c:97:2: warning: excess elements in struct initializer > drivers/mfd/syscon.c:97:2: warning: (near initialization for > 'syscon_regmap_config') > drivers/mfd/syscon.c: In function 'syscon_probe': > drivers/mfd/syscon.c:124:2: error: invalid use of undefined type 'struct > regmap_config' > drivers/mfd/syscon.c:125:2: error: implicit declaration of function > 'devm_regmap_init_mmio' > drivers/mfd/syscon.c:125:17: warning: assignment makes pointer from integer > without a cast > make[3]: *** [drivers/mfd/syscon.o] Error 1 > > > Full randconfig file is attached. > I sent out the fix patch with you CC-ed. Regards Dong Aisheng -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3 (mfd/syscon)
Hi Randy, On 4 October 2012 07:31, Randy Dunlap rdun...@xenotime.net wrote: On 10/03/2012 12:30 AM, Stephen Rothwell wrote: Hi all, Do not add stuff destined for v3.8 to your linux-next included branches until after v3.7-rc1 is released. Changes since 201201002: on i386: CC drivers/mfd/syscon.o drivers/mfd/syscon.c:94:15: error: variable 'syscon_regmap_config' has initializer but incomplete type drivers/mfd/syscon.c:95:2: error: unknown field 'reg_bits' specified in initializer drivers/mfd/syscon.c:95:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:95:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c:96:2: error: unknown field 'val_bits' specified in initializer drivers/mfd/syscon.c:96:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:96:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c:97:2: error: unknown field 'reg_stride' specified in initializer drivers/mfd/syscon.c:97:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:97:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c: In function 'syscon_probe': drivers/mfd/syscon.c:124:2: error: invalid use of undefined type 'struct regmap_config' drivers/mfd/syscon.c:125:2: error: implicit declaration of function 'devm_regmap_init_mmio' drivers/mfd/syscon.c:125:17: warning: assignment makes pointer from integer without a cast make[3]: *** [drivers/mfd/syscon.o] Error 1 Full randconfig file is attached. I sent out the fix patch with you CC-ed. Regards Dong Aisheng -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for Oct 3 (mfd/syscon)
On 10/03/2012 12:30 AM, Stephen Rothwell wrote: > Hi all, > > Do not add stuff destined for v3.8 to your linux-next included branches > until after v3.7-rc1 is released. > > Changes since 201201002: > on i386: CC drivers/mfd/syscon.o drivers/mfd/syscon.c:94:15: error: variable 'syscon_regmap_config' has initializer but incomplete type drivers/mfd/syscon.c:95:2: error: unknown field 'reg_bits' specified in initializer drivers/mfd/syscon.c:95:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:95:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c:96:2: error: unknown field 'val_bits' specified in initializer drivers/mfd/syscon.c:96:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:96:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c:97:2: error: unknown field 'reg_stride' specified in initializer drivers/mfd/syscon.c:97:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:97:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c: In function 'syscon_probe': drivers/mfd/syscon.c:124:2: error: invalid use of undefined type 'struct regmap_config' drivers/mfd/syscon.c:125:2: error: implicit declaration of function 'devm_regmap_init_mmio' drivers/mfd/syscon.c:125:17: warning: assignment makes pointer from integer without a cast make[3]: *** [drivers/mfd/syscon.o] Error 1 Full randconfig file is attached. -- ~Randy # # Automatically generated file; DO NOT EDIT. # Linux/i386 3.6.0 Kernel Configuration # # CONFIG_64BIT is not set CONFIG_X86_32=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf32-i386" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_GPIO=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_ARCH_HAS_CPU_AUTOPROBE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_32_SMP=y CONFIG_X86_HT=y CONFIG_X86_32_LAZY_GS=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-ecx -fcall-saved-edx" CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_HAVE_IRQ_WORK=y CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set CONFIG_DEFAULT_HOSTNAME="(none)" # CONFIG_SWAP is not set CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set CONFIG_FHANDLE=y CONFIG_AUDIT=y # CONFIG_AUDITSYSCALL is not set CONFIG_AUDIT_LOGINUID_IMMUTABLE=y CONFIG_HAVE_GENERIC_HARDIRQS=y # # IRQ subsystem # CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_GENERIC_IRQ_CHIP=y CONFIG_IRQ_DOMAIN=y # CONFIG_IRQ_DOMAIN_DEBUG is not set CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_KTIME_SCALAR=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # # CONFIG_TICK_CPU_ACCOUNTING is not set CONFIG_IRQ_TIME_ACCOUNTING=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_TASKSTATS=y # CONFIG_TASK_DELAY_ACCT is not set # CONFIG_TASK_XACCT is not set # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_PREEMPT_RCU is not set CONFIG_RCU_FANOUT=32 CONFIG_RCU_FANOUT_LEAF=16 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_RCU_FAST_NO_HZ is not set # CONFIG_TREE_RCU_TRACE is not set CONFIG_IKCONFIG=y CONFIG_LOG_BUF_SHIFT=17 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y # CONFIG_CGROUPS is not set CONFIG_CHECKPOINT_RESTORE=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y # CONFIG_IPC_NS is not set CONFIG_PID_NS=y # CONFIG_NET_NS is not set # CONFIG_SCHED_AUTOGROUP is not set # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_ANON_INODES=y CONFIG_EXPERT=y CONFIG_UID16=y CONFIG_KALLSYMS=y
linux-next: Tree for Oct 3
Hi all, Do not add stuff destined for v3.8 to your linux-next included branches until after v3.7-rc1 is released. Changes since 201201002: Removed tree: rr New trees: modules and virtio (replacing rr) Conflicts are migrating as trees are merged by Linus. The nfs tree lost its build failure. The ubi tree gained a build failure so I used the version from next-20121002. The mfd tree gained a conflict against Linus' tree. The battery tree gained a conflict against the mfd tree. The xen-two tree lost its build failure. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" as mentioned in the FAQ on the wiki (see below). You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc, sparc64 and arm defconfig. These builds also have CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary. Below is a summary of the state of the merge. We are up to 202 trees (counting Linus' and 26 trees of patches pending for Linus' tree), more are welcome (even if they are currently empty). Thanks to those who have contributed, and to those who haven't, please do. Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. There is a wiki covering stuff to do with linux-next at http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel. -- Cheers, Stephen Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (7fe0b14 Merge tag 'spi-3.7' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc) Merging fixes/master (9023a40 Merge tag 'mmc-fixes-for-3.5-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc) Merging kbuild-current/rc-fixes (fe04ddf kbuild: Do not package /boot and /lib in make tar-pkg) Merging arm-current/fixes (7253b85 ARM: 7541/1: Add ARM ERRATA 775420 workaround) Merging m68k-current/for-linus (f82735d m68k: Use PTR_RET rather than if(IS_ERR(...)) + PTR_ERR) Merging powerpc-merge/merge (636802e powerpc: Don't use __put_user() in patch_instruction) Merging sparc/master (1b62ca7 sparc64: Fix return value of Niagara-2 memcpy.) Merging net/master (a0d271c Linux 3.6) Merging sound-current/for-linus (5d037f9 Merge tag 'asoc-3.6' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus) Merging pci-current/for-linus (0ff9514 PCI: Don't print anything while decoding is disabled) Merging wireless/master (a7be50b iwlwifi: don't double free the interrupt in failure path) Merging driver-core.current/driver-core-linus (5698bd7 Linux 3.6-rc6) Merging tty.current/tty-linus (5698bd7 Linux 3.6-rc6) Merging usb.current/usb-linus (0d00dc2 USB: Fix race condition when removing host controllers) Merging staging.current/staging-linus (5698bd7 Linux 3.6-rc6) Merging char-misc.current/char-misc-linus (fea7a08 Linux 3.6-rc3) Merging input-current/for-linus (dde3ada Merge branch 'next' into for-linus) Merging md-current/for-linus (80b4812 md/raid10: fix "enough" function for detecting if array is failed.) Merging audit-current/for-linus (c158a35 audit: no leading space in audit_log_d_path prefix) Merging crypto-current/master (298b973 crypto: x86/glue_helper - fix storing of new IV in CBC encryption) Merging ide/master (9974e43 ide: fix generic_ide_suspend/resume Oops) Merging dwmw2/master (244dc4e Merge git://git.infradead.org/users/dwmw2/random-2.6) Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to inline functions) Merging irqdomain-current/irqdomain/merge (15e06bf irqdomain: Fix debugfs formatting) Merging devicetree-current/devicetree/merge (4e8383b of: release node fix for of_parse_phandle_with_args) Merging spi-current/spi/merge (d1c185b of/spi: Fix SPI module loading by using proper "spi:" modalias prefixes.) Merging gpio-current/gpio/merge (96b7064 gpio/tca6424: merge I2C transactions, remove cast) Merging arm/for-next (f537d06 Merge branch 'devel-stable' into for-next) CONFLICT
linux-next: Tree for Oct 3
Hi all, Do not add stuff destined for v3.8 to your linux-next included branches until after v3.7-rc1 is released. Changes since 201201002: Removed tree: rr New trees: modules and virtio (replacing rr) Conflicts are migrating as trees are merged by Linus. The nfs tree lost its build failure. The ubi tree gained a build failure so I used the version from next-20121002. The mfd tree gained a conflict against Linus' tree. The battery tree gained a conflict against the mfd tree. The xen-two tree lost its build failure. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use git pull to do so as that will try to merge the new linux-next release with the old one. You should use git fetch as mentioned in the FAQ on the wiki (see below). You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc, sparc64 and arm defconfig. These builds also have CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary. Below is a summary of the state of the merge. We are up to 202 trees (counting Linus' and 26 trees of patches pending for Linus' tree), more are welcome (even if they are currently empty). Thanks to those who have contributed, and to those who haven't, please do. Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. There is a wiki covering stuff to do with linux-next at http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel. -- Cheers, Stephen Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (7fe0b14 Merge tag 'spi-3.7' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc) Merging fixes/master (9023a40 Merge tag 'mmc-fixes-for-3.5-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc) Merging kbuild-current/rc-fixes (fe04ddf kbuild: Do not package /boot and /lib in make tar-pkg) Merging arm-current/fixes (7253b85 ARM: 7541/1: Add ARM ERRATA 775420 workaround) Merging m68k-current/for-linus (f82735d m68k: Use PTR_RET rather than if(IS_ERR(...)) + PTR_ERR) Merging powerpc-merge/merge (636802e powerpc: Don't use __put_user() in patch_instruction) Merging sparc/master (1b62ca7 sparc64: Fix return value of Niagara-2 memcpy.) Merging net/master (a0d271c Linux 3.6) Merging sound-current/for-linus (5d037f9 Merge tag 'asoc-3.6' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus) Merging pci-current/for-linus (0ff9514 PCI: Don't print anything while decoding is disabled) Merging wireless/master (a7be50b iwlwifi: don't double free the interrupt in failure path) Merging driver-core.current/driver-core-linus (5698bd7 Linux 3.6-rc6) Merging tty.current/tty-linus (5698bd7 Linux 3.6-rc6) Merging usb.current/usb-linus (0d00dc2 USB: Fix race condition when removing host controllers) Merging staging.current/staging-linus (5698bd7 Linux 3.6-rc6) Merging char-misc.current/char-misc-linus (fea7a08 Linux 3.6-rc3) Merging input-current/for-linus (dde3ada Merge branch 'next' into for-linus) Merging md-current/for-linus (80b4812 md/raid10: fix enough function for detecting if array is failed.) Merging audit-current/for-linus (c158a35 audit: no leading space in audit_log_d_path prefix) Merging crypto-current/master (298b973 crypto: x86/glue_helper - fix storing of new IV in CBC encryption) Merging ide/master (9974e43 ide: fix generic_ide_suspend/resume Oops) Merging dwmw2/master (244dc4e Merge git://git.infradead.org/users/dwmw2/random-2.6) Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to inline functions) Merging irqdomain-current/irqdomain/merge (15e06bf irqdomain: Fix debugfs formatting) Merging devicetree-current/devicetree/merge (4e8383b of: release node fix for of_parse_phandle_with_args) Merging spi-current/spi/merge (d1c185b of/spi: Fix SPI module loading by using proper spi: modalias prefixes.) Merging gpio-current/gpio/merge (96b7064 gpio/tca6424: merge I2C transactions, remove cast) Merging arm/for-next (f537d06 Merge branch 'devel-stable' into for-next) CONFLICT (content):
Re: linux-next: Tree for Oct 3 (mfd/syscon)
On 10/03/2012 12:30 AM, Stephen Rothwell wrote: Hi all, Do not add stuff destined for v3.8 to your linux-next included branches until after v3.7-rc1 is released. Changes since 201201002: on i386: CC drivers/mfd/syscon.o drivers/mfd/syscon.c:94:15: error: variable 'syscon_regmap_config' has initializer but incomplete type drivers/mfd/syscon.c:95:2: error: unknown field 'reg_bits' specified in initializer drivers/mfd/syscon.c:95:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:95:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c:96:2: error: unknown field 'val_bits' specified in initializer drivers/mfd/syscon.c:96:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:96:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c:97:2: error: unknown field 'reg_stride' specified in initializer drivers/mfd/syscon.c:97:2: warning: excess elements in struct initializer drivers/mfd/syscon.c:97:2: warning: (near initialization for 'syscon_regmap_config') drivers/mfd/syscon.c: In function 'syscon_probe': drivers/mfd/syscon.c:124:2: error: invalid use of undefined type 'struct regmap_config' drivers/mfd/syscon.c:125:2: error: implicit declaration of function 'devm_regmap_init_mmio' drivers/mfd/syscon.c:125:17: warning: assignment makes pointer from integer without a cast make[3]: *** [drivers/mfd/syscon.o] Error 1 Full randconfig file is attached. -- ~Randy # # Automatically generated file; DO NOT EDIT. # Linux/i386 3.6.0 Kernel Configuration # # CONFIG_64BIT is not set CONFIG_X86_32=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT=elf32-i386 CONFIG_ARCH_DEFCONFIG=arch/x86/configs/i386_defconfig CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_GPIO=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_ARCH_HAS_CPU_AUTOPROBE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y # CONFIG_ZONE_DMA32 is not set # CONFIG_AUDIT_ARCH is not set CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_32_SMP=y CONFIG_X86_HT=y CONFIG_X86_32_LAZY_GS=y CONFIG_ARCH_HWEIGHT_CFLAGS=-fcall-saved-ecx -fcall-saved-edx CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config CONFIG_HAVE_IRQ_WORK=y CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE= CONFIG_LOCALVERSION= CONFIG_LOCALVERSION_AUTO=y CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set CONFIG_DEFAULT_HOSTNAME=(none) # CONFIG_SWAP is not set CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set CONFIG_FHANDLE=y CONFIG_AUDIT=y # CONFIG_AUDITSYSCALL is not set CONFIG_AUDIT_LOGINUID_IMMUTABLE=y CONFIG_HAVE_GENERIC_HARDIRQS=y # # IRQ subsystem # CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_GENERIC_IRQ_CHIP=y CONFIG_IRQ_DOMAIN=y # CONFIG_IRQ_DOMAIN_DEBUG is not set CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_KTIME_SCALAR=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # # CONFIG_TICK_CPU_ACCOUNTING is not set CONFIG_IRQ_TIME_ACCOUNTING=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_TASKSTATS=y # CONFIG_TASK_DELAY_ACCT is not set # CONFIG_TASK_XACCT is not set # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_PREEMPT_RCU is not set CONFIG_RCU_FANOUT=32 CONFIG_RCU_FANOUT_LEAF=16 # CONFIG_RCU_FANOUT_EXACT is not set # CONFIG_RCU_FAST_NO_HZ is not set # CONFIG_TREE_RCU_TRACE is not set CONFIG_IKCONFIG=y CONFIG_LOG_BUF_SHIFT=17 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y # CONFIG_CGROUPS is not set CONFIG_CHECKPOINT_RESTORE=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y # CONFIG_IPC_NS is not set CONFIG_PID_NS=y # CONFIG_NET_NS is not set # CONFIG_SCHED_AUTOGROUP is not set # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_ANON_INODES=y CONFIG_EXPERT=y CONFIG_UID16=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y
