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>
Subject: Re: linux-next: Tree for November 26 (kexec/percpu/non-SMP)
Date: Thu, 26 Nov 2009 22:02:38 -0800 [thread overview]
Message-ID: <4B0F6B7E.8000904@oracle.com> (raw)
In-Reply-To: <20091126203837.b64fb4d3.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20091125:
in drivers/base/cpu.c, when CONFIG_SMP=n, per_cpu_ptr_to_phys() is not available
(inside #ifdef CONFIG_KEXEC):
in function show_crash_notes():
addr = per_cpu_ptr_to_phys(per_cpu_ptr(crash_notes, cpunum));
drivers/base/cpu.c:100: error: implicit declaration of function 'per_cpu_ptr_to_phys'
--
~Randy
next prev parent reply other threads:[~2009-11-27 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 9:38 linux-next: Tree for November 26 Stephen Rothwell
2009-11-27 6:02 ` Randy Dunlap [this message]
2009-11-27 6:22 ` [PATCH -next] misc/eeprom: fix at24 printk format Randy Dunlap
2009-11-27 6:46 ` Stephen Rothwell
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=4B0F6B7E.8000904@oracle.com \
--to=randy.dunlap@oracle.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).