From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Borislav Petkov <borislav.petkov@amd•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
"H. Peter Anvin" <hpa@zytor•com>
Subject: Re: linux-next: Tree for December 16 (amd64_edac)
Date: Wed, 16 Dec 2009 09:24:24 -0800 [thread overview]
Message-ID: <20091216092424.5f87214c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091216183212.118c5e14.sfr@canb.auug.org.au>
On Wed, 16 Dec 2009 18:32:12 +1100 Stephen Rothwell wrote:
> Hi all,
>
> My usual call for calm: please do not put stuff destined for 2.6.34 into
> linux-next trees until after 2.6.33-rc1.
>
> Changes since 20091215:
When CONFIG_SMP=n, CONFIG_X86_MSR=m:
ERROR: "msrs_free" [drivers/edac/amd64_edac_mod.ko] undefined!
ERROR: "msrs_alloc" [drivers/edac/amd64_edac_mod.ko] undefined!
Should EDAC_AMD64 also depend on SMP?
---
~Randy
next prev parent reply other threads:[~2009-12-16 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 7:32 linux-next: Tree for December 16 Stephen Rothwell
2009-12-16 17:24 ` Randy Dunlap [this message]
2009-12-16 17:32 ` linux-next: Tree for December 16 (amd64_edac) H. Peter Anvin
2009-12-16 17:45 ` Borislav Petkov
2009-12-16 18:36 ` H. Peter Anvin
2009-12-16 21:51 ` [PATCH -next] x86 msrs: alloc/free for CONFIG_SMP=n Randy Dunlap
2009-12-16 21:58 ` Borislav Petkov
2009-12-16 22:02 ` Randy Dunlap
2009-12-16 22:41 ` H. Peter Anvin
2009-12-16 23:16 ` Borislav Petkov
2009-12-16 21:54 ` linux-next: Tree for December 16 (amd64_edac) Borislav Petkov
2009-12-16 22:26 ` [PATCH -next] power: fix printk formats Randy Dunlap
2009-12-16 22:35 ` Rafael J. Wysocki
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=20091216092424.5f87214c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=borislav.petkov@amd$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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