From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Scott Wood <oss@buserror.net>,
Christophe Leroy <christophe.leroy@c-s.fr>
Subject: [PATCH 3/3] powerpc/8xx: xmon compile fix
Date: Fri, 12 May 2017 01:15:22 +1000 [thread overview]
Message-ID: <20170511151522.4772-3-npiggin@gmail.com> (raw)
In-Reply-To: <20170511151522.4772-1-npiggin@gmail.com>
Cc: Scott Wood <oss@buserror.net>
Cc: Christophe Leroy <christophe.leroy@c-s.fr>
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
arch/powerpc/xmon/xmon.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/xmon/xmon.c b/arch/powerpc/xmon/xmon.c
index f11f65634aab..ec420b0e6e88 100644
--- a/arch/powerpc/xmon/xmon.c
+++ b/arch/powerpc/xmon/xmon.c
@@ -1242,10 +1242,13 @@ bpt_cmds(void)
{
int cmd;
unsigned long a;
- int mode, i;
+ int i;
struct bpt *bp;
+#ifndef CONFIG_8xx
+ int mode;
const char badaddr[] = "Only kernel addresses are permitted "
"for breakpoints\n";
+#endif
cmd = inchar();
switch (cmd) {
--
2.11.0
next prev parent reply other threads:[~2017-05-11 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 15:15 [PATCH 1/3] powerpc/powernv: Fix CPU_HOTPLUG=n idle.c compile error Nicholas Piggin
2017-05-11 15:15 ` [PATCH 2/3] powerpc/32: tlbie provide L operand explicitly Nicholas Piggin
2017-05-12 3:35 ` Michael Ellerman
2017-05-12 10:31 ` Nick Piggin
2017-05-11 15:15 ` Nicholas Piggin [this message]
2017-05-11 17:14 ` [PATCH 3/3] powerpc/8xx: xmon compile fix christophe leroy
2017-05-11 18:52 ` christophe leroy
2017-05-11 19:30 ` Nicholas Piggin
2017-05-12 0:47 ` Nicholas Piggin
2017-05-12 5:37 ` Christophe LEROY
2017-05-26 7:24 ` Michael Ellerman
2017-05-26 16:20 ` David Laight
2017-05-29 5:21 ` Michael Ellerman
2017-05-30 9:11 ` [3/3] " Michael Ellerman
2017-05-12 9:19 ` [PATCH 1/3] powerpc/powernv: Fix CPU_HOTPLUG=n idle.c compile error Gautham R Shenoy
2017-05-30 9:11 ` [1/3] " Michael Ellerman
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=20170511151522.4772-3-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
/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).