From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 2] Introduction of Amlogic platform to buildroot
Date: Sat, 2 Nov 2013 16:36:48 +0100 [thread overview]
Message-ID: <20131102163648.4e4018a4@skate> (raw)
In-Reply-To: <l5361q$d6q$2@ger.gmane.org>
Dear Stanislav Vasic,
On Sat, 2 Nov 2013 15:34:18 +0000 (UTC), Stanislav Vasic wrote:
> From 5d941e3307401d261b817a3aa40fe75894050419 Mon Sep 17 00:00:00 2001
> From: Stanislav Vasic <svlasic@gmail.com>
> Date: Sat, 2 Nov 2013 14:52:14 +0100
> Subject: [PATCH] Re-add Linaro 2013.04 toolchain
>
> Linaro 2013.04 toolchain is dependency for Amlogic platform
> because none of current Amlogic kernels are failing to boot
> when compiled with GCC higher than 4.7
> ---
> toolchain/toolchain-external/Config.in | 21 +++++++++++++++++
> ++++
> toolchain/toolchain-external/toolchain-external.mk | 4 ++++
> 2 files changed, 25 insertions(+)
Your entire patch is severely line-wrapped, making it unusable. Can you
use 'git send-email' to send your patches instead?
See
http://buildroot.org/downloads/manual/manual.html#submitting-patches
for details.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-02 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADYw_J+dw+E6xCosXu=hOo172ZPu1QJgtVTrHmJEQ2eVa6BWWg@mail.gmail. com>
2013-11-02 15:34 ` [Buildroot] [PATCH 1 of 2] Introduction of Amlogic platform to buildroot Stanislav Vasic
2013-11-02 15:36 ` Thomas Petazzoni [this message]
2013-11-02 15:35 ` [Buildroot] [PATCH 2 " Stanislav Vasic
2013-11-02 15:54 ` Thomas Petazzoni
2013-11-02 16:10 ` Stanislav Vasic
2013-11-02 16:20 ` Thomas Petazzoni
2013-11-02 20:49 ` Stanislav Vasic
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=20131102163648.4e4018a4@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.