On 5/23/19 9:07 PM, Stephen Rothwell wrote: > Hi all, > > News: there will be no linux-next release on Monday. > > Changes since 20190523: > > The input-current tree gained a build failure so I reverted a commit. > > The drm-fixes tree gained a build failure so I reverted a commit. > > The v4l-dvb tree gained a conflict against Linus' tree. > > Non-merge commits (relative to Linus' tree): 1814 > 1870 files changed, 61172 insertions(+), 32723 deletions(-) > > ---------------------------------------------------------------------------- > > I have created today's linux-next tree at > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you > are tracking the linux-next tree using git, you should not use "git pull" > to do so as that will try to merge the new linux-next release with the > old one. You should use "git fetch" and checkout or reset to the new > master. > > You can see which trees have been included by looking in the Next/Trees > file in the source. There are also quilt-import.log and merge.log > files in the Next directory. Between each merge, the tree was built > with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a > multi_v7_defconfig for arm and a native build of tools/perf. After > the final fixups (if any), I do an x86_64 modules_install followed by > builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), > ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc > and sparc64 defconfig. And finally, a simple boot test of the powerpc > pseries_le_defconfig kernel in qemu (with and without kvm enabled). > > Below is a summary of the state of the merge. > > I am currently merging 290 trees (counting Linus' and 70 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. > seen on i386: ld: drivers/leds/leds-lm3697.o: in function `lm3697_probe': leds-lm3697.c:(.text+0x451): undefined reference to `devm_of_led_classdev_register' CONFIG_LEDS_CLASS=m CONFIG_LEDS_TI_LMU_COMMON=y CONFIG_LEDS_LM3697=y It looks to me like this is needed: depends on LEDS_CLASS && I2C && OF ? -- ~Randy
