From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10221] Buildroot Support
Date: Fri, 11 Aug 2017 01:50:10 +0000 [thread overview]
Message-ID: <bug-10221-163-YsWmc3UTcy@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10221-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10221
Carlos Santos <casantos@datacom.ind.br> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
Assignee|unassigned at buildroot.uclibc |casantos at datacom.ind.br
|.org |
--- Comment #1 from Carlos Santos <casantos@datacom.ind.br> ---
Please use the buildroot mailing list to ask questions, not the bug tracking
system:
http://www.buildroot.org/downloads/manual/manual.html#community-resources
By the way, Cortex M7 is not supported but Cortex M4, which is also am ARMv7E-M
architecture, is supported.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-08-11 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 12:13 [Buildroot] [Bug 10221] New: Buildroot Support bugzilla at busybox.net
2017-08-11 1:50 ` bugzilla at busybox.net [this message]
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=bug-10221-163-YsWmc3UTcy@https.bugs.busybox.net/ \
--to=bugzilla@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 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.