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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190206212259.GA28490@agluck-desk>
Date:   Wed, 6 Feb 2019 13:23:00 -0800
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Edac Mailing List <linux-edac@...r.kernel.org>
Subject: 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.text+0x11): undefined reference to `adxl_get_component_names'
> 
> 
> CONFIG_EDAC_I10NM=y
> but CONFIG_EDAC_SKX is not set.
> since # CONFIG_ACPI is not set
> 
> Should EDAC_I10NM depend on ACPI also?


Yes it should.

Boris applied a patch to fix this to his "for-next" branch today. So
this should be all fixed when linux-next does a new build.

-Tony