linux-next: Tree for Jul 16
Hi all,
Changes since 20200715:
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
The net-next tree gained a conflict against the bpf tree.
The block tree gained lost its build failure and runtime problem.
The security tree still had its build failure for which I applied a patch.
The tip tree still had one build failure for which I reverted a commit.
The akpm-current tree gained a conflict against the arm64 tree.
Non-merge commits (relative to Linus' tree): 7574
8303 files changed, 43 insertions(+), 159724 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 htmldocs. 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 324 trees (counting Linus' and 83 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 (e9919e11e219 Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input)
Merging fixes/master (dbf24e30ce2e device_cgroup: Fix RCU list debugging
warning)
Merging kbuild-current/fixes (20b1be595282 kbuild: fix single target builds for
external modules)
Merging arc-current/for-curr (11ba468877bb Linux 5.8-rc5)
Merging arm-current/fixes (3866f217aaa8 ARM: 8977/1: ptrace: Fix mask for thumb
breakpoint hook)
Merging arm-soc-fixes/arm/fixes (5516b2c942dc Merge tag 'amlogic-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic into
arm/fixes)
Merging uniphier-fixes/fixes (48778464bb7d Linux 5.8-rc2)
Merging arm64-fixes/for-next/fixes (7c116db24d94 efi/libstub/arm64: Retain 2MB
kernel Image alignment if !KASLR)
Merging m68k-current/for-linus (3381df095419 m68k: tools: Replace zero-length
array with flexible-array member)
Merging powerpc-fixes/fixes (f0479c4bcbd9 selftests/powerpc: Use proper error
code to check fault address)
Merging s390-fixes/fixes (dd9ce2d6eeae MAINTAINERS: update email address for
Gerald Schaefer)
Merging sparc/master (37719576046b arch/sparc: Replace HTTP links with HTTPS
ones)
Merging fscrypt-current/for-stable (2b4eae95c736 fscrypt: don't evict dirty
inodes after removing key)
Merging net/master (1d61e21852d3 qed: Disable "MFW indication via attention"
SPAM every 5 minutes)
Merging bpf/master (5b801dfb7feb bpf: Fix NULL pointer dereference in
__btf_resolve_helper_id())
Merging ipsec/master (17175d1a27c6 xfrm: esp6: fix encapsulation header offset
computation)
Merging netfilter/master (1e9451cbda45 netfilter: nf_tables: fix nat hook table
deletion)
Merging ipvs/master (eadede5f9362 Merge branch 'hns3-fixes')
Merging wireless-drivers/master (dc7bd30b97aa mt76: mt7615: fix EEPROM buffer
size)
Merging mac80211/master (8ff41cc21714 net: qrtr: Fix an out of bounds read
qrtr_endpoint_post())
Merging rdma-fixes/for-rc (11ba468877bb Linux 5.8-rc5)
Merging sound-current/for-linus (f50a121d2f32 ALSA: hda/realtek: Enable headset
mic of Acer TravelMate B311R-31 with ALC256)
Merging sound-asoc-fixes/for-linus (87b833f69616 Merge remote-tracking branch
'asoc/for-5.8' into asoc-linus)
Merging regmap-fixes/for-linus (516d63dbf222 Merge remote-tracking branch
'regmap/for-5.8' into regmap-linus)
Merging regulator-fixes/for-linus (5a8a6124b209 Merge remote-tracking branch
'regulator/for-5.8' into regulator-linus)
Merging spi-fixes/for-linus (420a94bd692a Merge remote-tracking branch
'spi/for-5.8' into spi-linus)
Merging pci-current/for-linus
linux-next: Tree for Jul 16
Hi all, Please do not add v5.4 material to your linux-next included branches until after v5.3-rc1 has been released. Changes since 20190715: The kbuild tree gained a build failure for which I reverted 4 commits. The pm tree lost its build failure. The rdma tree gained a conflict against the v4l-dvb-next tree. Non-merge commits (relative to Linus' tree): 4992 4742 files changed, 602614 insertions(+), 111348 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 299 trees (counting Linus' and 72 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 (fec88ab0af97 Merge tag 'for-linus-hmm' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma) Merging fixes/master (1e0fd3346b49 MIPS: fix some more fall through errors in arch/mips) Merging kspp-gustavo/for-next/kspp (d93512ef0f0e Makefile: Globally enable fall-through warning) Merging kbuild-current/fixes (964a4eacef67 Merge tag 'dlm-5.3' of git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm) Merging arc-current/for-curr (24a20b0a443f ARC: [plat-hsdk]: Enable AXI DW DMAC in defconfig) CONFLICT (content): Merge conflict in arch/arc/mm/fault.c Merging arm-current/fixes (c5d0e49e8d8f ARM: 8867/1: vdso: pass --be8 to linker if necessary) Merging arm-soc-fixes/arm/fixes (2659dc8d225c Merge tag 'davinci-fixes-for-v5.2-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci into arm/fixes) Merging arm64-fixes/for-next/fixes (aa69fb62bea1 arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly) Merging m68k-current/for-linus (f28a1f16135c m68k: Don't select ARCH_HAS_DMA_PREP_COHERENT for nommu or coldfire) Merging powerpc-fixes/fixes (192f0f8e9db7 Merge tag 'powerpc-5.3-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux) Merging s390-fixes/fixes (9a159190414d s390/unwind: avoid int overflow in outside_of_stack) Merging sparc/master (192f0f8e9db7 Merge tag 'powerpc-5.3-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (f384e62a82ba ISDN: hfcsusb: checking idx of ep configuration) Merging bpf/master (6da193569cbe Merge branch 'bpf-fix-wide-loads-sockaddr') Merging ipsec/master (114a5c324015 Merge tag 'mlx5-fixes-2019-07-11' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux) Merging netfilter/master (1c5ec78272e3 netfilter: nfnetlink: avoid deadlock due to synchronous request_module) Merging ipvs/master (58e8b37069ff Merge branch 'net-phy-dp83867-add-some-fixes') Merging wireless-drivers/master (41a531ffa4c5 rt2x00usb: fix rx queue hang) Merging mac80211/master (d2ce8d6bfcfe nl80211: Fix undefined behavior in bit shift) Merging rdma-fixes/for-rc (4b972a01a7da Linux 5.2-rc6) Merging sound-current/for-linus (2f235d92ac22 ALSA: rme9652: Unneeded variable: "result".) Merging sound-asoc-fixes/for-linus (bd6fe4ae445e Merge branch 'asoc-5.2' into asoc-linus) Merging regmap-fixes/for-linus (ea09b3e21f18 Merge branch 'regmap-5.2' into regmap-linus) Merging regulator-fixes/for-linus (174bc9941d7d Merge branch 'regulator-5.2' into regulator-linus) Merging spi-fixes/for-linus (70b5fa4cc32f Merge branch 'spi-5.2' into spi-linus) Merging pci-current/for-linus (6dbbd053e6ae PCI/P2PDMA: Ignore
linux-next: Tree for Jul 16
Hi all, Changes since 20180713: The arm-soc tree gained a build failure so I used the version from next-20180713. Non-merge commits (relative to Linus' tree): 6029 5901 files changed, 216652 insertions(+), 121372 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 283 trees (counting Linus' and 65 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 pgprbyaZHPlEc.pgp Description: OpenPGP digital signature
linux-next: Tree for Jul 16
Hi all, Changes since 20180713: The arm-soc tree gained a build failure so I used the version from next-20180713. Non-merge commits (relative to Linus' tree): 6029 5901 files changed, 216652 insertions(+), 121372 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 283 trees (counting Linus' and 65 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 pgprbyaZHPlEc.pgp Description: OpenPGP digital signature
linux-next: Tree for Jul 16
Hi all, For those that care: I have stopped signing these messages because vger's mailing list software destroys the signatures and then Google (at least) assumes that they are spam. I could clear sign them instead (if anyone thinks that is worth while). Changes since 20150715: Removed tree: init (it has all been merged) The tip tree lost its build failure. The rcu tree gained a conflict against the tip tree and a build failure for which I applied a merge fix patch. The akpm-current tree gained a conflict against the arm tree and 2 build failures for which I applied fix patches. Non-merge commits (relative to Linus' tree): 2446 2485 files changed, 100730 insertions(+), 34595 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, a multi_v7_defconfig for arm and a native build of tools/perf. 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 223 trees (counting Linus' and 33 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 (97d6e2b636c6 Merge tag 'module-final-v4.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux) Merging fixes/master (c7e9ad7da219 Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip) Merging kbuild-current/rc-fixes (c517d838eb7d Linux 4.0-rc1) Merging arc-current/for-curr (e4140819dadc ARC: signal handling robustify) Merging arm-current/fixes (ab525b473c96 ARM: invalidate L1 before enabling coherency) Merging m68k-current/for-linus (1214c525484c m68k: Use for_each_sg()) Merging metag-fixes/fixes (0164a711c97b metag: Fix ioremap_wc/ioremap_cached build errors) Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5) Merging powerpc-fixes/fixes (bc0195aad0da Linux 4.2-rc2) Merging powerpc-merge-mpe/fixes (bc0195aad0da Linux 4.2-rc2) Merging powerpc-merge-benh/merge (c517d838eb7d Linux 4.0-rc1) Merging sparc/master (4a10a91756ef Merge branch 'upstream' of git://git.infradead.org/users/pcmoore/audit) Merging net/master (bc8c20acaea1 bridge: multicast: treat igmpv3 report with INCLUDE and no sources as a leave) Merging ipsec/master (31a418986a58 xen: netback: read hotplug script once at start of day.) Merging sound-current/for-linus (4d0e677523a9 ALSA: line6: Fix -EBUSY error during active monitoring) Merging pci-current/for-linus (c9ddbac9c891 PCI: Restore PCI_MSIX_FLAGS_BIRMASK definition) Merging wireless-drivers/master (7865598ec24a ath9k_hw: fix device ID check for AR956x) Merging driver-core.current/driver-core-linus (bc0195aad0da Linux 4.2-rc2) Merging tty.current/tty-linus (bc0195aad0da Linux 4.2-rc2) Merging usb.current/usb-linus (51f007e1a1f1 Merge tag 'usb-serial-4.2-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial into usb-linus) Merging usb-gadget-fixes/fixes (b2e2c94b878b usb: gadget: f_midi: fix error recovery path) Merging usb-serial-fixes/usb-linus (d23f47d4927f USB: serial: Destroy serial_minors IDR on module exit) Merging staging.current/staging-linus (d309509f8472 staging: vt6656: check ieee80211_bss_conf bssid not NULL) Merging char-misc.current/char-misc-linus (bc0195aad0da Linux 4.2-rc2) Merging input-current/for-linus (dbf3c370862d Revert "Input: synaptics - allocate 3 slots to keep stability in image sensors") Merging crypto-current/master (030f4e968741 crypto: nx - Fix reentrancy bugs) Merging ide/master (d681f1166919 ide: remove deprecated use of pci api) Merging devicetree-current/devicetree/merge (f76502aa9140 of/dynamic: Fix test for PPC_PSERIES) Merging rr-fixes/fixes (758556bdc1c8 module: Fix load_module()
linux-next: Tree for Jul 16
Hi all, For those that care: I have stopped signing these messages because vger's mailing list software destroys the signatures and then Google (at least) assumes that they are spam. I could clear sign them instead (if anyone thinks that is worth while). Changes since 20150715: Removed tree: init (it has all been merged) The tip tree lost its build failure. The rcu tree gained a conflict against the tip tree and a build failure for which I applied a merge fix patch. The akpm-current tree gained a conflict against the arm tree and 2 build failures for which I applied fix patches. Non-merge commits (relative to Linus' tree): 2446 2485 files changed, 100730 insertions(+), 34595 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, a multi_v7_defconfig for arm and a native build of tools/perf. 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 223 trees (counting Linus' and 33 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 (97d6e2b636c6 Merge tag 'module-final-v4.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux) Merging fixes/master (c7e9ad7da219 Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip) Merging kbuild-current/rc-fixes (c517d838eb7d Linux 4.0-rc1) Merging arc-current/for-curr (e4140819dadc ARC: signal handling robustify) Merging arm-current/fixes (ab525b473c96 ARM: invalidate L1 before enabling coherency) Merging m68k-current/for-linus (1214c525484c m68k: Use for_each_sg()) Merging metag-fixes/fixes (0164a711c97b metag: Fix ioremap_wc/ioremap_cached build errors) Merging mips-fixes/mips-fixes (1795cd9b3a91 Linux 3.16-rc5) Merging powerpc-fixes/fixes (bc0195aad0da Linux 4.2-rc2) Merging powerpc-merge-mpe/fixes (bc0195aad0da Linux 4.2-rc2) Merging powerpc-merge-benh/merge (c517d838eb7d Linux 4.0-rc1) Merging sparc/master (4a10a91756ef Merge branch 'upstream' of git://git.infradead.org/users/pcmoore/audit) Merging net/master (bc8c20acaea1 bridge: multicast: treat igmpv3 report with INCLUDE and no sources as a leave) Merging ipsec/master (31a418986a58 xen: netback: read hotplug script once at start of day.) Merging sound-current/for-linus (4d0e677523a9 ALSA: line6: Fix -EBUSY error during active monitoring) Merging pci-current/for-linus (c9ddbac9c891 PCI: Restore PCI_MSIX_FLAGS_BIRMASK definition) Merging wireless-drivers/master (7865598ec24a ath9k_hw: fix device ID check for AR956x) Merging driver-core.current/driver-core-linus (bc0195aad0da Linux 4.2-rc2) Merging tty.current/tty-linus (bc0195aad0da Linux 4.2-rc2) Merging usb.current/usb-linus (51f007e1a1f1 Merge tag 'usb-serial-4.2-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial into usb-linus) Merging usb-gadget-fixes/fixes (b2e2c94b878b usb: gadget: f_midi: fix error recovery path) Merging usb-serial-fixes/usb-linus (d23f47d4927f USB: serial: Destroy serial_minors IDR on module exit) Merging staging.current/staging-linus (d309509f8472 staging: vt6656: check ieee80211_bss_conf bssid not NULL) Merging char-misc.current/char-misc-linus (bc0195aad0da Linux 4.2-rc2) Merging input-current/for-linus (dbf3c370862d Revert Input: synaptics - allocate 3 slots to keep stability in image sensors) Merging crypto-current/master (030f4e968741 crypto: nx - Fix reentrancy bugs) Merging ide/master (d681f1166919 ide: remove deprecated use of pci api) Merging devicetree-current/devicetree/merge (f76502aa9140 of/dynamic: Fix test for PPC_PSERIES) Merging rr-fixes/fixes (758556bdc1c8 module: Fix load_module() error
Re: linux-next: Tree for Jul 16
On Wed, Jul 16, 2014 at 11:14 PM, Stephen Rothwell wrote: > Hi Nick, > > On Wed, 16 Jul 2014 22:01:35 -0400 Nick Krause wrote: >> >> Absolutely , I am using the latest kernel rc from git. I am using gcc >> 4.8.3 and binutils 2.83.91. > > Then that has nothing to do with me ... I am the linux-next > maintainer. I just happen to use the same build test system as is also > used to test Linus' tree (kisskb). I hope you are looking at the right > result pages for what you are testing. The URL I gave you was for the > linux-next builds, not Linus' tree. > >> In addition I am using the default configurations as you are in less >> I am doing it differently. >> By the way xtensa-defconfig seems to fail because of binutils as I >> discussed this with >> the maintainers and they seemed to have tested it with a newer upstream >> binutils >> then I am using and it succeeded it the linking failures I am seeing with it. > > Maybe we need per architecture minimum tools versions (instead of > current global one). > > -- > Cheers, > Stephen Rothwells...@canb.auug.org.au That seems like a good idea. I am also curious if when there is a build failure in the mainline kernel if we can mail the logs to the maintainers of that arch as if we do it seems to get resolved much faster, usually in a day or two, Cheers Nick -- 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 Jul 16
Hi Nick, On Wed, 16 Jul 2014 22:01:35 -0400 Nick Krause wrote: > > Absolutely , I am using the latest kernel rc from git. I am using gcc > 4.8.3 and binutils 2.83.91. Then that has nothing to do with me ... I am the linux-next maintainer. I just happen to use the same build test system as is also used to test Linus' tree (kisskb). I hope you are looking at the right result pages for what you are testing. The URL I gave you was for the linux-next builds, not Linus' tree. > In addition I am using the default configurations as you are in less > I am doing it differently. > By the way xtensa-defconfig seems to fail because of binutils as I > discussed this with > the maintainers and they seemed to have tested it with a newer upstream > binutils > then I am using and it succeeded it the linking failures I am seeing with it. Maybe we need per architecture minimum tools versions (instead of current global one). -- Cheers, Stephen Rothwells...@canb.auug.org.au signature.asc Description: PGP signature
Re: linux-next: Tree for Jul 16
On Wed, Jul 16, 2014 at 9:47 PM, Stephen Rothwell wrote: > Hi Nick, > > On Wed, 16 Jul 2014 21:16:16 -0400 Nick Krause wrote: >> >> > On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause wrote: >> >> >> >> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell >> >> wrote: >> >> > >> >> > Status of my local build tests will be at >> >> > http://kisskb.ellerman.id.au/linux-next . >> > >> >> I am trying to get the maintainers to clean up still failing builds. >> >> When you get time I wondering >> >> if you can send me a list of still failing builds and warnings of >> >> interest in the kernel that is' >> >> up to date for me to help clean up these outstanding issues with the >> >> maintainers support as needed. >> > >> > See above ... >> >> There seems to be a few that are still succeeding for me that aren't for. >> Would you mind testing some of them again to see if they are succeeding >> with a gcc compiler that is newer then version 4.7. > > Please tell us exactly what you are testing: what kernel version, what > compiler/binutils version. The kernel is meant to be able to be built > with gcc 4.7 (and some earlier) - barring compiler bugs, of course. > > -- > Cheers, > Stephen Rothwells...@canb.auug.org.au Absolutely , I am using the latest kernel rc from git. I am using gcc 4.8.3 and binutils 2.83.91. In addition I am using the default configurations as you are in less I am doing it differently. By the way xtensa-defconfig seems to fail because of binutils as I discussed this with the maintainers and they seemed to have tested it with a newer upstream binutils then I am using and it succeeded it the linking failures I am seeing with it. Cheers Nick -- 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 Jul 16
Hi Nick, On Wed, 16 Jul 2014 21:16:16 -0400 Nick Krause wrote: > > > On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause wrote: > >> > >> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell > >> wrote: > >> > > >> > Status of my local build tests will be at > >> > http://kisskb.ellerman.id.au/linux-next . > > > >> I am trying to get the maintainers to clean up still failing builds. > >> When you get time I wondering > >> if you can send me a list of still failing builds and warnings of > >> interest in the kernel that is' > >> up to date for me to help clean up these outstanding issues with the > >> maintainers support as needed. > > > > See above ... > > There seems to be a few that are still succeeding for me that aren't for. > Would you mind testing some of them again to see if they are succeeding > with a gcc compiler that is newer then version 4.7. Please tell us exactly what you are testing: what kernel version, what compiler/binutils version. The kernel is meant to be able to be built with gcc 4.7 (and some earlier) - barring compiler bugs, of course. -- Cheers, Stephen Rothwells...@canb.auug.org.au signature.asc Description: PGP signature
Re: linux-next: Tree for Jul 16
> > On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause wrote: >> >> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell >> wrote: >> > >> > Status of my local build tests will be at >> > http://kisskb.ellerman.id.au/linux-next . > >> I am trying to get the maintainers to clean up still failing builds. >> When you get time I wondering >> if you can send me a list of still failing builds and warnings of >> interest in the kernel that is' >> up to date for me to help clean up these outstanding issues with the >> maintainers support as needed. > > See above ... > > -- > Cheers, > Stephen Rothwells...@canb.auug.org.au There seems to be a few that are still succeeding for me that aren't for. Would you mind testing some of them again to see if they are succeeding with a gcc compiler that is newer then version 4.7. Cheers Nick -- 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 Jul 16
Hi Nick, [Please trim your replies to just the bit (if any) that you are referring to] On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause wrote: > > On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell > wrote: > > > > Status of my local build tests will be at > > http://kisskb.ellerman.id.au/linux-next . > I am trying to get the maintainers to clean up still failing builds. > When you get time I wondering > if you can send me a list of still failing builds and warnings of > interest in the kernel that is' > up to date for me to help clean up these outstanding issues with the > maintainers support as needed. See above ... -- Cheers, Stephen Rothwells...@canb.auug.org.au signature.asc Description: PGP signature
Re: linux-next: Tree for Jul 16
On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20140715: > > The v4l-dvb tree lost its build failure. > > The wireless-next tree gained a build failure so I used the version > from next-20140715. > > The infiniband tree gained a conflict against the net-next tree. > > The staging tree gained conflict against the net-next and v4l-dvb trees. > > The akpm tree gained a build failure due to an interaction with the > cgroup tree for which I applied a fix patch. > > Non-merge commits (relative to Linus' tree): 5966 > 5609 files changed, 220568 insertions(+), 280729 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 222 trees (counting Linus' and 30 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 > Hey Stephen, I am trying to get the maintainers to clean up still failing builds. When you get time I wondering if you can send me a list of still failing builds and warnings of interest in the kernel that is' up to date for me to help clean up these outstanding issues with the maintainers support as needed. Cheers Nick -- 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 Jul 16
Hi all, Changes since 20140715: The v4l-dvb tree lost its build failure. The wireless-next tree gained a build failure so I used the version from next-20140715. The infiniband tree gained a conflict against the net-next tree. The staging tree gained conflict against the net-next and v4l-dvb trees. The akpm tree gained a build failure due to an interaction with the cgroup tree for which I applied a fix patch. Non-merge commits (relative to Linus' tree): 5966 5609 files changed, 220568 insertions(+), 280729 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 222 trees (counting Linus' and 30 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 (1795cd9b3a91 Linux 3.16-rc5) Merging fixes/master (1795cd9b3a91 Linux 3.16-rc5) Merging kbuild-current/rc-fixes (dd5a6752ae7d firmware: Create directories for external firmware) Merging arc-current/for-curr (89ca3b881987 Linux 3.15-rc4) Merging arm-current/fixes (cda390bb8f0f Merge branch 'kprobes-test-fixes' of git://git.linaro.org/people/tixy/kernel into fixes) Merging m68k-current/for-linus (5bc8c7cdeb6e m68k: Export mach_random_get_entropy to modules) Merging metag-fixes/fixes (ffe6902b66aa asm-generic: remove _STK_LIM_MAX) Merging powerpc-merge/merge (f56029410a13 powerpc/perf: Never program book3s PMCs with values >= 0x8000) Merging sparc/master (894e552cfaa3 Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security) Merging net/master (8f9818af4eae hso: fix deadlock when receiving bursts of data) Merging ipsec/master (a0e5ef53aac8 xfrm: Fix installation of AH IPsec SAs) Merging sound-current/for-linus (4da63c6fc426 ALSA: hda - Fix broken PM due to incomplete i915 initialization) Merging pci-current/for-linus (bf177a1eb6d1 MAINTAINERS: Update mx6 PCI driver maintainer's email) Merging wireless/master (2c4db12ec469 rt2800usb: Don't perform DMA from stack) Merging driver-core.current/driver-core-linus (aff008ad813c platform_get_irq: Revert to platform_get_resource if of_irq_get fails) Merging tty.current/tty-linus (1795cd9b3a91 Linux 3.16-rc5) Merging usb.current/usb-linus (1795cd9b3a91 Linux 3.16-rc5) Merging usb-gadget-fixes/fixes (8035691365b8 usb: musb: dsps: fix the base address for accessing the mode register) Merging usb-serial-fixes/usb-linus (3d28bd840b2d usb: option: Add ID for Telewell TW-LTE 4G v2) Merging staging.current/staging-linus (9359003385a2 Merge tag 'iio-fixes-for-3.16d' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus) Merging char-misc.current/char-misc-linus (1795cd9b3a91 Linux 3.16-rc5) Merging input-current/for-linus (31972f6e517d Input: ti_am335x_tsc - warn about incorrect spelling) Merging md-current/for-linus (d47648fcf061 raid5: avoid finding "discard" stripe) Merging crypto-current/master (e052dbf55461 hwrng: virtio - ensure reads happen after successful probe) Merging ide/master (5b40dd30bbfa ide: Fix SC1200 dependencies) Merging dwmw2/master (5950f0803ca9 pcmcia: remove RPX board stuff) Merging devicetree-current/devicetree/merge (356facff5275 of/platform: Fix of_platform_device_destroy iteration of devices) Merging rr-fixes/fixes (79465d2fd48e module: remove warning about waiting module removal.) Merging mfd-fixes/master (73beb63d290f mfd: rtsx_pcr: Disable interrupts before cancelling delayed works) Merging vfio-fixes/for-linus (239a87020b26 Merge branch 'for-joerg/arm-smmu/fixes' of
linux-next: Tree for Jul 16
Hi all, Changes since 20140715: The v4l-dvb tree lost its build failure. The wireless-next tree gained a build failure so I used the version from next-20140715. The infiniband tree gained a conflict against the net-next tree. The staging tree gained conflict against the net-next and v4l-dvb trees. The akpm tree gained a build failure due to an interaction with the cgroup tree for which I applied a fix patch. Non-merge commits (relative to Linus' tree): 5966 5609 files changed, 220568 insertions(+), 280729 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 222 trees (counting Linus' and 30 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 (1795cd9b3a91 Linux 3.16-rc5) Merging fixes/master (1795cd9b3a91 Linux 3.16-rc5) Merging kbuild-current/rc-fixes (dd5a6752ae7d firmware: Create directories for external firmware) Merging arc-current/for-curr (89ca3b881987 Linux 3.15-rc4) Merging arm-current/fixes (cda390bb8f0f Merge branch 'kprobes-test-fixes' of git://git.linaro.org/people/tixy/kernel into fixes) Merging m68k-current/for-linus (5bc8c7cdeb6e m68k: Export mach_random_get_entropy to modules) Merging metag-fixes/fixes (ffe6902b66aa asm-generic: remove _STK_LIM_MAX) Merging powerpc-merge/merge (f56029410a13 powerpc/perf: Never program book3s PMCs with values = 0x8000) Merging sparc/master (894e552cfaa3 Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security) Merging net/master (8f9818af4eae hso: fix deadlock when receiving bursts of data) Merging ipsec/master (a0e5ef53aac8 xfrm: Fix installation of AH IPsec SAs) Merging sound-current/for-linus (4da63c6fc426 ALSA: hda - Fix broken PM due to incomplete i915 initialization) Merging pci-current/for-linus (bf177a1eb6d1 MAINTAINERS: Update mx6 PCI driver maintainer's email) Merging wireless/master (2c4db12ec469 rt2800usb: Don't perform DMA from stack) Merging driver-core.current/driver-core-linus (aff008ad813c platform_get_irq: Revert to platform_get_resource if of_irq_get fails) Merging tty.current/tty-linus (1795cd9b3a91 Linux 3.16-rc5) Merging usb.current/usb-linus (1795cd9b3a91 Linux 3.16-rc5) Merging usb-gadget-fixes/fixes (8035691365b8 usb: musb: dsps: fix the base address for accessing the mode register) Merging usb-serial-fixes/usb-linus (3d28bd840b2d usb: option: Add ID for Telewell TW-LTE 4G v2) Merging staging.current/staging-linus (9359003385a2 Merge tag 'iio-fixes-for-3.16d' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus) Merging char-misc.current/char-misc-linus (1795cd9b3a91 Linux 3.16-rc5) Merging input-current/for-linus (31972f6e517d Input: ti_am335x_tsc - warn about incorrect spelling) Merging md-current/for-linus (d47648fcf061 raid5: avoid finding discard stripe) Merging crypto-current/master (e052dbf55461 hwrng: virtio - ensure reads happen after successful probe) Merging ide/master (5b40dd30bbfa ide: Fix SC1200 dependencies) Merging dwmw2/master (5950f0803ca9 pcmcia: remove RPX board stuff) Merging devicetree-current/devicetree/merge (356facff5275 of/platform: Fix of_platform_device_destroy iteration of devices) Merging rr-fixes/fixes (79465d2fd48e module: remove warning about waiting module removal.) Merging mfd-fixes/master (73beb63d290f mfd: rtsx_pcr: Disable interrupts before cancelling delayed works) Merging vfio-fixes/for-linus (239a87020b26 Merge branch 'for-joerg/arm-smmu/fixes' of
Re: linux-next: Tree for Jul 16
On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20140715: The v4l-dvb tree lost its build failure. The wireless-next tree gained a build failure so I used the version from next-20140715. The infiniband tree gained a conflict against the net-next tree. The staging tree gained conflict against the net-next and v4l-dvb trees. The akpm tree gained a build failure due to an interaction with the cgroup tree for which I applied a fix patch. Non-merge commits (relative to Linus' tree): 5966 5609 files changed, 220568 insertions(+), 280729 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 222 trees (counting Linus' and 30 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 Hey Stephen, I am trying to get the maintainers to clean up still failing builds. When you get time I wondering if you can send me a list of still failing builds and warnings of interest in the kernel that is' up to date for me to help clean up these outstanding issues with the maintainers support as needed. Cheers Nick -- 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 Jul 16
Hi Nick, [Please trim your replies to just the bit (if any) that you are referring to] On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause xerofo...@gmail.com wrote: On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . I am trying to get the maintainers to clean up still failing builds. When you get time I wondering if you can send me a list of still failing builds and warnings of interest in the kernel that is' up to date for me to help clean up these outstanding issues with the maintainers support as needed. See above ... -- Cheers, Stephen Rothwells...@canb.auug.org.au signature.asc Description: PGP signature
Re: linux-next: Tree for Jul 16
On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause xerofo...@gmail.com wrote: On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . I am trying to get the maintainers to clean up still failing builds. When you get time I wondering if you can send me a list of still failing builds and warnings of interest in the kernel that is' up to date for me to help clean up these outstanding issues with the maintainers support as needed. See above ... -- Cheers, Stephen Rothwells...@canb.auug.org.au There seems to be a few that are still succeeding for me that aren't for. Would you mind testing some of them again to see if they are succeeding with a gcc compiler that is newer then version 4.7. Cheers Nick -- 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 Jul 16
Hi Nick, On Wed, 16 Jul 2014 21:16:16 -0400 Nick Krause xerofo...@gmail.com wrote: On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause xerofo...@gmail.com wrote: On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . I am trying to get the maintainers to clean up still failing builds. When you get time I wondering if you can send me a list of still failing builds and warnings of interest in the kernel that is' up to date for me to help clean up these outstanding issues with the maintainers support as needed. See above ... There seems to be a few that are still succeeding for me that aren't for. Would you mind testing some of them again to see if they are succeeding with a gcc compiler that is newer then version 4.7. Please tell us exactly what you are testing: what kernel version, what compiler/binutils version. The kernel is meant to be able to be built with gcc 4.7 (and some earlier) - barring compiler bugs, of course. -- Cheers, Stephen Rothwells...@canb.auug.org.au signature.asc Description: PGP signature
Re: linux-next: Tree for Jul 16
On Wed, Jul 16, 2014 at 9:47 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Nick, On Wed, 16 Jul 2014 21:16:16 -0400 Nick Krause xerofo...@gmail.com wrote: On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause xerofo...@gmail.com wrote: On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . I am trying to get the maintainers to clean up still failing builds. When you get time I wondering if you can send me a list of still failing builds and warnings of interest in the kernel that is' up to date for me to help clean up these outstanding issues with the maintainers support as needed. See above ... There seems to be a few that are still succeeding for me that aren't for. Would you mind testing some of them again to see if they are succeeding with a gcc compiler that is newer then version 4.7. Please tell us exactly what you are testing: what kernel version, what compiler/binutils version. The kernel is meant to be able to be built with gcc 4.7 (and some earlier) - barring compiler bugs, of course. -- Cheers, Stephen Rothwells...@canb.auug.org.au Absolutely , I am using the latest kernel rc from git. I am using gcc 4.8.3 and binutils 2.83.91. In addition I am using the default configurations as you are in less I am doing it differently. By the way xtensa-defconfig seems to fail because of binutils as I discussed this with the maintainers and they seemed to have tested it with a newer upstream binutils then I am using and it succeeded it the linking failures I am seeing with it. Cheers Nick -- 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 Jul 16
Hi Nick, On Wed, 16 Jul 2014 22:01:35 -0400 Nick Krause xerofo...@gmail.com wrote: Absolutely , I am using the latest kernel rc from git. I am using gcc 4.8.3 and binutils 2.83.91. Then that has nothing to do with me ... I am the linux-next maintainer. I just happen to use the same build test system as is also used to test Linus' tree (kisskb). I hope you are looking at the right result pages for what you are testing. The URL I gave you was for the linux-next builds, not Linus' tree. In addition I am using the default configurations as you are in less I am doing it differently. By the way xtensa-defconfig seems to fail because of binutils as I discussed this with the maintainers and they seemed to have tested it with a newer upstream binutils then I am using and it succeeded it the linking failures I am seeing with it. Maybe we need per architecture minimum tools versions (instead of current global one). -- Cheers, Stephen Rothwells...@canb.auug.org.au signature.asc Description: PGP signature
Re: linux-next: Tree for Jul 16
On Wed, Jul 16, 2014 at 11:14 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Nick, On Wed, 16 Jul 2014 22:01:35 -0400 Nick Krause xerofo...@gmail.com wrote: Absolutely , I am using the latest kernel rc from git. I am using gcc 4.8.3 and binutils 2.83.91. Then that has nothing to do with me ... I am the linux-next maintainer. I just happen to use the same build test system as is also used to test Linus' tree (kisskb). I hope you are looking at the right result pages for what you are testing. The URL I gave you was for the linux-next builds, not Linus' tree. In addition I am using the default configurations as you are in less I am doing it differently. By the way xtensa-defconfig seems to fail because of binutils as I discussed this with the maintainers and they seemed to have tested it with a newer upstream binutils then I am using and it succeeded it the linking failures I am seeing with it. Maybe we need per architecture minimum tools versions (instead of current global one). -- Cheers, Stephen Rothwells...@canb.auug.org.au That seems like a good idea. I am also curious if when there is a build failure in the mainline kernel if we can mail the logs to the maintainers of that arch as if we do it seems to get resolved much faster, usually in a day or two, Cheers Nick -- 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 Jul 16
Hi all, Changes since 20130712: New tree: ptr-ret Removed tree: cpuidle (at maintainers request) The drm-intel tree gained a conflict against the drm-intel-fixes tree. The sound-asoc tree gained a build failure so I used the version from next-20130715. The akpm tree gained conflicts against the ext4 tree. The cpuinit tree gained a conflict against the hwmon-staging tree and lost a patch that turned up elsewhere. 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 230 trees (counting Linus' and 33 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 (47188d3 Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4) Merging fixes/master (8177a9d lseek(fd, n, SEEK_END) does *not* go to eof - n) Merging kbuild-current/rc-fixes (42a0940 Merge branch 'yem-kconfig-rc-fixes' of git://gitorious.org/linux-kconfig/linux-kconfig into kbuild/rc-fixes) Merging arc-current/for-curr (6d128e1 Revert "Makefile: Fix install error with make -j option") Merging arm-current/fixes (cbbe6f8 ARM: 7778/1: smp_twd: twd_update_frequency need be run on all online CPUs) Merging m68k-current/for-linus (ad81f05 Linux 3.11-rc1) Merging metag-fixes/fixes (d903bca metag: checksum.h: fix carry in csum_tcpudp_nofold) Merging powerpc-merge/merge (ea461ab powerpc/eeh: Fix fetching bus for single-dev-PE) Merging sparc/master (6d128e1 Revert "Makefile: Fix install error with make -j option") Merging net/master (63345b4 Merge branch 'for_linus' of git://cavan.codon.org.uk/platform-drivers-x86) Merging ipsec/master (01cb71d net_sched: restore "overhead xxx" handling) Merging sound-current/for-linus (86f0b5b staging: line6: Fix unlocked snd_pcm_stop() call) Merging pci-current/for-linus (65694c5 x86/PCI: Map PCI setup data with ioremap() so it can be in highmem) Merging wireless/master (53e5946 ath9k_htc: fix data race between request_firmware_nowait() callback and suspend()) Merging driver-core.current/driver-core-linus (ad81f05 Linux 3.11-rc1) Merging tty.current/tty-linus (ad81f05 Linux 3.11-rc1) Merging usb.current/usb-linus (ad81f05 Linux 3.11-rc1) Merging staging.current/staging-linus (ad81f05 Linux 3.11-rc1) Merging char-misc.current/char-misc-linus (ad81f05 Linux 3.11-rc1) Merging input-current/for-linus (88ce3c3 Merge branch 'next' into for-linus) Merging md-current/for-linus (1376512 md/raid10: fix bug which causes all RAID10 reshapes to move no data.) Merging audit-current/for-linus (c158a35 audit: no leading space in audit_log_d_path prefix) Merging crypto-current/master (9c23b7d crypto: caam - Fixed the memory out of bound overwrite issue) Merging ide/master (6d128e1 Revert "Makefile: Fix install error with make -j option") Merging dwmw2/master (5950f08 pcmcia: remove RPX board stuff) Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to inline functions) Merging irqdomain-current/irqdomain/merge (d94ea3f irqchip: Return -EPERM for reserved IRQs) Merging devicetree-current/devicetree/merge (706b78f dtc: ensure #line directives don't consume data from the next line) Merging spi-current/spi/merge (0d2d0cc spi/davinci: fix module build error) Merging
linux-next: Tree for Jul 16
Hi all, Changes since 20130712: New tree: ptr-ret Removed tree: cpuidle (at maintainers request) The drm-intel tree gained a conflict against the drm-intel-fixes tree. The sound-asoc tree gained a build failure so I used the version from next-20130715. The akpm tree gained conflicts against the ext4 tree. The cpuinit tree gained a conflict against the hwmon-staging tree and lost a patch that turned up elsewhere. 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 230 trees (counting Linus' and 33 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 (47188d3 Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4) Merging fixes/master (8177a9d lseek(fd, n, SEEK_END) does *not* go to eof - n) Merging kbuild-current/rc-fixes (42a0940 Merge branch 'yem-kconfig-rc-fixes' of git://gitorious.org/linux-kconfig/linux-kconfig into kbuild/rc-fixes) Merging arc-current/for-curr (6d128e1 Revert Makefile: Fix install error with make -j option) Merging arm-current/fixes (cbbe6f8 ARM: 7778/1: smp_twd: twd_update_frequency need be run on all online CPUs) Merging m68k-current/for-linus (ad81f05 Linux 3.11-rc1) Merging metag-fixes/fixes (d903bca metag: checksum.h: fix carry in csum_tcpudp_nofold) Merging powerpc-merge/merge (ea461ab powerpc/eeh: Fix fetching bus for single-dev-PE) Merging sparc/master (6d128e1 Revert Makefile: Fix install error with make -j option) Merging net/master (63345b4 Merge branch 'for_linus' of git://cavan.codon.org.uk/platform-drivers-x86) Merging ipsec/master (01cb71d net_sched: restore overhead xxx handling) Merging sound-current/for-linus (86f0b5b staging: line6: Fix unlocked snd_pcm_stop() call) Merging pci-current/for-linus (65694c5 x86/PCI: Map PCI setup data with ioremap() so it can be in highmem) Merging wireless/master (53e5946 ath9k_htc: fix data race between request_firmware_nowait() callback and suspend()) Merging driver-core.current/driver-core-linus (ad81f05 Linux 3.11-rc1) Merging tty.current/tty-linus (ad81f05 Linux 3.11-rc1) Merging usb.current/usb-linus (ad81f05 Linux 3.11-rc1) Merging staging.current/staging-linus (ad81f05 Linux 3.11-rc1) Merging char-misc.current/char-misc-linus (ad81f05 Linux 3.11-rc1) Merging input-current/for-linus (88ce3c3 Merge branch 'next' into for-linus) Merging md-current/for-linus (1376512 md/raid10: fix bug which causes all RAID10 reshapes to move no data.) Merging audit-current/for-linus (c158a35 audit: no leading space in audit_log_d_path prefix) Merging crypto-current/master (9c23b7d crypto: caam - Fixed the memory out of bound overwrite issue) Merging ide/master (6d128e1 Revert Makefile: Fix install error with make -j option) Merging dwmw2/master (5950f08 pcmcia: remove RPX board stuff) Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to inline functions) Merging irqdomain-current/irqdomain/merge (d94ea3f irqchip: Return -EPERM for reserved IRQs) Merging devicetree-current/devicetree/merge (706b78f dtc: ensure #line directives don't consume data from the next line) Merging spi-current/spi/merge (0d2d0cc spi/davinci: fix module build error) Merging gpio-current/gpio/merge
