From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Microblaze maintenance in Buildroot
Date: Sun, 6 Apr 2014 15:42:14 +0200 [thread overview]
Message-ID: <20140406154214.27160264@skate> (raw)
Hello all,
You're receiving this e-mail because you've at one point or another
expressed interest in the Microblaze support in Buildroot.
We have a number of Microblaze related failures in the autobuilders,
but for the moment, only Spenser is receiving each day the
notifications of Microblaze failures, and he has not been very active
lately in terms of Buildroot contribution.
Would any (or several) of you be willing to receive these notifications
(one e-mail per day) and provide patches to fix Microblaze related
problems?
Generally, I'm also interested in having a group of people take care of
the Microblaze architecture in Buildroot. There are a few outstanding
patches initially posted by Spenser in January (to update
gcc/binutils/gdb, etc.) that received some comments, but Spenser never
got back with updated versions of those patches.
Anybody interested?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2014-04-06 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 13:42 Thomas Petazzoni [this message]
2014-04-06 17:22 ` [Buildroot] Microblaze maintenance in Buildroot Spenser Gilliland
2014-04-06 17:29 ` Thomas Petazzoni
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=20140406154214.27160264@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox