Re: linux-next: Tree for Feb 6 (drivers/edac/skx* and i10nm)

On Wed, Feb 06, 2019 at 01:11:23PM -0800, Randy Dunlap wrote: > on x86_64: > > ld: drivers/edac/skx_common.o: in function `skx_mce_check_error': > skx_common.c:(.text+0x982): undefined reference to `adxl_decode' > ld: drivers/edac/skx_common.o: in function `skx_adxl_get': > skx_common.c:(.init.tex

Re: linux-next: Tree for Feb 6 (drivers/edac/skx* and i10nm)

On Wed, Feb 06, 2019 at 01:11:23PM -0800, Randy Dunlap wrote: > CONFIG_EDAC_I10NM=y > but CONFIG_EDAC_SKX is not set. > since # CONFIG_ACPI is not set > > Should EDAC_I10NM depend on ACPI also? This should do it: https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/commit/?h=for-next&id=d6a

Re: linux-next: Tree for Feb 6 (drivers/edac/skx* and i10nm)

On 2/5/19 10:00 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20190205: > > The mips tree gained conflicts against the mips-fixes tree. > > The opp tree gained a conflict against the pm tree. > > The drm-intel tree gained a conflict against the drm tree. > > The akpm-current tree gai