From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7580] Invalid filesystem in Pandaboard defconfig
Date: Mon, 07 Mar 2016 20:24:20 +0000 [thread overview]
Message-ID: <bug-7580-163-1Rtqfv374n@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-7580-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=7580
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|REOPENED |RESOLVED
--- Comment #11 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Fixed by commit:
commit 000b972f49bcf9ed35417bb787a4440f22b12f8e
Author: Sergio Prado <sergio.prado@e-labworks.com>
Date: Tue Feb 9 16:14:52 2016 -0200
configs: pandaboard: bump u-boot to 2015.10 and kernel to 4.3
VFPv3 and NEON was enabled and a readme.txt file was added.
Fixes bug #7580.
Tested on Pandaboard ES.
[Peter: use EABIhf]
Signed-off-by: Sergio Prado <sergio.prado@e-labworks.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-03-07 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 0:40 [Buildroot] [Bug 7580] New: Invalid filesystem in Pandaboard defconfig bugzilla at busybox.net
2014-10-30 1:14 ` [Buildroot] [Bug 7580] " bugzilla at busybox.net
2014-11-07 7:27 ` bugzilla at busybox.net
2014-11-08 11:31 ` bugzilla at busybox.net
2014-11-09 13:23 ` bugzilla at busybox.net
2014-11-09 16:38 ` bugzilla at busybox.net
2014-11-10 9:17 ` bugzilla at busybox.net
2014-11-12 21:33 ` bugzilla at busybox.net
2014-11-12 21:34 ` bugzilla at busybox.net
2015-12-24 16:51 ` bugzilla at busybox.net
2015-12-25 17:32 ` bugzilla at busybox.net
2016-03-07 20:24 ` 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-7580-163-1Rtqfv374n@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox