From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] trinity: Disable for Microblaze architecture
Date: Mon, 27 Oct 2014 17:19:36 +0000 [thread overview]
Message-ID: <544E7EA8.7030207@imgtec.com> (raw)
In-Reply-To: <20141027174348.0d4bcccb@free-electrons.com>
Dear Thomas Petazzoni,
On 10/27/2014 04:43 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
>
> On Mon, 27 Oct 2014 16:11:10 +0000, Vicente Olivert Riera wrote:
>> This package doesn't support the Microblaze architecture. The full list
>> of supported architectures is in the trinity website, and Microblaze is
>> not among them.
>
> Then what we want is not something like the patch you propose, but
> instead a patch using positive logic to enable Trinity only on the
> architecture that are known to work.
>
> The website says: "Trinity supports Alpha, Aarch64, ARM, i386, IA-64,
> MIPS, PowerPC-64, S390, S390x, SPARC-64, x86-64.". So it means that not
> only Microblaze is going to cause issue, but also Blackfin, ARC,
> Xtensa, SPARC 32 bits, and probably some others I forgot.
>
> Can you respin the patch with something like:
>
> depends BR2_... || BR2_... || BR2_...
>
> Thanks!
>
> Thomas
Done: http://patchwork.ozlabs.org/patch/403703/
I have marked the former patch as superseded.
Best regards,
--
Vicente Olivert Riera
Graduate Software Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
next prev parent reply other threads:[~2014-10-27 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 16:11 [Buildroot] [PATCH] trinity: Disable for Microblaze architecture Vicente Olivert Riera
2014-10-27 16:43 ` Thomas Petazzoni
2014-10-27 17:19 ` Vicente Olivert Riera [this message]
2014-10-27 18:30 ` Thomas Petazzoni
2014-10-28 9:31 ` Vicente Olivert Riera
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=544E7EA8.7030207@imgtec.com \
--to=vincent.riera@imgtec.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