linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	borislav.petkov@amd.com, dougthompson@xmission.com
Subject: Re: linux-next: Tree for May 20 (amd64_edac)
Date: Wed, 20 May 2009 09:16:09 -0700	[thread overview]
Message-ID: <4A142CC9.4050904@oracle.com> (raw)
In-Reply-To: <20090520170807.b75a9d86.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20090519:
> 
> Undropped tree:
> 	edac-amd
> 
> The edac-amd tree lost its build failure.


When K8_NB is not enabled:

drivers/built-in.o: In function `amd64_edac_init':
amd64_edac.c:(.init.text+0x254f6): undefined reference to `cache_k8_northbridges'
amd64_edac.c:(.init.text+0x25c38): undefined reference to `num_k8_northbridges'


Error with EDAC_AMD64 =y or =m.
Error on both i386 and on x86_64.


Comments on Kconfig for EDAC_AMD64:

config EDAC_AMD64
	tristate "AMD64 (Opteron, Athlon64) K8, F10h, F11h"
	depends on EDAC_MM_EDAC && X86 && PCI
	default m
	help
	Support for error detection and correction on the AMD 64
	Families of Memory Controllers (K8, F10h and F11h)


Does this actually apply to X86_32 or should the depends be on
X86_64 instead of X86?

The default y on EDAC_MM_EDAC and default m on EDAC_AMD64 should
be removed.

The 2 lines of help text should be indented by 2 spaces.

Would be Good to have the amd64_edac maintainer(s) email addresses
in MAINTAINERS file, please.

-- 
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

  reply	other threads:[~2009-05-20 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  7:08 linux-next: Tree for May 20 Stephen Rothwell
2009-05-20 16:16 ` Randy Dunlap [this message]
2009-05-20 16:41   ` linux-next: Tree for May 20 (amd64_edac) Borislav Petkov
2009-05-20 16:51     ` Randy Dunlap
2009-05-20 17:17       ` Borislav Petkov

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=4A142CC9.4050904@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=borislav.petkov@amd.com \
    --cc=dougthompson@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).