Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: Update Sourcery CodeBench MIPS toolchain
Date: Tue, 17 Sep 2013 20:14:57 +0200	[thread overview]
Message-ID: <20130917201457.31b7772c@skate> (raw)
In-Reply-To: <1379408657-18335-1-git-send-email-markos.chandras@imgtec.com>

Dear Markos Chandras,

On Tue, 17 Sep 2013 10:04:17 +0100, Markos Chandras wrote:
> Update to the latest update for the 2013.05 toolchain
> released on 11 September 2013.
> 
> https://sourcery.mentor.com/GNUToolchain/release2554
> 
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>

Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-09-17 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  9:04 [Buildroot] [PATCH] toolchain-external: Update Sourcery CodeBench MIPS toolchain Markos Chandras
2013-09-17 18:14 ` Thomas Petazzoni [this message]
2013-09-17 21:22 ` Peter Korsgaard

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=20130917201457.31b7772c@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