On 11/30/21 21:37, Stephen Rothwell wrote: > Hi all, > > Changes since 20211130: > > The fscache tree gained a conflict against Linus' tree. > > The tip tree still has its build failure for which I reverted 2 commits. > > The gpio-brgl tree still had its build failure so I used the version from > next-20211115. > > The akpm tree still had its boot failure for which I reverted 6 commits. > It also gained a build failure for which I applied a patch. > > Non-merge commits (relative to Linus' tree): 4036 > 4605 files changed, 187261 insertions(+), 88751 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, > arm64, 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 344 trees (counting Linus' and 94 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. > on i386 or x86_64: when # CONFIG_PACKING is not set ld: drivers/net/ethernet/microchip/lan966x/lan966x_main.o: in function `lan966x_xtr_irq_handler': lan966x_main.c:(.text+0x5ea): undefined reference to `packing' ld: lan966x_main.c:(.text+0x611): undefined reference to `packing' ld: drivers/net/ethernet/microchip/lan966x/lan966x_main.o: in function `lan966x_port_xmit': lan966x_main.c:(.text+0x7f5): undefined reference to `packing' ld: lan966x_main.c:(.text+0x82e): undefined reference to `packing' ld: lan966x_main.c:(.text+0x86f): undefined reference to `packing' ld: drivers/net/ethernet/microchip/lan966x/lan966x_main.o:lan966x_main.c:(.text+0x8b1): more undefined references to `packing' follow Please add select PACKING to the driver's Kconfig entry. -- ~Randy
