Re: linux-next: Tree for Feb 13 (drivers/spmi/spmi-pmic-arb.c)
On Wed, Feb 13, 2019 at 01:12:08PM -0800, Randy Dunlap wrote: > On 2/13/19 10:31 AM, Brian Masney wrote: > > On Wed, Feb 13, 2019 at 06:18:17PM +0100, Marc Gonzalez wrote: > >> On 13/02/2019 17:47, Randy Dunlap wrote: > >> > >>> seen on i386: > >>> > >>> when CONFIG_IRQ_DOMAIN_HIERARCHY is not enabled: > >>> > >>> ../drivers/spmi/spmi-pmic-arb.c:1154:2: error: unknown field ‘activate’ > >>> specified in initializer > >>> .activate = qpnpint_irq_domain_activate, > >>> ^ > >>> ../drivers/spmi/spmi-pmic-arb.c:1154:2: warning: initialization from > >>> incompatible pointer type [enabled by default] > >>> ../drivers/spmi/spmi-pmic-arb.c:1154:2: warning: (near initialization for > >>> ‘pmic_arb_irq_domain_ops.match’) [enabled by default] > >>> ../drivers/spmi/spmi-pmic-arb.c:1155:2: error: unknown field ‘alloc’ > >>> specified in initializer > >>> .alloc = qpnpint_irq_domain_alloc, > >>> ^ > >>> ../drivers/spmi/spmi-pmic-arb.c:1155:2: warning: initialization from > >>> incompatible pointer type [enabled by default] > >>> ../drivers/spmi/spmi-pmic-arb.c:1155:2: warning: (near initialization for > >>> ‘pmic_arb_irq_domain_ops.select’) [enabled by default] > >>> ../drivers/spmi/spmi-pmic-arb.c:1156:2: error: unknown field ‘free’ > >>> specified in initializer > >>> .free = irq_domain_free_irqs_common, > >>> ^ > >>> ../drivers/spmi/spmi-pmic-arb.c:1156:10: error: > >>> ‘irq_domain_free_irqs_common’ undeclared here (not in a function) > >>> .free = irq_domain_free_irqs_common, > >>> ^ > >>> ../drivers/spmi/spmi-pmic-arb.c:1157:2: error: unknown field ‘translate’ > >>> specified in initializer > >>> .translate = qpnpint_irq_domain_translate, > >>> ^ > >>> ../drivers/spmi/spmi-pmic-arb.c:1157:2: warning: initialization from > >>> incompatible pointer type [enabled by default] > >>> ../drivers/spmi/spmi-pmic-arb.c:1157:2: warning: (near initialization for > >>> ‘pmic_arb_irq_domain_ops.unmap’) [enabled by default] > > > > drivers/pinctrl/qcom/Kconfig already has this in linux-next: > > > > config PINCTRL_QCOM_SPMI_PMIC > >tristate "Qualcomm SPMI PMIC pin controller driver" > >... > >select IRQ_DOMAIN_HIERARCHY > > > > Am I missing something else? > > That kconfig symbol is not set/enabled. > However, SPMI_MSM_PMIC_ARB=m and that is where the build error happens. > > I am attaching the full randconfig file. Ohh, I see. I should have looked closer. I initially assumed it was the spmi-gpio driver. I'll send out a fix in a little bit. Thanks, Brian
Re: linux-next: Tree for Feb 13 (drivers/spmi/spmi-pmic-arb.c)
On Wed, Feb 13, 2019 at 06:18:17PM +0100, Marc Gonzalez wrote: > On 13/02/2019 17:47, Randy Dunlap wrote: > > > seen on i386: > > > > when CONFIG_IRQ_DOMAIN_HIERARCHY is not enabled: > > > > ../drivers/spmi/spmi-pmic-arb.c:1154:2: error: unknown field ‘activate’ > > specified in initializer > > .activate = qpnpint_irq_domain_activate, > > ^ > > ../drivers/spmi/spmi-pmic-arb.c:1154:2: warning: initialization from > > incompatible pointer type [enabled by default] > > ../drivers/spmi/spmi-pmic-arb.c:1154:2: warning: (near initialization for > > ‘pmic_arb_irq_domain_ops.match’) [enabled by default] > > ../drivers/spmi/spmi-pmic-arb.c:1155:2: error: unknown field ‘alloc’ > > specified in initializer > > .alloc = qpnpint_irq_domain_alloc, > > ^ > > ../drivers/spmi/spmi-pmic-arb.c:1155:2: warning: initialization from > > incompatible pointer type [enabled by default] > > ../drivers/spmi/spmi-pmic-arb.c:1155:2: warning: (near initialization for > > ‘pmic_arb_irq_domain_ops.select’) [enabled by default] > > ../drivers/spmi/spmi-pmic-arb.c:1156:2: error: unknown field ‘free’ > > specified in initializer > > .free = irq_domain_free_irqs_common, > > ^ > > ../drivers/spmi/spmi-pmic-arb.c:1156:10: error: > > ‘irq_domain_free_irqs_common’ undeclared here (not in a function) > > .free = irq_domain_free_irqs_common, > > ^ > > ../drivers/spmi/spmi-pmic-arb.c:1157:2: error: unknown field ‘translate’ > > specified in initializer > > .translate = qpnpint_irq_domain_translate, > > ^ > > ../drivers/spmi/spmi-pmic-arb.c:1157:2: warning: initialization from > > incompatible pointer type [enabled by default] > > ../drivers/spmi/spmi-pmic-arb.c:1157:2: warning: (near initialization for > > ‘pmic_arb_irq_domain_ops.unmap’) [enabled by default] drivers/pinctrl/qcom/Kconfig already has this in linux-next: config PINCTRL_QCOM_SPMI_PMIC tristate "Qualcomm SPMI PMIC pin controller driver" ... select IRQ_DOMAIN_HIERARCHY Am I missing something else? Brian
Re: linux-next: Tree for Feb 13 (drivers/spmi/spmi-pmic-arb.c)
On 13/02/2019 17:47, Randy Dunlap wrote: > seen on i386: > > when CONFIG_IRQ_DOMAIN_HIERARCHY is not enabled: > > ../drivers/spmi/spmi-pmic-arb.c:1154:2: error: unknown field ‘activate’ > specified in initializer > .activate = qpnpint_irq_domain_activate, > ^ > ../drivers/spmi/spmi-pmic-arb.c:1154:2: warning: initialization from > incompatible pointer type [enabled by default] > ../drivers/spmi/spmi-pmic-arb.c:1154:2: warning: (near initialization for > ‘pmic_arb_irq_domain_ops.match’) [enabled by default] > ../drivers/spmi/spmi-pmic-arb.c:1155:2: error: unknown field ‘alloc’ > specified in initializer > .alloc = qpnpint_irq_domain_alloc, > ^ > ../drivers/spmi/spmi-pmic-arb.c:1155:2: warning: initialization from > incompatible pointer type [enabled by default] > ../drivers/spmi/spmi-pmic-arb.c:1155:2: warning: (near initialization for > ‘pmic_arb_irq_domain_ops.select’) [enabled by default] > ../drivers/spmi/spmi-pmic-arb.c:1156:2: error: unknown field ‘free’ specified > in initializer > .free = irq_domain_free_irqs_common, > ^ > ../drivers/spmi/spmi-pmic-arb.c:1156:10: error: ‘irq_domain_free_irqs_common’ > undeclared here (not in a function) > .free = irq_domain_free_irqs_common, > ^ > ../drivers/spmi/spmi-pmic-arb.c:1157:2: error: unknown field ‘translate’ > specified in initializer > .translate = qpnpint_irq_domain_translate, > ^ > ../drivers/spmi/spmi-pmic-arb.c:1157:2: warning: initialization from > incompatible pointer type [enabled by default] > ../drivers/spmi/spmi-pmic-arb.c:1157:2: warning: (near initialization for > ‘pmic_arb_irq_domain_ops.unmap’) [enabled by default]
Re: linux-next: Tree for Feb 13 (drivers/spmi/spmi-pmic-arb.c)
On 2/12/19 11:39 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20190212: > seen on i386: when CONFIG_IRQ_DOMAIN_HIERARCHY is not enabled: ../drivers/spmi/spmi-pmic-arb.c:1154:2: error: unknown field ‘activate’ specified in initializer .activate = qpnpint_irq_domain_activate, ^ ../drivers/spmi/spmi-pmic-arb.c:1154:2: warning: initialization from incompatible pointer type [enabled by default] ../drivers/spmi/spmi-pmic-arb.c:1154:2: warning: (near initialization for ‘pmic_arb_irq_domain_ops.match’) [enabled by default] ../drivers/spmi/spmi-pmic-arb.c:1155:2: error: unknown field ‘alloc’ specified in initializer .alloc = qpnpint_irq_domain_alloc, ^ ../drivers/spmi/spmi-pmic-arb.c:1155:2: warning: initialization from incompatible pointer type [enabled by default] ../drivers/spmi/spmi-pmic-arb.c:1155:2: warning: (near initialization for ‘pmic_arb_irq_domain_ops.select’) [enabled by default] ../drivers/spmi/spmi-pmic-arb.c:1156:2: error: unknown field ‘free’ specified in initializer .free = irq_domain_free_irqs_common, ^ ../drivers/spmi/spmi-pmic-arb.c:1156:10: error: ‘irq_domain_free_irqs_common’ undeclared here (not in a function) .free = irq_domain_free_irqs_common, ^ ../drivers/spmi/spmi-pmic-arb.c:1157:2: error: unknown field ‘translate’ specified in initializer .translate = qpnpint_irq_domain_translate, ^ ../drivers/spmi/spmi-pmic-arb.c:1157:2: warning: initialization from incompatible pointer type [enabled by default] ../drivers/spmi/spmi-pmic-arb.c:1157:2: warning: (near initialization for ‘pmic_arb_irq_domain_ops.unmap’) [enabled by default] -- ~Randy
linux-next: Tree for Feb 13
Hi all, Changes since 20190212: The net-next tree gained a conflict against the net tree. The netfilter-next tree gained a build failure so I reverted a commit. The tip tree gained conflicts against the block tree. The vhost tree gained a conflict against the swiotlb tree. The akpm-current tree gained a conflict against the kspp tree and a build failure due to an interaction with the block tree for which I applied a merge fix patch. The akpm gained a conflict against with the tip tree. Non-merge commits (relative to Linus' tree): 7421 7866 files changed, 306843 insertions(+), 191459 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 296 trees (counting Linus' and 69 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 (aa0c38cf39de Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal) Merging fixes/master (0dd62c042779 x86/syscalls: Mark expected switch fall-throughs) Merging kbuild-current/fixes (6db2983cd806 kallsyms: Handle too long symbols in kallsyms.c) Merging arc-current/for-curr (7e9246a982a6 ARCv2: support manual regfile save on interrupts) Merging arm-current/fixes (fc67e6f120a3 ARM: 8835/1: dma-mapping: Clear DMA ops on teardown) Merging arm64-fixes/for-next/fixes (ea5736805190 arm64: kexec_file: handle empty command-line) Merging m68k-current/for-linus (bed1369f5190 m68k: Fix memblock-related crashes) Merging powerpc-fixes/fixes (5a3840a470c4 powerpc/papr_scm: Use the correct bind address) Merging sparc/master (b71acb0e3721 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (2fdeee254923 team: avoid complex list operations in team_nl_cmd_options_set()) Merging bpf/master (1e405c1a3f66 xsk: do not remove umem from netdevice on fall-back to copy-mode) Merging ipsec/master (fc2d5cfdcfe2 af_key: unconditionally clone on broadcast) Merging netfilter/master (8d29d16d2134 netfilter: compat: initialize all fields in xt_init) Merging ipvs/master (b2e3d68d1251 netfilter: nft_compat: destroy function must not have side effects) Merging wireless-drivers/master (d04ca383860b mt76x0u: fix suspend/resume) Merging mac80211/master (6157ca0d6bfe mac80211: Fix Tx aggregation session tear down with ITXQs) Merging rdma-fixes/for-rc (48396e80fb65 RDMA/srp: Rework SCSI device reset handling) Merging sound-current/for-linus (00a399cad1a0 ALSA: pcm: Revert capture stream behavior change in blocking mode) Merging sound-asoc-fixes/for-linus (476e1f03e36e Merge branch 'asoc-5.0' into asoc-linus) Merging regmap-fixes/for-linus (f17b5f06cb92 Linux 5.0-rc4) Merging regulator-fixes/for-linus (e03ae9fb9107 Merge branch 'regulator-5.0' into regulator-linus) Merging spi-fixes/for-linus (5ff2531354af Merge branch 'spi-5.0' into spi-linus) Merging pci-current/for-linus (f57a98e1b713 PCI: Work around Synopsys duplicate Device ID (HAPS USB3, NXP i.MX)) Merging driver-core.current/driver-core-linus (d13937116f1e Linux 5.0-rc6) Merging tty.current/tty-linus (d13937116f1e Linux 5.0-rc6) Merging usb.current/usb-linus (d13937116f1e Linux 5.0-rc6) Merging usb-gadget-fixes/fixes (a53469a68eb8 usb: phy: am335x: fix race condition in _probe) Merging
Re: linux-next: Tree for Feb 13 (i386: apm_32.c)
On 02/12/2018 08:15 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20180212: > > Non-merge commits (relative to Linus' tree): 963 > 1297 files changed, 63627 insertions(+), 31515 deletions(-) > > on i386: arch/x86/kernel/apm_32.o: In function `apm_init': apm_32.c:(.init.text+0x47a): undefined reference to `cpuidle_poll_state_init' drivers/cpuidle/ is not being built: # CONFIG_CPU_IDLE is not set CONFIG_ARCH_HAS_CPU_RELAX=y obj-$(CONFIG_CPU_IDLE) += cpuidle/ -- ~Randy
Re: linux-next: Tree for Feb 13 (i386: apm_32.c)
On 02/12/2018 08:15 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20180212: > > Non-merge commits (relative to Linus' tree): 963 > 1297 files changed, 63627 insertions(+), 31515 deletions(-) > > on i386: arch/x86/kernel/apm_32.o: In function `apm_init': apm_32.c:(.init.text+0x47a): undefined reference to `cpuidle_poll_state_init' drivers/cpuidle/ is not being built: # CONFIG_CPU_IDLE is not set CONFIG_ARCH_HAS_CPU_RELAX=y obj-$(CONFIG_CPU_IDLE) += cpuidle/ -- ~Randy
linux-next: Tree for Feb 13
Hi all, Changes since 20180212: Non-merge commits (relative to Linus' tree): 963 1297 files changed, 63627 insertions(+), 31515 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 256 trees (counting Linus' and 44 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 (178e834c47b0 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging fixes/master (7928b2cbe55b Linux 4.16-rc1) Merging kbuild-current/fixes (36c1681678b5 genksyms: drop *.hash.c from .gitignore) Merging arc-current/for-curr (053823335956 arc: dts: use 'atmel' as manufacturer for at24 in axs10x_mb) Merging arm-current/fixes (091f02483df7 ARM: net: bpf: clarify tail_call index) Merging m68k-current/for-linus (2334b1ac1235 MAINTAINERS: Add NuBus subsystem entry) Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups) Merging powerpc-fixes/fixes (4dd5f8a99e79 powerpc/mm/radix: Split linear mapping on hot-unplug) Merging sparc/master (aebb48f5e465 sparc64: fix typo in CONFIG_CRYPTO_DES_SPARC64 => CONFIG_CRYPTO_CAMELLIA_SPARC64) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (07a2e1cf3981 net: cavium: fix NULL pointer dereference in cavium_ptp_put) Merging bpf/master (1b12580af1d0 bridge: check brport attr show in brport_show) Merging ipsec/master (545d8ae7afff xfrm: fix boolean assignment in xfrm_get_type_offload) Merging netfilter/master (fd2c19b2a28b netfilter: x_tables: remove size check) Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook mask only if set) Merging wireless-drivers/master (7ac8ff95f48c mvpp2: fix multicast address filter) Merging mac80211/master (c4de37ee2b55 mac80211: mesh: fix wrong mesh TTL offset calculation) Merging rdma-fixes/for-rc (7928b2cbe55b Linux 4.16-rc1) Merging sound-current/for-linus (1dcb1859dd67 Merge branch 'topic/fixes' into for-linus) Merging pci-current/for-linus (7928b2cbe55b Linux 4.16-rc1) Merging driver-core.current/driver-core-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging tty.current/tty-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging usb.current/usb-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging usb-gadget-fixes/fixes (b2cd1df66037 Linux 4.15-rc7) Merging usb-serial-fixes/usb-linus (d14ac576d10f USB: serial: cp210x: add new device ID ELV ALC 8xxx) Merging usb-chipidea-fixes/ci-for-usb-stable (964728f9f407 USB: chipidea: msm: fix ulpi-node lookup) Merging phy/fixes (7928b2cbe55b Linux 4.16-rc1) Merging staging.current/staging-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging char-misc.current/char-misc-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging input-current/for-linus (ea4f7bd2aca9 Input: matrix_keypad - fix race when disabling interrupts) Merging crypto-current/master (2e7d1d61ea6c crypto: sun4i_ss_prng - convert lock to _bh in sun4i_ss_prng_generate) Merging ide/master (8e44e6600caa Merge branch 'KASAN-read_word_at_a_time') Merging vfio-fixes/for-linus (563b5cbe334e iommu/arm-smmu-v3: Cope with duplicated Stream IDs) Merging kselftest-fixes/fixes
linux-next: Tree for Feb 13
Hi all, Changes since 20180212: Non-merge commits (relative to Linus' tree): 963 1297 files changed, 63627 insertions(+), 31515 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 256 trees (counting Linus' and 44 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 (178e834c47b0 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging fixes/master (7928b2cbe55b Linux 4.16-rc1) Merging kbuild-current/fixes (36c1681678b5 genksyms: drop *.hash.c from .gitignore) Merging arc-current/for-curr (053823335956 arc: dts: use 'atmel' as manufacturer for at24 in axs10x_mb) Merging arm-current/fixes (091f02483df7 ARM: net: bpf: clarify tail_call index) Merging m68k-current/for-linus (2334b1ac1235 MAINTAINERS: Add NuBus subsystem entry) Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups) Merging powerpc-fixes/fixes (4dd5f8a99e79 powerpc/mm/radix: Split linear mapping on hot-unplug) Merging sparc/master (aebb48f5e465 sparc64: fix typo in CONFIG_CRYPTO_DES_SPARC64 => CONFIG_CRYPTO_CAMELLIA_SPARC64) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (07a2e1cf3981 net: cavium: fix NULL pointer dereference in cavium_ptp_put) Merging bpf/master (1b12580af1d0 bridge: check brport attr show in brport_show) Merging ipsec/master (545d8ae7afff xfrm: fix boolean assignment in xfrm_get_type_offload) Merging netfilter/master (fd2c19b2a28b netfilter: x_tables: remove size check) Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook mask only if set) Merging wireless-drivers/master (7ac8ff95f48c mvpp2: fix multicast address filter) Merging mac80211/master (c4de37ee2b55 mac80211: mesh: fix wrong mesh TTL offset calculation) Merging rdma-fixes/for-rc (7928b2cbe55b Linux 4.16-rc1) Merging sound-current/for-linus (1dcb1859dd67 Merge branch 'topic/fixes' into for-linus) Merging pci-current/for-linus (7928b2cbe55b Linux 4.16-rc1) Merging driver-core.current/driver-core-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging tty.current/tty-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging usb.current/usb-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging usb-gadget-fixes/fixes (b2cd1df66037 Linux 4.15-rc7) Merging usb-serial-fixes/usb-linus (d14ac576d10f USB: serial: cp210x: add new device ID ELV ALC 8xxx) Merging usb-chipidea-fixes/ci-for-usb-stable (964728f9f407 USB: chipidea: msm: fix ulpi-node lookup) Merging phy/fixes (7928b2cbe55b Linux 4.16-rc1) Merging staging.current/staging-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging char-misc.current/char-misc-linus (f1517df8701c Merge tag 'nfsd-4.16' of git://linux-nfs.org/~bfields/linux) Merging input-current/for-linus (ea4f7bd2aca9 Input: matrix_keypad - fix race when disabling interrupts) Merging crypto-current/master (2e7d1d61ea6c crypto: sun4i_ss_prng - convert lock to _bh in sun4i_ss_prng_generate) Merging ide/master (8e44e6600caa Merge branch 'KASAN-read_word_at_a_time') Merging vfio-fixes/for-linus (563b5cbe334e iommu/arm-smmu-v3: Cope with duplicated Stream IDs) Merging kselftest-fixes/fixes
linux-next: Tree for Feb 13
Hi all, Changes since 20170210: The ipsec-next tree gained a conflict against the net-next tree. The rdma-leon gained a conflict against Linus' tree. The l2mtd-tree lost its build failure. Non-merge commits (relative to Linus' tree): 8646 9682 files changed, 388711 insertions(+), 182504 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 and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 256 trees (counting Linus' and 37 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 (1ce42845f987 Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip) Merging fixes/master (30066ce675d3 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging kbuild-current/rc-fixes (c7858bf16c0b asm-prototypes: Clear any CPP defines before declaring the functions) Merging arc-current/for-curr (8ba605b607b7 ARC: [plat-*] ARC_HAS_COH_CACHES no longer relevant) Merging arm-current/fixes (228dbbfb5d77 ARM: 8643/3: arm/ptrace: Preserve previous registers for short regset write) Merging m68k-current/for-linus (ad595b77c4a8 m68k/atari: Use seq_puts() in atari_get_hardware_list()) Merging metag-fixes/fixes (35d04077ad96 metag: Only define atomic_dec_if_positive conditionally) Merging powerpc-fixes/fixes (f83e6862047e powerpc/powernv: Properly set "host-ipi" on IPIs) Merging sparc/master (f9a42e0d58cf Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc) Merging fscrypt-current/for-stable (42d97eb0ade3 fscrypt: fix renaming and linking special files) Merging net/master (e722af639194 ibmvnic: Call napi_disable instead of napi_enable in failure path) Merging ipsec/master (c28a45cb xfrm: policy: init locks early) Merging netfilter/master (f95d7a46bc57 netfilter: ctnetlink: Fix regression in CTA_HELP processing) Merging ipvs/master (045169816b31 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging wireless-drivers/master (52f5631a4c05 rtlwifi: rtl8192ce: Fix loading of incorrect firmware) Merging mac80211/master (fd551bac4795 nl80211: Fix mesh HT operation check) Merging sound-current/for-linus (af677166cf63 ALSA: hda - adding a new NV HDMI/DP codec ID in the driver) Merging pci-current/for-linus (d98e0929071e Revert "PCI: pciehp: Add runtime PM support for PCIe hotplug ports") Merging driver-core.current/driver-core-linus (49def1853334 Linux 4.10-rc4) Merging tty.current/tty-linus (49def1853334 Linux 4.10-rc4) Merging usb.current/usb-linus (d5adbfcd5f7b Linux 4.10-rc7) Merging usb-gadget-fixes/fixes (efe357f4633a usb: dwc2: host: fix Wmaybe-uninitialized warning) Merging usb-serial-fixes/usb-linus (d07830db1bdb USB: serial: pl2303: add ATEN device ID) Merging usb-chipidea-fixes/ci-for-usb-stable (c7fbb09b2ea1 usb: chipidea: move the lock initialization to core file) Merging phy/fixes (7ce7d89f4883 Linux 4.10-rc1) Merging staging.current/staging-linus (d5adbfcd5f7b Linux 4.10-rc7) Merging char-misc.current/char-misc-linus (d5adbfcd5f7b Linux 4.10-rc7) Merging input-current/for-linus (413d37326700 Input: synaptics-rmi4 - select 'SERIO' when needed) Merging crypto-current/master (7c2cf1c4615c crypto: chcr - Fix key length for RFC4106) Merging ide/master (da095587e6be Revert "ide: Fix interface autodetection in legacy IDE driver (trial #2)") Merging vfio-fixes/for-linus (930a42ded3fe vfio/spapr_tce: Set window when adding
linux-next: Tree for Feb 13
Hi all, Changes since 20170210: The ipsec-next tree gained a conflict against the net-next tree. The rdma-leon gained a conflict against Linus' tree. The l2mtd-tree lost its build failure. Non-merge commits (relative to Linus' tree): 8646 9682 files changed, 388711 insertions(+), 182504 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 and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 256 trees (counting Linus' and 37 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 (1ce42845f987 Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip) Merging fixes/master (30066ce675d3 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging kbuild-current/rc-fixes (c7858bf16c0b asm-prototypes: Clear any CPP defines before declaring the functions) Merging arc-current/for-curr (8ba605b607b7 ARC: [plat-*] ARC_HAS_COH_CACHES no longer relevant) Merging arm-current/fixes (228dbbfb5d77 ARM: 8643/3: arm/ptrace: Preserve previous registers for short regset write) Merging m68k-current/for-linus (ad595b77c4a8 m68k/atari: Use seq_puts() in atari_get_hardware_list()) Merging metag-fixes/fixes (35d04077ad96 metag: Only define atomic_dec_if_positive conditionally) Merging powerpc-fixes/fixes (f83e6862047e powerpc/powernv: Properly set "host-ipi" on IPIs) Merging sparc/master (f9a42e0d58cf Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc) Merging fscrypt-current/for-stable (42d97eb0ade3 fscrypt: fix renaming and linking special files) Merging net/master (e722af639194 ibmvnic: Call napi_disable instead of napi_enable in failure path) Merging ipsec/master (c28a45cb xfrm: policy: init locks early) Merging netfilter/master (f95d7a46bc57 netfilter: ctnetlink: Fix regression in CTA_HELP processing) Merging ipvs/master (045169816b31 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6) Merging wireless-drivers/master (52f5631a4c05 rtlwifi: rtl8192ce: Fix loading of incorrect firmware) Merging mac80211/master (fd551bac4795 nl80211: Fix mesh HT operation check) Merging sound-current/for-linus (af677166cf63 ALSA: hda - adding a new NV HDMI/DP codec ID in the driver) Merging pci-current/for-linus (d98e0929071e Revert "PCI: pciehp: Add runtime PM support for PCIe hotplug ports") Merging driver-core.current/driver-core-linus (49def1853334 Linux 4.10-rc4) Merging tty.current/tty-linus (49def1853334 Linux 4.10-rc4) Merging usb.current/usb-linus (d5adbfcd5f7b Linux 4.10-rc7) Merging usb-gadget-fixes/fixes (efe357f4633a usb: dwc2: host: fix Wmaybe-uninitialized warning) Merging usb-serial-fixes/usb-linus (d07830db1bdb USB: serial: pl2303: add ATEN device ID) Merging usb-chipidea-fixes/ci-for-usb-stable (c7fbb09b2ea1 usb: chipidea: move the lock initialization to core file) Merging phy/fixes (7ce7d89f4883 Linux 4.10-rc1) Merging staging.current/staging-linus (d5adbfcd5f7b Linux 4.10-rc7) Merging char-misc.current/char-misc-linus (d5adbfcd5f7b Linux 4.10-rc7) Merging input-current/for-linus (413d37326700 Input: synaptics-rmi4 - select 'SERIO' when needed) Merging crypto-current/master (7c2cf1c4615c crypto: chcr - Fix key length for RFC4106) Merging ide/master (da095587e6be Revert "ide: Fix interface autodetection in legacy IDE driver (trial #2)") Merging vfio-fixes/for-linus (930a42ded3fe vfio/spapr_tce: Set window when adding
Re: linux-next: Tree for Feb 13 (runtime failures and 'non-zero nr_pmds' messages)
Hi Stephen, On 02/13/2015 03:37 PM, Stephen Rothwell wrote: Hi Guenter, On Fri, 13 Feb 2015 10:54:28 -0800 Guenter Roeck wrote: I see a number of runtime failures with this version. It affects alpha, mips64, ppc64, and x86_64. Symptom is always the same. There are lots of BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4) messages in the log, and the affected VMs don't reboot. I don't see the problem in curent mainline, nor in mmotm. Bisect points to "Merge branch 'akpm-current/current'", which isn't really helpful. Not sure if this is a bad merge resolution, so just take this as a heads-up for now. Yours is the second report overnight (see attached). Almost certainly a bad merge resolution on my part (its a bit hard when Andrew get part of his patch set merged by Linus :-() And now Fengguang's tests caught it as well. I will fix up the merge on Monday (unless Andrew gets more stuff merged or updates mmotm for me). Sorry about that. No worries. Good news is that test coverage is getting better. 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 Feb 13 (iio/magnetometer/ak8975.c)
On 02/13/15 16:32, Randy Dunlap wrote:
> On 02/12/15 21:56, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any material destined for v3.21 to your linux-next
>> included trees until after v3.20-rc1 has been released.
>>
>> Changes since 20150212:
>
> on i386: when CONFIG_I2C is not enabled:
Caused by AK09911 selecting AK8975 but AK09911 does not depend on I2C.
> ../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_who_i_am':
> ../drivers/iio/magnetometer/ak8975.c:393:2: error: implicit declaration of
> function 'i2c_smbus_read_i2c_block_data'
> [-Werror=implicit-function-declaration]
> ret = i2c_smbus_read_i2c_block_data(client, AK09912_REG_WIA1,
> ^
> ../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_set_mode':
> ../drivers/iio/magnetometer/ak8975.c:431:2: error: implicit declaration of
> function 'i2c_smbus_write_byte_data' [-Werror=implicit-function-declaration]
> ret = i2c_smbus_write_byte_data(data->client,
> ^
> ../drivers/iio/magnetometer/ak8975.c: In function
> 'wait_conversion_complete_gpio':
> ../drivers/iio/magnetometer/ak8975.c:555:2: error: implicit declaration of
> function 'i2c_smbus_read_byte_data' [-Werror=implicit-function-declaration]
> ret = i2c_smbus_read_byte_data(client, data->def->ctrl_regs[ST1]);
> ^
> ../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_read_axis':
> ../drivers/iio/magnetometer/ak8975.c:650:2: error: implicit declaration of
> function 'i2c_smbus_read_word_data' [-Werror=implicit-function-declaration]
> ret = i2c_smbus_read_word_data(client, data->def->data_regs[index]);
> ^
> ../drivers/iio/magnetometer/ak8975.c: At top level:
> ../drivers/iio/magnetometer/ak8975.c:846:1: warning: data definition has no
> type or storage class [enabled by default]
> module_i2c_driver(ak8975_driver);
> ^
> ../drivers/iio/magnetometer/ak8975.c:846:1: error: type defaults to 'int' in
> declaration of 'module_i2c_driver' [-Werror=implicit-int]
> ../drivers/iio/magnetometer/ak8975.c:846:1: warning: parameter names (without
> types) in function declaration [enabled by default]
> ../drivers/iio/magnetometer/ak8975.c:837:26: warning: 'ak8975_driver' defined
> but not used [-Wunused-variable]
> static struct i2c_driver ak8975_driver = {
> ^
> cc1: some warnings being treated as errors
> make[4]: *** [drivers/iio/magnetometer/ak8975.o] Error 1
>
>
--
~Randy
--
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 Feb 13 (iio/magnetometer/ak8975.c)
On 02/12/15 21:56, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
on i386: when CONFIG_I2C is not enabled:
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_who_i_am':
../drivers/iio/magnetometer/ak8975.c:393:2: error: implicit declaration of
function 'i2c_smbus_read_i2c_block_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_read_i2c_block_data(client, AK09912_REG_WIA1,
^
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_set_mode':
../drivers/iio/magnetometer/ak8975.c:431:2: error: implicit declaration of
function 'i2c_smbus_write_byte_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_write_byte_data(data->client,
^
../drivers/iio/magnetometer/ak8975.c: In function
'wait_conversion_complete_gpio':
../drivers/iio/magnetometer/ak8975.c:555:2: error: implicit declaration of
function 'i2c_smbus_read_byte_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_read_byte_data(client, data->def->ctrl_regs[ST1]);
^
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_read_axis':
../drivers/iio/magnetometer/ak8975.c:650:2: error: implicit declaration of
function 'i2c_smbus_read_word_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_read_word_data(client, data->def->data_regs[index]);
^
../drivers/iio/magnetometer/ak8975.c: At top level:
../drivers/iio/magnetometer/ak8975.c:846:1: warning: data definition has no
type or storage class [enabled by default]
module_i2c_driver(ak8975_driver);
^
../drivers/iio/magnetometer/ak8975.c:846:1: error: type defaults to 'int' in
declaration of 'module_i2c_driver' [-Werror=implicit-int]
../drivers/iio/magnetometer/ak8975.c:846:1: warning: parameter names (without
types) in function declaration [enabled by default]
../drivers/iio/magnetometer/ak8975.c:837:26: warning: 'ak8975_driver' defined
but not used [-Wunused-variable]
static struct i2c_driver ak8975_driver = {
^
cc1: some warnings being treated as errors
make[4]: *** [drivers/iio/magnetometer/ak8975.o] Error 1
--
~Randy
--
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 Feb 13 (runtime failures and 'non-zero nr_pmds' messages)
Hi Guenter,
On Fri, 13 Feb 2015 10:54:28 -0800 Guenter Roeck wrote:
>
> I see a number of runtime failures with this version.
> It affects alpha, mips64, ppc64, and x86_64.
> Symptom is always the same. There are lots of
>
> BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4)
>
> messages in the log, and the affected VMs don't reboot.
>
> I don't see the problem in curent mainline, nor in mmotm.
> Bisect points to "Merge branch 'akpm-current/current'",
> which isn't really helpful.
>
> Not sure if this is a bad merge resolution, so just take this
> as a heads-up for now.
Yours is the second report overnight (see attached). Almost certainly
a bad merge resolution on my part (its a bit hard when Andrew get part
of his patch set merged by Linus :-()
I will fix up the merge on Monday (unless Andrew gets more stuff merged
or updates mmotm for me).
Sorry about that.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
--- Begin Message ---
2015-02-13, 16:56:15 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
Hi Stephen,
Your conflict resolution in
8fe7fba50596 "Merge branch 'akpm-current/current'"
for mm/memory.c looks a bit off. I get flooded with these messages:
BUG: non-zero nr_pmds on freeing mm: 4
and fixed it with:
diff --git a/mm/memory.c b/mm/memory.c
index 450e4952c5ef..802adda2b0b6 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -3350,7 +3350,6 @@ int __pmd_alloc(struct mm_struct *mm, pud_t *pud,
unsigned long address)
smp_wmb(); /* See comment in __pte_alloc */
spin_lock(>page_table_lock);
- mm_inc_nr_pmds(mm);
#ifndef __ARCH_HAS_4LEVEL_HACK
if (!pud_present(*pud)) {
mm_inc_nr_pmds(mm);
references:
http://www.spinics.net/lists/linux-mm/msg84294.html
dc6c9a35b66b "mm: account pmd page tables to the process"
[CC'ed Kirill A. Shutemov]
Thanks
--
Sabrina
--- End Message ---
pgp9Hoo3gQhMf.pgp
Description: OpenPGP digital signature
Re: linux-next: Tree for Feb 13 (runtime failures and 'non-zero nr_pmds' messages)
On Fri, Feb 13, 2015 at 04:56:15PM +1100, Stephen Rothwell wrote: > Hi all, > > Please do not add any material destined for v3.21 to your linux-next > included trees until after v3.20-rc1 has been released. > > Changes since 20150212: > > The mips tree gained a conflict against Linus' tree. > > Non-merge commits (relative to Linus' tree): 4418 > 4081 files changed, 183203 insertions(+), 92585 deletions(-) > > > I see a number of runtime failures with this version. It affects alpha, mips64, ppc64, and x86_64. Symptom is always the same. There are lots of BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4) messages in the log, and the affected VMs don't reboot. I don't see the problem in curent mainline, nor in mmotm. Bisect points to "Merge branch 'akpm-current/current'", which isn't really helpful. Not sure if this is a bad merge resolution, so just take this as a heads-up for now. 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 Feb 13 (nfsd)
On 02/12/15 21:56, Stephen Rothwell wrote: > Hi all, > > Please do not add any material destined for v3.21 to your linux-next > included trees until after v3.20-rc1 has been released. > > Changes since 20150212: on x86_64, when # CONFIG_NFS_FS is not set CONFIG_NFSD=y # CONFIG_NFSD_V3 is not set # CONFIG_NFSD_V4 is not set In file included from ../include/linux/linkage.h:4:0, from ../include/linux/preempt.h:9, from ../include/linux/spinlock.h:50, from ../include/linux/mmzone.h:7, from ../include/linux/gfp.h:5, from ../include/linux/slab.h:14, from ../fs/nfsd/nfsctl.c:7: ../fs/nfsd/xdr4.h: In function 'set_change_info': ../fs/nfsd/xdr4.h:633:13: error: 'struct svc_fh' has no member named 'fh_pre_saved' BUG_ON(!fhp->fh_pre_saved); ^ ../include/linux/compiler.h:164:42: note: in definition of macro 'unlikely' # define unlikely(x) __builtin_expect(!!(x), 0) ^ ../fs/nfsd/xdr4.h:633:2: note: in expansion of macro 'BUG_ON' BUG_ON(!fhp->fh_pre_saved); ^ In file included from ../fs/nfsd/pnfs.h:8:0, from ../fs/nfsd/nfsctl.c:24: ../fs/nfsd/xdr4.h:634:21: error: 'struct svc_fh' has no member named 'fh_post_saved' cinfo->atomic = fhp->fh_post_saved; ^ ../fs/nfsd/xdr4.h:637:28: error: 'struct svc_fh' has no member named 'fh_pre_change' cinfo->before_change = fhp->fh_pre_change; ^ ../fs/nfsd/xdr4.h:638:27: error: 'struct svc_fh' has no member named 'fh_post_change' cinfo->after_change = fhp->fh_post_change; ^ ../fs/nfsd/xdr4.h:639:31: error: 'struct svc_fh' has no member named 'fh_pre_ctime' cinfo->before_ctime_sec = fhp->fh_pre_ctime.tv_sec; ^ ../fs/nfsd/xdr4.h:640:32: error: 'struct svc_fh' has no member named 'fh_pre_ctime' cinfo->before_ctime_nsec = fhp->fh_pre_ctime.tv_nsec; ^ ../fs/nfsd/xdr4.h:641:30: error: 'struct svc_fh' has no member named 'fh_post_attr' cinfo->after_ctime_sec = fhp->fh_post_attr.ctime.tv_sec; ^ ../fs/nfsd/xdr4.h:642:31: error: 'struct svc_fh' has no member named 'fh_post_attr' cinfo->after_ctime_nsec = fhp->fh_post_attr.ctime.tv_nsec; ^ -- ~Randy -- 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 Feb 13
2015-02-13, 16:56:15 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
Hi Stephen,
Your conflict resolution in
8fe7fba50596 "Merge branch 'akpm-current/current'"
for mm/memory.c looks a bit off. I get flooded with these messages:
BUG: non-zero nr_pmds on freeing mm: 4
and fixed it with:
diff --git a/mm/memory.c b/mm/memory.c
index 450e4952c5ef..802adda2b0b6 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -3350,7 +3350,6 @@ int __pmd_alloc(struct mm_struct *mm, pud_t *pud,
unsigned long address)
smp_wmb(); /* See comment in __pte_alloc */
spin_lock(>page_table_lock);
- mm_inc_nr_pmds(mm);
#ifndef __ARCH_HAS_4LEVEL_HACK
if (!pud_present(*pud)) {
mm_inc_nr_pmds(mm);
references:
http://www.spinics.net/lists/linux-mm/msg84294.html
dc6c9a35b66b "mm: account pmd page tables to the process"
[CC'ed Kirill A. Shutemov]
Thanks
--
Sabrina
--
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 Feb 13
2015-02-13, 16:56:15 +1100, Stephen Rothwell wrote:
Hi all,
Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.
Changes since 20150212:
Hi Stephen,
Your conflict resolution in
8fe7fba50596 Merge branch 'akpm-current/current'
for mm/memory.c looks a bit off. I get flooded with these messages:
BUG: non-zero nr_pmds on freeing mm: 4
and fixed it with:
diff --git a/mm/memory.c b/mm/memory.c
index 450e4952c5ef..802adda2b0b6 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -3350,7 +3350,6 @@ int __pmd_alloc(struct mm_struct *mm, pud_t *pud,
unsigned long address)
smp_wmb(); /* See comment in __pte_alloc */
spin_lock(mm-page_table_lock);
- mm_inc_nr_pmds(mm);
#ifndef __ARCH_HAS_4LEVEL_HACK
if (!pud_present(*pud)) {
mm_inc_nr_pmds(mm);
references:
http://www.spinics.net/lists/linux-mm/msg84294.html
dc6c9a35b66b mm: account pmd page tables to the process
[CC'ed Kirill A. Shutemov]
Thanks
--
Sabrina
--
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 Feb 13 (nfsd)
On 02/12/15 21:56, Stephen Rothwell wrote: Hi all, Please do not add any material destined for v3.21 to your linux-next included trees until after v3.20-rc1 has been released. Changes since 20150212: on x86_64, when # CONFIG_NFS_FS is not set CONFIG_NFSD=y # CONFIG_NFSD_V3 is not set # CONFIG_NFSD_V4 is not set In file included from ../include/linux/linkage.h:4:0, from ../include/linux/preempt.h:9, from ../include/linux/spinlock.h:50, from ../include/linux/mmzone.h:7, from ../include/linux/gfp.h:5, from ../include/linux/slab.h:14, from ../fs/nfsd/nfsctl.c:7: ../fs/nfsd/xdr4.h: In function 'set_change_info': ../fs/nfsd/xdr4.h:633:13: error: 'struct svc_fh' has no member named 'fh_pre_saved' BUG_ON(!fhp-fh_pre_saved); ^ ../include/linux/compiler.h:164:42: note: in definition of macro 'unlikely' # define unlikely(x) __builtin_expect(!!(x), 0) ^ ../fs/nfsd/xdr4.h:633:2: note: in expansion of macro 'BUG_ON' BUG_ON(!fhp-fh_pre_saved); ^ In file included from ../fs/nfsd/pnfs.h:8:0, from ../fs/nfsd/nfsctl.c:24: ../fs/nfsd/xdr4.h:634:21: error: 'struct svc_fh' has no member named 'fh_post_saved' cinfo-atomic = fhp-fh_post_saved; ^ ../fs/nfsd/xdr4.h:637:28: error: 'struct svc_fh' has no member named 'fh_pre_change' cinfo-before_change = fhp-fh_pre_change; ^ ../fs/nfsd/xdr4.h:638:27: error: 'struct svc_fh' has no member named 'fh_post_change' cinfo-after_change = fhp-fh_post_change; ^ ../fs/nfsd/xdr4.h:639:31: error: 'struct svc_fh' has no member named 'fh_pre_ctime' cinfo-before_ctime_sec = fhp-fh_pre_ctime.tv_sec; ^ ../fs/nfsd/xdr4.h:640:32: error: 'struct svc_fh' has no member named 'fh_pre_ctime' cinfo-before_ctime_nsec = fhp-fh_pre_ctime.tv_nsec; ^ ../fs/nfsd/xdr4.h:641:30: error: 'struct svc_fh' has no member named 'fh_post_attr' cinfo-after_ctime_sec = fhp-fh_post_attr.ctime.tv_sec; ^ ../fs/nfsd/xdr4.h:642:31: error: 'struct svc_fh' has no member named 'fh_post_attr' cinfo-after_ctime_nsec = fhp-fh_post_attr.ctime.tv_nsec; ^ -- ~Randy -- 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 Feb 13 (runtime failures and 'non-zero nr_pmds' messages)
On Fri, Feb 13, 2015 at 04:56:15PM +1100, Stephen Rothwell wrote: Hi all, Please do not add any material destined for v3.21 to your linux-next included trees until after v3.20-rc1 has been released. Changes since 20150212: The mips tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree): 4418 4081 files changed, 183203 insertions(+), 92585 deletions(-) I see a number of runtime failures with this version. It affects alpha, mips64, ppc64, and x86_64. Symptom is always the same. There are lots of BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4) messages in the log, and the affected VMs don't reboot. I don't see the problem in curent mainline, nor in mmotm. Bisect points to Merge branch 'akpm-current/current', which isn't really helpful. Not sure if this is a bad merge resolution, so just take this as a heads-up for now. 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 Feb 13 (runtime failures and 'non-zero nr_pmds' messages)
Hi Guenter,
On Fri, 13 Feb 2015 10:54:28 -0800 Guenter Roeck li...@roeck-us.net wrote:
I see a number of runtime failures with this version.
It affects alpha, mips64, ppc64, and x86_64.
Symptom is always the same. There are lots of
BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4)
messages in the log, and the affected VMs don't reboot.
I don't see the problem in curent mainline, nor in mmotm.
Bisect points to Merge branch 'akpm-current/current',
which isn't really helpful.
Not sure if this is a bad merge resolution, so just take this
as a heads-up for now.
Yours is the second report overnight (see attached). Almost certainly
a bad merge resolution on my part (its a bit hard when Andrew get part
of his patch set merged by Linus :-()
I will fix up the merge on Monday (unless Andrew gets more stuff merged
or updates mmotm for me).
Sorry about that.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
---BeginMessage---
2015-02-13, 16:56:15 +1100, Stephen Rothwell wrote:
Hi all,
Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.
Changes since 20150212:
Hi Stephen,
Your conflict resolution in
8fe7fba50596 Merge branch 'akpm-current/current'
for mm/memory.c looks a bit off. I get flooded with these messages:
BUG: non-zero nr_pmds on freeing mm: 4
and fixed it with:
diff --git a/mm/memory.c b/mm/memory.c
index 450e4952c5ef..802adda2b0b6 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -3350,7 +3350,6 @@ int __pmd_alloc(struct mm_struct *mm, pud_t *pud,
unsigned long address)
smp_wmb(); /* See comment in __pte_alloc */
spin_lock(mm-page_table_lock);
- mm_inc_nr_pmds(mm);
#ifndef __ARCH_HAS_4LEVEL_HACK
if (!pud_present(*pud)) {
mm_inc_nr_pmds(mm);
references:
http://www.spinics.net/lists/linux-mm/msg84294.html
dc6c9a35b66b mm: account pmd page tables to the process
[CC'ed Kirill A. Shutemov]
Thanks
--
Sabrina
---End Message---
pgp9Hoo3gQhMf.pgp
Description: OpenPGP digital signature
Re: linux-next: Tree for Feb 13 (iio/magnetometer/ak8975.c)
On 02/13/15 16:32, Randy Dunlap wrote:
On 02/12/15 21:56, Stephen Rothwell wrote:
Hi all,
Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.
Changes since 20150212:
on i386: when CONFIG_I2C is not enabled:
Caused by AK09911 selecting AK8975 but AK09911 does not depend on I2C.
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_who_i_am':
../drivers/iio/magnetometer/ak8975.c:393:2: error: implicit declaration of
function 'i2c_smbus_read_i2c_block_data'
[-Werror=implicit-function-declaration]
ret = i2c_smbus_read_i2c_block_data(client, AK09912_REG_WIA1,
^
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_set_mode':
../drivers/iio/magnetometer/ak8975.c:431:2: error: implicit declaration of
function 'i2c_smbus_write_byte_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_write_byte_data(data-client,
^
../drivers/iio/magnetometer/ak8975.c: In function
'wait_conversion_complete_gpio':
../drivers/iio/magnetometer/ak8975.c:555:2: error: implicit declaration of
function 'i2c_smbus_read_byte_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_read_byte_data(client, data-def-ctrl_regs[ST1]);
^
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_read_axis':
../drivers/iio/magnetometer/ak8975.c:650:2: error: implicit declaration of
function 'i2c_smbus_read_word_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_read_word_data(client, data-def-data_regs[index]);
^
../drivers/iio/magnetometer/ak8975.c: At top level:
../drivers/iio/magnetometer/ak8975.c:846:1: warning: data definition has no
type or storage class [enabled by default]
module_i2c_driver(ak8975_driver);
^
../drivers/iio/magnetometer/ak8975.c:846:1: error: type defaults to 'int' in
declaration of 'module_i2c_driver' [-Werror=implicit-int]
../drivers/iio/magnetometer/ak8975.c:846:1: warning: parameter names (without
types) in function declaration [enabled by default]
../drivers/iio/magnetometer/ak8975.c:837:26: warning: 'ak8975_driver' defined
but not used [-Wunused-variable]
static struct i2c_driver ak8975_driver = {
^
cc1: some warnings being treated as errors
make[4]: *** [drivers/iio/magnetometer/ak8975.o] Error 1
--
~Randy
--
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 Feb 13 (iio/magnetometer/ak8975.c)
On 02/12/15 21:56, Stephen Rothwell wrote:
Hi all,
Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.
Changes since 20150212:
on i386: when CONFIG_I2C is not enabled:
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_who_i_am':
../drivers/iio/magnetometer/ak8975.c:393:2: error: implicit declaration of
function 'i2c_smbus_read_i2c_block_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_read_i2c_block_data(client, AK09912_REG_WIA1,
^
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_set_mode':
../drivers/iio/magnetometer/ak8975.c:431:2: error: implicit declaration of
function 'i2c_smbus_write_byte_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_write_byte_data(data-client,
^
../drivers/iio/magnetometer/ak8975.c: In function
'wait_conversion_complete_gpio':
../drivers/iio/magnetometer/ak8975.c:555:2: error: implicit declaration of
function 'i2c_smbus_read_byte_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_read_byte_data(client, data-def-ctrl_regs[ST1]);
^
../drivers/iio/magnetometer/ak8975.c: In function 'ak8975_read_axis':
../drivers/iio/magnetometer/ak8975.c:650:2: error: implicit declaration of
function 'i2c_smbus_read_word_data' [-Werror=implicit-function-declaration]
ret = i2c_smbus_read_word_data(client, data-def-data_regs[index]);
^
../drivers/iio/magnetometer/ak8975.c: At top level:
../drivers/iio/magnetometer/ak8975.c:846:1: warning: data definition has no
type or storage class [enabled by default]
module_i2c_driver(ak8975_driver);
^
../drivers/iio/magnetometer/ak8975.c:846:1: error: type defaults to 'int' in
declaration of 'module_i2c_driver' [-Werror=implicit-int]
../drivers/iio/magnetometer/ak8975.c:846:1: warning: parameter names (without
types) in function declaration [enabled by default]
../drivers/iio/magnetometer/ak8975.c:837:26: warning: 'ak8975_driver' defined
but not used [-Wunused-variable]
static struct i2c_driver ak8975_driver = {
^
cc1: some warnings being treated as errors
make[4]: *** [drivers/iio/magnetometer/ak8975.o] Error 1
--
~Randy
--
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 Feb 13 (runtime failures and 'non-zero nr_pmds' messages)
Hi Stephen, On 02/13/2015 03:37 PM, Stephen Rothwell wrote: Hi Guenter, On Fri, 13 Feb 2015 10:54:28 -0800 Guenter Roeck li...@roeck-us.net wrote: I see a number of runtime failures with this version. It affects alpha, mips64, ppc64, and x86_64. Symptom is always the same. There are lots of BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4) messages in the log, and the affected VMs don't reboot. I don't see the problem in curent mainline, nor in mmotm. Bisect points to Merge branch 'akpm-current/current', which isn't really helpful. Not sure if this is a bad merge resolution, so just take this as a heads-up for now. Yours is the second report overnight (see attached). Almost certainly a bad merge resolution on my part (its a bit hard when Andrew get part of his patch set merged by Linus :-() And now Fengguang's tests caught it as well. I will fix up the merge on Monday (unless Andrew gets more stuff merged or updates mmotm for me). Sorry about that. No worries. Good news is that test coverage is getting better. 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 Feb 13
Hi all, Please do not add any material destined for v3.21 to your linux-next included trees until after v3.20-rc1 has been released. Changes since 20150212: The mips tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree): 4418 4081 files changed, 183203 insertions(+), 92585 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 206 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 (8494bcf5b7c4 Merge branch 'for-3.20/drivers' of git://git.kernel.dk/linux-block) Merging fixes/master (b94d525e58dc Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging kbuild-current/rc-fixes (a16c5f99a28c kbuild: Fix removal of the debian/ directory) Merging arc-current/for-curr (2ce7598c9a45 Linux 3.17-rc4) Merging arm-current/fixes (8e6480667246 ARM: 8299/1: mm: ensure local active ASID is marked as allocated on rollover) Merging m68k-current/for-linus (4436820a98cd m68k/defconfig: Enable Ethernet bridging) 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 (31345e1a071e powerpc/pci: Remove unused force_32bit_msi quirk) Merging powerpc-merge-mpe/fixes (c59c961ca511 Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux) Merging sparc/master (66d0f7ec9f10 sparc32: destroy_context() and switch_mm() needs to disable interrupts.) Merging net/master (9672723973f1 bridge: netfilter: Move sysctl-specific error code inside #ifdef) Merging ipsec/master (ac37e2515c1a xfrm: release dst_orig in case of error in xfrm_lookup()) Merging sound-current/for-linus (0b444af8daf9 ALSA: seq: potential out of bounds in do_control()) Merging pci-current/for-linus (feb28979c137 of/pci: Remove duplicate kfree in of_pci_get_host_bridge_resources()) Merging wireless-drivers/master (aeb2d2a4c0ae rtlwifi: Remove logging statement that is no longer needed) Merging driver-core.current/driver-core-linus (26bc420b59a3 Linux 3.19-rc6) Merging tty.current/tty-linus (ec6f34e5b552 Linux 3.19-rc5) Merging usb.current/usb-linus (e36f014edff7 Linux 3.19-rc7) Merging usb-gadget-fixes/fixes (0df8fc37f6e4 usb: phy: never defer probe in non-OF case) Merging usb-serial-fixes/usb-linus (a6f0331236fa USB: cp210x: add ID for RUGGEDCOM USB Serial Console) Merging staging.current/staging-linus (e36f014edff7 Linux 3.19-rc7) Merging char-misc.current/char-misc-linus (e36f014edff7 Linux 3.19-rc7) Merging input-current/for-linus (4ba24fef3eb3 Merge branch 'next' into for-linus) Merging crypto-current/master (3e14dcf7cb80 crypto: add missing crypto module aliases) Merging ide/master (f96fe225677b Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging devicetree-current/devicetree/merge (6b1271de3723 of/unittest: Overlays with sub-devices tests) Merging rr-fixes/fixes (dc4515ea26d6 scsi: always increment reference count) Merging vfio-fixes/for-linus (7c2e211f3c95 vfio-pci: Fix the check on pci device type in vfio_pci_probe()) Merging kselftest-fixes/fixes (f5db310d77ef selftests/vm: fix link error for transhuge-stress test) Merging drm-intel-fixes/for-linux-next-fixes (bfa76d495765 Linux 3.19) Merging asm-generic/master (643165c8bbc8 Merge tag 'uaccess_for_upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost into asm-generic) Merging arc/for-next (091f56be10ef ARC: Fix earlycon build
linux-next: Tree for Feb 13
Hi all, Please do not add any material destined for v3.21 to your linux-next included trees until after v3.20-rc1 has been released. Changes since 20150212: The mips tree gained a conflict against Linus' tree. Non-merge commits (relative to Linus' tree): 4418 4081 files changed, 183203 insertions(+), 92585 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 206 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 (8494bcf5b7c4 Merge branch 'for-3.20/drivers' of git://git.kernel.dk/linux-block) Merging fixes/master (b94d525e58dc Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging kbuild-current/rc-fixes (a16c5f99a28c kbuild: Fix removal of the debian/ directory) Merging arc-current/for-curr (2ce7598c9a45 Linux 3.17-rc4) Merging arm-current/fixes (8e6480667246 ARM: 8299/1: mm: ensure local active ASID is marked as allocated on rollover) Merging m68k-current/for-linus (4436820a98cd m68k/defconfig: Enable Ethernet bridging) 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 (31345e1a071e powerpc/pci: Remove unused force_32bit_msi quirk) Merging powerpc-merge-mpe/fixes (c59c961ca511 Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux) Merging sparc/master (66d0f7ec9f10 sparc32: destroy_context() and switch_mm() needs to disable interrupts.) Merging net/master (9672723973f1 bridge: netfilter: Move sysctl-specific error code inside #ifdef) Merging ipsec/master (ac37e2515c1a xfrm: release dst_orig in case of error in xfrm_lookup()) Merging sound-current/for-linus (0b444af8daf9 ALSA: seq: potential out of bounds in do_control()) Merging pci-current/for-linus (feb28979c137 of/pci: Remove duplicate kfree in of_pci_get_host_bridge_resources()) Merging wireless-drivers/master (aeb2d2a4c0ae rtlwifi: Remove logging statement that is no longer needed) Merging driver-core.current/driver-core-linus (26bc420b59a3 Linux 3.19-rc6) Merging tty.current/tty-linus (ec6f34e5b552 Linux 3.19-rc5) Merging usb.current/usb-linus (e36f014edff7 Linux 3.19-rc7) Merging usb-gadget-fixes/fixes (0df8fc37f6e4 usb: phy: never defer probe in non-OF case) Merging usb-serial-fixes/usb-linus (a6f0331236fa USB: cp210x: add ID for RUGGEDCOM USB Serial Console) Merging staging.current/staging-linus (e36f014edff7 Linux 3.19-rc7) Merging char-misc.current/char-misc-linus (e36f014edff7 Linux 3.19-rc7) Merging input-current/for-linus (4ba24fef3eb3 Merge branch 'next' into for-linus) Merging crypto-current/master (3e14dcf7cb80 crypto: add missing crypto module aliases) Merging ide/master (f96fe225677b Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net) Merging devicetree-current/devicetree/merge (6b1271de3723 of/unittest: Overlays with sub-devices tests) Merging rr-fixes/fixes (dc4515ea26d6 scsi: always increment reference count) Merging vfio-fixes/for-linus (7c2e211f3c95 vfio-pci: Fix the check on pci device type in vfio_pci_probe()) Merging kselftest-fixes/fixes (f5db310d77ef selftests/vm: fix link error for transhuge-stress test) Merging drm-intel-fixes/for-linux-next-fixes (bfa76d495765 Linux 3.19) Merging asm-generic/master (643165c8bbc8 Merge tag 'uaccess_for_upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost into asm-generic) Merging arc/for-next (091f56be10ef ARC: Fix earlycon build breakage)
linux-next: Tree for Feb 13
Hi all,
If you see failures in building this tree due to missing declarations of
k..alloc/free, then it may be caused by commit 2bd59d48ebfb ("cgroup:
convert to kernfs"). Please send Tejun Heo a patch
adding an inclusion of linux/slab.h to the appropriate file(s).
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140212:
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The wireless-next tree gained a build failure for which I applied a patch.
The tip tree lost its build failure.
Non-merge commits (relative to Linus' tree): 2188
2457 files changed, 80774 insertions(+), 41385 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" 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 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 (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.
I am currently merging 208 trees (counting Linus' and 28 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.
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 (9398a10cd964 Merge tag 'regulator-v3.14-rc2' of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator)
Merging fixes/master (b0031f227e47 Merge tag 's2mps11-build' of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator)
Merging kbuild-current/rc-fixes (38dbfb59d117 Linus 3.14-rc1)
Merging arc-current/for-curr (7e22e91102c6 Linux 3.13-rc8)
Merging arm-current/fixes (b027df048500 ARM: 7957/1: add DSB after icache flush
in __flush_icache_all())
Merging m68k-current/for-linus (7247f55381d5 m68k: Wire up sched_setattr and
sched_getattr)
Merging metag-fixes/fixes (3b2f64d00c46 Linux 3.11-rc2)
Merging powerpc-merge/merge (cd15b048445d powerpc/powernv: Add iommu DMA bypass
support for IODA2)
Merging sparc/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of
git://git.monstr.eu/linux-2.6-microblaze)
Merging net/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of
git://git.monstr.eu/linux-2.6-microblaze)
Merging ipsec/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of
git://git.monstr.eu/linux-2.6-microblaze)
Merging sound-current/for-linus (0d7b520c9770 ALSA: hda - Better fix for
invalid COEF setup on Acer AO725)
Merging pci-current/for-linus (322a8e91844f PCI: mvebu: Use Device ID and
revision from underlying endpoint)
Merging wireless/master (348f7d4adee9 rtl8180: Add error check for
pci_map_single return value in TX path)
Merging driver-core.current/driver-core-linus (9e1ccb4a7700 drivers/base: fix
devres handling for master device)
Merging tty.current/tty-linus (d8a5dc3033af tty: Set correct tty name in
'active' sysfs attribute)
Merging usb.current/usb-linus (3635c7e2d59f usb: option: blacklist ZTE MF667
net interface)
Merging staging.current/staging-linus (ddf5eb564d97 staging/rtl8821ae: fix
build, depends on MAC80211)
Merging char-misc.current/char-misc-linus (3b1cc9b9622a misc: mic: fix possible
signed underflow (undefined behavior) in userspace API)
Merging input-current/for-linus (55df811f2066 Merge branch 'next' into
for-linus)
Merging md-current/for-linus (d47648fcf061 raid5: avoid finding "discard"
stripe)
Merging crypto-current/master (ee97dc7db4cb crypto: s390 - fix des and des3_ede
ctr concurrency issue)
Merging ide/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of
linux-next: Tree for Feb 13
Hi all, If you see failures in building this tree due to missing declarations of k..alloc/free, then it may be caused by commit 2bd59d48ebfb (cgroup: convert to kernfs). Please send Tejun Heo t...@kernel.org a patch adding an inclusion of linux/slab.h to the appropriate file(s). This tree fails (more than usual) the powerpc allyesconfig build. Changes since 20140212: The powerpc tree still had its build failure. The mfd-lj tree still had its build failure so I used the version from next-20140210. The wireless-next tree gained a build failure for which I applied a patch. The tip tree lost its build failure. Non-merge commits (relative to Linus' tree): 2188 2457 files changed, 80774 insertions(+), 41385 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 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 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 (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. I am currently merging 208 trees (counting Linus' and 28 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. 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 (9398a10cd964 Merge tag 'regulator-v3.14-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator) Merging fixes/master (b0031f227e47 Merge tag 's2mps11-build' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator) Merging kbuild-current/rc-fixes (38dbfb59d117 Linus 3.14-rc1) Merging arc-current/for-curr (7e22e91102c6 Linux 3.13-rc8) Merging arm-current/fixes (b027df048500 ARM: 7957/1: add DSB after icache flush in __flush_icache_all()) Merging m68k-current/for-linus (7247f55381d5 m68k: Wire up sched_setattr and sched_getattr) Merging metag-fixes/fixes (3b2f64d00c46 Linux 3.11-rc2) Merging powerpc-merge/merge (cd15b048445d powerpc/powernv: Add iommu DMA bypass support for IODA2) Merging sparc/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of git://git.monstr.eu/linux-2.6-microblaze) Merging net/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of git://git.monstr.eu/linux-2.6-microblaze) Merging ipsec/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of git://git.monstr.eu/linux-2.6-microblaze) Merging sound-current/for-linus (0d7b520c9770 ALSA: hda - Better fix for invalid COEF setup on Acer AO725) Merging pci-current/for-linus (322a8e91844f PCI: mvebu: Use Device ID and revision from underlying endpoint) Merging wireless/master (348f7d4adee9 rtl8180: Add error check for pci_map_single return value in TX path) Merging driver-core.current/driver-core-linus (9e1ccb4a7700 drivers/base: fix devres handling for master device) Merging tty.current/tty-linus (d8a5dc3033af tty: Set correct tty name in 'active' sysfs attribute) Merging usb.current/usb-linus (3635c7e2d59f usb: option: blacklist ZTE MF667 net interface) Merging staging.current/staging-linus (ddf5eb564d97 staging/rtl8821ae: fix build, depends on MAC80211) Merging char-misc.current/char-misc-linus (3b1cc9b9622a misc: mic: fix possible signed underflow (undefined behavior) in userspace API) Merging input-current/for-linus (55df811f2066 Merge branch 'next' into for-linus) Merging md-current/for-linus (d47648fcf061 raid5: avoid finding discard stripe) Merging crypto-current/master (ee97dc7db4cb crypto: s390 - fix des and des3_ede ctr concurrency issue) Merging ide/master (738b52bb9845 Merge tag 'microblaze-3.14-rc3' of
Re: linux-next: Tree for Feb 13 (virtio_console)
On Thu, Feb 14, 2013 at 4:23 PM, Stephen Rothwell wrote: > Hi Greg, > > On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH wrote: >> On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote: >> > >> > Also, has someone checked to see if any of the CONFIG_ symbols that had a >> > dependency on TTY added are selected anywhere else? >> >> Joe did all of that I think. Joe? > > OK, good. > I tried to find all of them, but I can't guarantee they're all fixed : ). I tried to search out the features that used the tty driver (using two initialization functions), and tried enabling all features while disabling TTY on my x86 64 bit machine. In addition to stubbing out functions that the kernel's initialization required. Any other suggestions for finding problems proactively are appreciated. - Joe -- 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 Feb 13 (virtio_console)
Hi Greg, On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH wrote: > > On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote: > > > > The patch below is needed in the tty tree (which introduced CONFIG_TTY). > > Ok, now done. Thanks. > > Also, has someone checked to see if any of the CONFIG_ symbols that had a > > dependency on TTY added are selected anywhere else? > > Joe did all of that I think. Joe? OK, good. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpXv60E4SqGc.pgp Description: PGP signature
Re: linux-next: Tree for Feb 13 (virtio_console)
On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote: > Hi Greg, > > The patch below is needed in the tty tree (which introduced CONFIG_TTY). Ok, now done. > Also, has someone checked to see if any of the CONFIG_ symbols that had a > dependency on TTY added are selected anywhere else? Joe did all of that I think. Joe? -- 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 Feb 13 (virtio_console)
Hi Greg, The patch below is needed in the tty tree (which introduced CONFIG_TTY). Also, has someone checked to see if any of the CONFIG_ symbols that had a dependency on TTY added are selected anywhere else? On Thu, 14 Feb 2013 10:55:06 -0800 Randy Dunlap wrote: > > On 02/14/13 10:45, Randy Dunlap wrote: > > On 02/13/13 19:00, Rusty Russell wrote: > >> Randy Dunlap writes: > >> > >>> On 02/13/13 00:35, Stephen Rothwell wrote: > Hi all, > > Changes since 20130212: > >>> > >>> on i386: > >>> > >>> drivers/built-in.o: In function `in_intr': > >>> virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' > >>> virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' > >>> drivers/built-in.o: In function `resize_console': > >>> virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize' > >>> drivers/built-in.o: In function `unplug_port': > >>> virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove' > >>> drivers/built-in.o: In function `init_port_console': > >>> (.text+0x2fe59): undefined reference to `hvc_alloc' > >>> drivers/built-in.o: In function `virtio_cons_early_init': > >>> (.init.text+0x16d1): undefined reference to `hvc_instantiate' > >>> > >>> > >>> Full randconfig file is attached. > >> > >> This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but > >> CONFIG_HVC_DRIVER isn't set. > >> > >> From drivers/char/Kconfig: > >> > >> config VIRTIO_CONSOLE > >>tristate "Virtio console" > >>depends on VIRTIO > >>select HVC_DRIVER > >> > >> ??? > > > > OK. It's probably yet another stinking problem with kvmtool and randconfig. > > Running *config reports: > > > > warning: (KVMTOOL_TEST_ENABLE && LGUEST_GUEST) selects VIRTIO_CONSOLE which > > has unmet direct dependencies (VIRTIO && TTY) > > > > > > I'll look a bit more... > > Nope, that's not it. Stephen's comments were much closer. > > The patch below fixes the kconfig warning and the build errors. > --- > > > > From: Randy Dunlap > > Fix kconfig warning for LGUEST_GUEST config by selecting TTY: > > warning: (KVMTOOL_TEST_ENABLE && LGUEST_GUEST) selects VIRTIO_CONSOLE which > has unmet direct dependencies (VIRTIO && TTY) > > Signed-off-by: Randy Dunlap > --- > arch/x86/lguest/Kconfig |1 + > 1 file changed, 1 insertion(+) > > --- linux-next-20130213.orig/arch/x86/lguest/Kconfig > +++ linux-next-20130213/arch/x86/lguest/Kconfig > @@ -2,6 +2,7 @@ config LGUEST_GUEST > bool "Lguest guest support" > select PARAVIRT > depends on X86_32 > + select TTY > select VIRTUALIZATION > select VIRTIO > select VIRTIO_CONSOLE -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpWjd2hXixte.pgp Description: PGP signature
Re: linux-next: Tree for Feb 13 (virtio_console)
On 02/14/13 10:45, Randy Dunlap wrote: > On 02/13/13 19:00, Rusty Russell wrote: >> Randy Dunlap writes: >> >>> On 02/13/13 00:35, Stephen Rothwell wrote: Hi all, Changes since 20130212: >>> >>> on i386: >>> >>> drivers/built-in.o: In function `in_intr': >>> virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' >>> virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' >>> drivers/built-in.o: In function `resize_console': >>> virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize' >>> drivers/built-in.o: In function `unplug_port': >>> virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove' >>> drivers/built-in.o: In function `init_port_console': >>> (.text+0x2fe59): undefined reference to `hvc_alloc' >>> drivers/built-in.o: In function `virtio_cons_early_init': >>> (.init.text+0x16d1): undefined reference to `hvc_instantiate' >>> >>> >>> Full randconfig file is attached. >> >> This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but >> CONFIG_HVC_DRIVER isn't set. >> >> From drivers/char/Kconfig: >> >> config VIRTIO_CONSOLE >> tristate "Virtio console" >> depends on VIRTIO >> select HVC_DRIVER >> >> ??? > > OK. It's probably yet another stinking problem with kvmtool and randconfig. > Running *config reports: > > warning: (KVMTOOL_TEST_ENABLE && LGUEST_GUEST) selects VIRTIO_CONSOLE which > has unmet direct dependencies (VIRTIO && TTY) > > > I'll look a bit more... Nope, that's not it. Stephen's comments were much closer. The patch below fixes the kconfig warning and the build errors. --- From: Randy Dunlap Fix kconfig warning for LGUEST_GUEST config by selecting TTY: warning: (KVMTOOL_TEST_ENABLE && LGUEST_GUEST) selects VIRTIO_CONSOLE which has unmet direct dependencies (VIRTIO && TTY) Signed-off-by: Randy Dunlap --- arch/x86/lguest/Kconfig |1 + 1 file changed, 1 insertion(+) --- linux-next-20130213.orig/arch/x86/lguest/Kconfig +++ linux-next-20130213/arch/x86/lguest/Kconfig @@ -2,6 +2,7 @@ config LGUEST_GUEST bool "Lguest guest support" select PARAVIRT depends on X86_32 + select TTY select VIRTUALIZATION select VIRTIO select VIRTIO_CONSOLE -- 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 Feb 13 (virtio_console)
On 02/13/13 19:00, Rusty Russell wrote: > Randy Dunlap writes: > >> On 02/13/13 00:35, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20130212: >> >> on i386: >> >> drivers/built-in.o: In function `in_intr': >> virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' >> virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' >> drivers/built-in.o: In function `resize_console': >> virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize' >> drivers/built-in.o: In function `unplug_port': >> virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove' >> drivers/built-in.o: In function `init_port_console': >> (.text+0x2fe59): undefined reference to `hvc_alloc' >> drivers/built-in.o: In function `virtio_cons_early_init': >> (.init.text+0x16d1): undefined reference to `hvc_instantiate' >> >> >> Full randconfig file is attached. > > This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but > CONFIG_HVC_DRIVER isn't set. > > From drivers/char/Kconfig: > > config VIRTIO_CONSOLE > tristate "Virtio console" > depends on VIRTIO > select HVC_DRIVER > > ??? OK. It's probably yet another stinking problem with kvmtool and randconfig. Running *config reports: warning: (KVMTOOL_TEST_ENABLE && LGUEST_GUEST) selects VIRTIO_CONSOLE which has unmet direct dependencies (VIRTIO && TTY) I'll look a bit more... thanks, -- ~Randy -- 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 Feb 13 (virtio_console)
On 02/13/13 19:00, Rusty Russell wrote: Randy Dunlap rdun...@infradead.org writes: On 02/13/13 00:35, Stephen Rothwell wrote: Hi all, Changes since 20130212: on i386: drivers/built-in.o: In function `in_intr': virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' drivers/built-in.o: In function `resize_console': virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize' drivers/built-in.o: In function `unplug_port': virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove' drivers/built-in.o: In function `init_port_console': (.text+0x2fe59): undefined reference to `hvc_alloc' drivers/built-in.o: In function `virtio_cons_early_init': (.init.text+0x16d1): undefined reference to `hvc_instantiate' Full randconfig file is attached. This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but CONFIG_HVC_DRIVER isn't set. From drivers/char/Kconfig: config VIRTIO_CONSOLE tristate Virtio console depends on VIRTIO select HVC_DRIVER ??? OK. It's probably yet another stinking problem with kvmtool and randconfig. Running *config reports: warning: (KVMTOOL_TEST_ENABLE LGUEST_GUEST) selects VIRTIO_CONSOLE which has unmet direct dependencies (VIRTIO TTY) I'll look a bit more... thanks, -- ~Randy -- 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 Feb 13 (virtio_console)
On 02/14/13 10:45, Randy Dunlap wrote: On 02/13/13 19:00, Rusty Russell wrote: Randy Dunlap rdun...@infradead.org writes: On 02/13/13 00:35, Stephen Rothwell wrote: Hi all, Changes since 20130212: on i386: drivers/built-in.o: In function `in_intr': virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' drivers/built-in.o: In function `resize_console': virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize' drivers/built-in.o: In function `unplug_port': virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove' drivers/built-in.o: In function `init_port_console': (.text+0x2fe59): undefined reference to `hvc_alloc' drivers/built-in.o: In function `virtio_cons_early_init': (.init.text+0x16d1): undefined reference to `hvc_instantiate' Full randconfig file is attached. This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but CONFIG_HVC_DRIVER isn't set. From drivers/char/Kconfig: config VIRTIO_CONSOLE tristate Virtio console depends on VIRTIO select HVC_DRIVER ??? OK. It's probably yet another stinking problem with kvmtool and randconfig. Running *config reports: warning: (KVMTOOL_TEST_ENABLE LGUEST_GUEST) selects VIRTIO_CONSOLE which has unmet direct dependencies (VIRTIO TTY) I'll look a bit more... Nope, that's not it. Stephen's comments were much closer. The patch below fixes the kconfig warning and the build errors. --- From: Randy Dunlap rdun...@infradead.org Fix kconfig warning for LGUEST_GUEST config by selecting TTY: warning: (KVMTOOL_TEST_ENABLE LGUEST_GUEST) selects VIRTIO_CONSOLE which has unmet direct dependencies (VIRTIO TTY) Signed-off-by: Randy Dunlap rdun...@infradead.org --- arch/x86/lguest/Kconfig |1 + 1 file changed, 1 insertion(+) --- linux-next-20130213.orig/arch/x86/lguest/Kconfig +++ linux-next-20130213/arch/x86/lguest/Kconfig @@ -2,6 +2,7 @@ config LGUEST_GUEST bool Lguest guest support select PARAVIRT depends on X86_32 + select TTY select VIRTUALIZATION select VIRTIO select VIRTIO_CONSOLE -- 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 Feb 13 (virtio_console)
Hi Greg, The patch below is needed in the tty tree (which introduced CONFIG_TTY). Also, has someone checked to see if any of the CONFIG_ symbols that had a dependency on TTY added are selected anywhere else? On Thu, 14 Feb 2013 10:55:06 -0800 Randy Dunlap rdun...@infradead.org wrote: On 02/14/13 10:45, Randy Dunlap wrote: On 02/13/13 19:00, Rusty Russell wrote: Randy Dunlap rdun...@infradead.org writes: On 02/13/13 00:35, Stephen Rothwell wrote: Hi all, Changes since 20130212: on i386: drivers/built-in.o: In function `in_intr': virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' drivers/built-in.o: In function `resize_console': virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize' drivers/built-in.o: In function `unplug_port': virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove' drivers/built-in.o: In function `init_port_console': (.text+0x2fe59): undefined reference to `hvc_alloc' drivers/built-in.o: In function `virtio_cons_early_init': (.init.text+0x16d1): undefined reference to `hvc_instantiate' Full randconfig file is attached. This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but CONFIG_HVC_DRIVER isn't set. From drivers/char/Kconfig: config VIRTIO_CONSOLE tristate Virtio console depends on VIRTIO select HVC_DRIVER ??? OK. It's probably yet another stinking problem with kvmtool and randconfig. Running *config reports: warning: (KVMTOOL_TEST_ENABLE LGUEST_GUEST) selects VIRTIO_CONSOLE which has unmet direct dependencies (VIRTIO TTY) I'll look a bit more... Nope, that's not it. Stephen's comments were much closer. The patch below fixes the kconfig warning and the build errors. --- From: Randy Dunlap rdun...@infradead.org Fix kconfig warning for LGUEST_GUEST config by selecting TTY: warning: (KVMTOOL_TEST_ENABLE LGUEST_GUEST) selects VIRTIO_CONSOLE which has unmet direct dependencies (VIRTIO TTY) Signed-off-by: Randy Dunlap rdun...@infradead.org --- arch/x86/lguest/Kconfig |1 + 1 file changed, 1 insertion(+) --- linux-next-20130213.orig/arch/x86/lguest/Kconfig +++ linux-next-20130213/arch/x86/lguest/Kconfig @@ -2,6 +2,7 @@ config LGUEST_GUEST bool Lguest guest support select PARAVIRT depends on X86_32 + select TTY select VIRTUALIZATION select VIRTIO select VIRTIO_CONSOLE -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpWjd2hXixte.pgp Description: PGP signature
Re: linux-next: Tree for Feb 13 (virtio_console)
On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote: Hi Greg, The patch below is needed in the tty tree (which introduced CONFIG_TTY). Ok, now done. Also, has someone checked to see if any of the CONFIG_ symbols that had a dependency on TTY added are selected anywhere else? Joe did all of that I think. Joe? -- 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 Feb 13 (virtio_console)
Hi Greg, On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH g...@kroah.com wrote: On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote: The patch below is needed in the tty tree (which introduced CONFIG_TTY). Ok, now done. Thanks. Also, has someone checked to see if any of the CONFIG_ symbols that had a dependency on TTY added are selected anywhere else? Joe did all of that I think. Joe? OK, good. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpXv60E4SqGc.pgp Description: PGP signature
Re: linux-next: Tree for Feb 13 (virtio_console)
On Thu, Feb 14, 2013 at 4:23 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Greg, On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH g...@kroah.com wrote: On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote: Also, has someone checked to see if any of the CONFIG_ symbols that had a dependency on TTY added are selected anywhere else? Joe did all of that I think. Joe? OK, good. I tried to find all of them, but I can't guarantee they're all fixed : ). I tried to search out the features that used the tty driver (using two initialization functions), and tried enabling all features while disabling TTY on my x86 64 bit machine. In addition to stubbing out functions that the kernel's initialization required. Any other suggestions for finding problems proactively are appreciated. - Joe -- 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 Feb 13 (virtio_console)
Hi Rusty, On Thu, 14 Feb 2013 13:30:37 +1030 Rusty Russell wrote: > > This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but > CONFIG_HVC_DRIVER isn't set. > > From drivers/char/Kconfig: > > config VIRTIO_CONSOLE > tristate "Virtio console" > depends on VIRTIO This also has "&& TTY" in -next (not actually relevant) > select HVC_DRIVER Its weird, but since CONFIG_TTY is not set (see the config), the HVC_DRIVER symbol is not even visible, so I suspect that the above select does nothing :-( But also, I can't see how VIRTIO_CONSOLE could be set in the first place since TTY is not set. (cc'ing some more people) (this is a randconfig that has TTY=n, HVC_DRIVER=n, but VIRTIO_CONSOLE=y) -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpoK2yTEsPCF.pgp Description: PGP signature
Re: linux-next: Tree for Feb 13 (virtio_console)
Randy Dunlap writes: > On 02/13/13 00:35, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20130212: > > on i386: > > drivers/built-in.o: In function `in_intr': > virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' > virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' > drivers/built-in.o: In function `resize_console': > virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize' > drivers/built-in.o: In function `unplug_port': > virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove' > drivers/built-in.o: In function `init_port_console': > (.text+0x2fe59): undefined reference to `hvc_alloc' > drivers/built-in.o: In function `virtio_cons_early_init': > (.init.text+0x16d1): undefined reference to `hvc_instantiate' > > > Full randconfig file is attached. This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but CONFIG_HVC_DRIVER isn't set. >From drivers/char/Kconfig: config VIRTIO_CONSOLE tristate "Virtio console" depends on VIRTIO select HVC_DRIVER ??? Cheers, Rusty. -- 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 Feb 13 (virtio_console)
Randy Dunlap rdun...@infradead.org writes: On 02/13/13 00:35, Stephen Rothwell wrote: Hi all, Changes since 20130212: on i386: drivers/built-in.o: In function `in_intr': virtio_console.c:(.text+0x2dd31): undefined reference to `hvc_poll' virtio_console.c:(.text+0x2dd41): undefined reference to `hvc_kick' drivers/built-in.o: In function `resize_console': virtio_console.c:(.text+0x2e26f): undefined reference to `__hvc_resize' drivers/built-in.o: In function `unplug_port': virtio_console.c:(.text+0x2e572): undefined reference to `hvc_remove' drivers/built-in.o: In function `init_port_console': (.text+0x2fe59): undefined reference to `hvc_alloc' drivers/built-in.o: In function `virtio_cons_early_init': (.init.text+0x16d1): undefined reference to `hvc_instantiate' Full randconfig file is attached. This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but CONFIG_HVC_DRIVER isn't set. From drivers/char/Kconfig: config VIRTIO_CONSOLE tristate Virtio console depends on VIRTIO select HVC_DRIVER ??? Cheers, Rusty. -- 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 Feb 13 (virtio_console)
Hi Rusty, On Thu, 14 Feb 2013 13:30:37 +1030 Rusty Russell ru...@rustcorp.com.au wrote: This looks like an impossible config. CONFIG_VIRTIO_CONSOLE=y, but CONFIG_HVC_DRIVER isn't set. From drivers/char/Kconfig: config VIRTIO_CONSOLE tristate Virtio console depends on VIRTIO This also has TTY in -next (not actually relevant) select HVC_DRIVER Its weird, but since CONFIG_TTY is not set (see the config), the HVC_DRIVER symbol is not even visible, so I suspect that the above select does nothing :-( But also, I can't see how VIRTIO_CONSOLE could be set in the first place since TTY is not set. (cc'ing some more people) (this is a randconfig that has TTY=n, HVC_DRIVER=n, but VIRTIO_CONSOLE=y) -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpoK2yTEsPCF.pgp Description: PGP signature
