public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Edac Mailing List <linux-edac@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 6 (drivers/edac/skx* and i10nm)
Date: Wed, 6 Feb 2019 13:23:00 -0800	[thread overview]
Message-ID: <20190206212259.GA28490@agluck-desk> (raw)
In-Reply-To: <3f095f3e-ace0-aadb-ead1-01908da5c08c@infradead.org>

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

      parent reply	other threads:[~2019-02-06 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  6:00 linux-next: Tree for Feb 6 Stephen Rothwell
2019-02-06 21:11 ` linux-next: Tree for Feb 6 (drivers/edac/skx* and i10nm) Randy Dunlap
2019-02-06 21:22   ` Borislav Petkov
2019-02-06 21:23   ` Luck, Tony [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190206212259.GA28490@agluck-desk \
    --to=tony.luck@intel.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox