From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help to fix Microblaze issues in Buildroot
Date: Wed, 20 Nov 2013 15:18:43 +0100 [thread overview]
Message-ID: <20131120151843.0bd4d834@skate> (raw)
In-Reply-To: <CAM+bi4uLpkQjiQ3nh7oDd+kOPPjPUq2na6A9fnCCDG4fbV=DUg@mail.gmail.com>
Dear Alvaro Gamez,
On Wed, 20 Nov 2013 15:15:07 +0100, Alvaro Gamez wrote:
> Sorry, no, I didn't read much and run wildly and foolishly to apply
> as few patches as possible, for I've been very disconnected from
> buildroot development for months, so I wasn't really following the
> dependencies between patches. In retrospect, that was unwise.
>
> For what it's worth, if by simply renaming and recompressing some
> files I've managed to build a microblaze system with only Spenser's
> patches applied to master... that seems to mean that everything is
> working really great.
Great, thanks for the testing!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-20 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 16:54 [Buildroot] Help to fix Microblaze issues in Buildroot Thomas Petazzoni
[not found] ` <CAM+bi4vGmKHRA3j0ua-dsOBzTuj-BPrM2+z3papeyfDjjazhgw@mail.gmail.com>
2013-11-20 10:03 ` Alvaro Gamez
2013-11-20 10:10 ` Thomas Petazzoni
2013-11-20 10:28 ` Thomas De Schampheleire
2013-11-20 10:32 ` Alvaro Gamez
2013-11-20 10:36 ` Alvaro Gamez
2013-11-20 10:41 ` Thomas Petazzoni
2013-11-20 12:40 ` Spenser Gilliland
2013-11-20 13:56 ` Alvaro Gamez
2013-11-20 14:00 ` Spenser Gilliland
2013-11-20 14:09 ` Thomas Petazzoni
2013-11-20 14:15 ` Alvaro Gamez
2013-11-20 14:18 ` Thomas Petazzoni [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=20131120151843.0bd4d834@skate \
--to=thomas.petazzoni@free-electrons.com \
--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.