From: Nishanth Aravamudan <nacc@us.ibm.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
ebiederm@xmission.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Fix kexec-related UP build error
Date: Fri, 15 Apr 2011 14:00:51 -0700 [thread overview]
Message-ID: <20110415210051.GA31245@us.ibm.com> (raw)
In-Reply-To: <20110415202916.GA6758@linux.vnet.ibm.com>
Hi Paul,
On 15.04.2011 [13:29:16 -0700], Paul E. McKenney wrote:
> Hello!
>
> The following patch fixes a UP build problem for kexec() on powerpc.
> When the crash_kexec_wait_realmode() function was added, it was
> placed in only two of the three required locations.
I believe the fix has already been posted as
http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-April/089559.html
Thanks,
Nish
next prev parent reply other threads:[~2011-04-15 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 20:29 [PATCH] powerpc: Fix kexec-related UP build error Paul E. McKenney
2011-04-15 21:00 ` Nishanth Aravamudan [this message]
2011-04-15 21:08 ` Paul E. McKenney
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=20110415210051.GA31245@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
/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).