From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xtensa support ?
Date: Wed, 19 Feb 2014 09:04:57 +0100 [thread overview]
Message-ID: <20140219090457.4816d674@skate> (raw)
In-Reply-To: <5303F9B4.60102@zankel.net>
Dear Chris Zankel,
On Tue, 18 Feb 2014 16:24:20 -0800, Chris Zankel wrote:
> Unfortunately, I have been really busy with another project and won't
> have much time to look into it for another week or so.
I am not really worried about the immediate future (i.e the coming
week), but more in the mid to long term future.
> Max has been working on Xtensa a lot, so maybe he can step in?
We'll be definitely happy to receive contributions from Max. Max, do
you want to receive a daily e-mail that lists the Xtensa build issues
(no mail is sent when there are no Xtensa build issues during the day).
> If the autobuilder supports multiple recipients, it would be great if
> you could still keep me in that list, though.
I can send the e-mail to as many recipients as I want, so I'll
definitely keep you in the list.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-19 8:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-13 Thomas Petazzoni
2014-02-14 9:12 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2014-02-14 10:23 ` Anton Kolesov
2014-02-14 14:13 ` Thomas Petazzoni
2014-02-14 14:42 ` Peter Korsgaard
2014-02-14 15:19 ` Thomas Petazzoni
2014-02-14 17:05 ` Anton Kolesov
2014-02-14 17:42 ` Thomas Petazzoni
2014-02-14 11:29 ` Peter Korsgaard
2014-02-14 13:15 ` Ezequiel García
2014-02-15 7:27 ` Frank Bergmann
2014-02-15 17:29 ` Frank Bergmann
2014-02-15 18:52 ` [Buildroot] [PATCH 1/1] e2fsprogs: fix missing fallocate64() on nios2 Frank Bergmann
2014-02-18 21:19 ` Thomas Petazzoni
2014-02-18 23:13 ` Frank Bergmann
2014-02-20 20:52 ` Frank Bergmann
2014-02-27 13:35 ` Peter Korsgaard
2014-02-15 21:31 ` [Buildroot] Analysis of build failures Baruch Siach
2014-02-18 21:22 ` [Buildroot] Xtensa support ? Thomas Petazzoni
2014-02-19 0:24 ` Chris Zankel
2014-02-19 8:04 ` Thomas Petazzoni [this message]
[not found] ` <CAMo8Bf+gfdgfV+XFows8HmppvXdL=VWXGG_givbUNerep0zeHg@mail.gmail.com>
2014-02-19 13:19 ` Thomas Petazzoni
2014-02-19 5:26 ` Jonathan Ben Avraham
2014-02-19 8:05 ` Thomas Petazzoni
2014-02-19 8:16 ` Jonathan Ben Avraham
2014-02-19 8:22 ` Thomas Petazzoni
2014-02-16 0:00 ` [Buildroot] Analysis of build failures Romain Naour
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=20140219090457.4816d674@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