On Tue, Apr 20, 2021 at 07:47:18PM +1000, Stephen Rothwell wrote: > Hi all, > > Changes since 20210419: > > The powerpc tree lost its build failure. > > The ftrace tree gained a conflict against the bpf-next tree. > > Non-merge commits (relative to Linus' tree): 12917 > 11294 files changed, 619161 insertions(+), 276245 deletions(-) > > ---------------------------------------------------------------------------- > > I have created today's linux-next tree at > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you > are tracking the linux-next tree using git, you should not use "git pull" > to do so as that will try to merge the new linux-next release with the > old one. You should use "git fetch" and checkout or reset to the new > master. > > You can see which trees have been included by looking in the Next/Trees > file in the source. There are also quilt-import.log and merge.log > files in the Next directory. Between each merge, the tree was built > with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a > multi_v7_defconfig for arm and a native build of tools/perf. After > the final fixups (if any), I do an x86_64 modules_install followed by > builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), > ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc > and sparc64 defconfig and htmldocs. And finally, a simple boot test > of the powerpc pseries_le_defconfig kernel in qemu (with and without > kvm enabled). > > Below is a summary of the state of the merge. > > I am currently merging 340 trees (counting Linus' and 89 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. I have full of build warnings / errors in x86 and iommu X86: arch/x86/include/asm/string_64.h:14:14: warning: conflicting types for built-in function ‘memcpy’; expected ‘void *(void *, const void *, long unsigned int)’ [-Wbuiltin-declaration-mismatch] 14 | extern void *memcpy(void *to, const void *from, size_t len); | ^~~~~~ arch/x86/include/asm/string_64.h:7:1: note: ‘memcpy’ is declared in header ‘<string.h>’ 6 | #include <linux/jump_label.h> +++ |+#include <string.h> And so on for standard string function definitions. IOMMU: drivers/iommu/amd/io_pgtable.c: In function ‘v1_alloc_pgtable’: drivers/iommu/amd/io_pgtable.c:551:32: error: assignment to ‘size_t (*)(struct io_pgtable_ops *, long unsigned int, size_t, struct iommu_iotlb_gather *)’ {aka ‘unsigned int (*)(struct io_pgtable_ops *, long unsigned int, unsigned int, struct iommu_iotlb_gather *)’} from incompatible pointer type ‘long unsigned int (*)(struct io_pgtable_ops *, long unsigned int, size_t, struct iommu_iotlb_gather *)’ {aka ‘long unsigned int (*)(struct io_pgtable_ops *, long unsigned int, unsigned int, struct iommu_iotlb_gather *)’} [-Werror=incompatible-pointer-types] 551 | pgtable->iop.ops.unmap = iommu_v1_unmap_page; | ^ cc1: some warnings being treated as errors Is it only me? -- With Best Regards, Andy Shevchenko
