From: Magnus Damm <magnus@valinux.co.jp>
To: Ian Campbell <Ian.Campbell@xensource.com>
Cc: xen-devel@lists.xensource.com, magnus.damm@gmail.com,
Akio Takebe <takebe_akio@jp.fujitsu.com>,
Magnus Damm <magnus@valinux.co.jp>,
Alex Williamson <alex.williamson@hp.com>
Subject: [PATCH 02/02] Kexec / Kdump: Don't declare _end
Date: Mon, 04 Dec 2006 13:35:38 +0900 [thread overview]
Message-ID: <20061204043538.25410.29650.sendpatchset@localhost> (raw)
In-Reply-To: <20061204043528.25410.42087.sendpatchset@localhost>
[PATCH 02/02] Kexec / Kdump: Don't declare _end
_end is already declared in xen/include/asm/config.h, so don't declare
it twice. This solves a powerpc/ia64 build problem where _end is declared
as char _end[] compared to unsigned long _end on x86.
Signed-Off-By: Magnus Damm <magnus@valinux.co.jp>
---
Applies on top of xen-unstable-12717.
xen/common/kexec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- 0001/xen/common/kexec.c
+++ work/xen/common/kexec.c 2006-12-04 12:45:57.000000000 +0900
@@ -158,7 +158,7 @@ static int kexec_get_reserve(xen_kexec_r
return 0;
}
-extern unsigned long _text, _end;
+extern unsigned long _text;
static int kexec_get_xen(xen_kexec_range_t *range, int get_ma)
{
@@ -167,7 +167,7 @@ static int kexec_get_xen(xen_kexec_range
else
range->start = (unsigned long) &_text;
- range->size = &_end - &_text;
+ range->size = (unsigned long)&_end - (unsigned long)&_text;
return 0;
}
next prev parent reply other threads:[~2006-12-04 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 4:35 [PATCH 00/02] Kexec / Kdump: ia64 build fixes Magnus Damm
2006-12-04 4:35 ` [PATCH 01/02] Kexec / Kdump: Use NOTE_ALIGN() instead of ALIGN() Magnus Damm
2006-12-04 4:35 ` Magnus Damm [this message]
2006-12-04 17:45 ` [PATCH 02/02] Kexec / Kdump: Don't declare _end Ian Campbell
2006-12-05 6:55 ` Magnus Damm
2006-12-04 9:18 ` [PATCH 00/02] Kexec / Kdump: ia64 build fixes Ian Campbell
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=20061204043538.25410.29650.sendpatchset@localhost \
--to=magnus@valinux.co.jp \
--cc=Ian.Campbell@xensource.com \
--cc=alex.williamson@hp.com \
--cc=magnus.damm@gmail.com \
--cc=takebe_akio@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.