From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support
Date: Sun, 7 Dec 2014 23:48:35 +0100 [thread overview]
Message-ID: <20141207234835.4fac269f@free-electrons.com> (raw)
In-Reply-To: <1416266092-6465-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 17 Nov 2014 20:14:50 -0300, Gustavo Zacarias wrote:
> Gustavo Zacarias (2):
> arch/powerpc: add fsl e5500 and e6500 support
> package/gcc: set e5500 and e6500 version mask
Patches applied. I must say I'm a bit confused by why we exclude PP64le
for those new platforms. Is there theoretically something that would
prevent those from being used in LE mode?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-07 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 23:14 [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support Gustavo Zacarias
2014-11-17 23:14 ` [Buildroot] [PATCH 1/2] arch/powerpc: add fsl e5500 and " Gustavo Zacarias
2014-11-18 13:56 ` Matthew Weber
2014-11-18 14:28 ` Gustavo Zacarias
2014-11-18 15:20 ` Thomas Petazzoni
2014-11-18 16:28 ` Gustavo Zacarias
2014-11-18 16:56 ` Thomas Petazzoni
2014-11-18 17:00 ` Gustavo Zacarias
2014-11-18 17:04 ` Thomas Petazzoni
2014-11-18 18:31 ` Baruch Siach
2014-11-18 20:59 ` Thomas Petazzoni
2014-11-17 23:14 ` [Buildroot] [PATCH 2/2] package/gcc: set e5500 and e6500 version mask Gustavo Zacarias
2014-12-07 22:48 ` Thomas Petazzoni [this message]
2014-12-07 23:17 ` [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support Gustavo Zacarias
2014-12-07 23:21 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2014-11-20 16:41 Dwayne Fontenot
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=20141207234835.4fac269f@free-electrons.com \
--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