From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001537]: kexec doesn't build for arm/armeb
Date: Tue, 16 Oct 2007 22:33:00 -0700 [thread overview]
Message-ID: <9e896385eff33f3870e5581612e438ff@bugs.uclibc.org> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1537
======================================================================
Reported By: hmoffatt
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1537
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 10-16-2007 22:32 PDT
Last Modified: 10-16-2007 22:33 PDT
======================================================================
Summary: kexec doesn't build for arm/armeb
Description:
kexec doesn't build on arm or armeb.
Problems are:
1. armeb not a supported architecture;
2. arm support patch needs to be updated due to an internal API change.
Fix is trivial - attached.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
10-16-07 22:32 hmoffatt New Issue
10-16-07 22:32 hmoffatt Status new => assigned
10-16-07 22:32 hmoffatt Assigned To => buildroot
10-16-07 22:33 hmoffatt File Added: kexec-arm-fix
======================================================================
next reply other threads:[~2007-10-17 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 5:33 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 4:43 [Buildroot] [buildroot 0001537]: kexec doesn't build for arm/armeb bugs at busybox.net
2007-10-18 5:27 bugs at busybox.net
2007-10-19 21:32 ` Bernhard Fischer
2007-10-30 21:44 bugs at busybox.net
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=9e896385eff33f3870e5581612e438ff@bugs.uclibc.org \
--to=bugs@busybox.net \
--cc=buildroot@busybox.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