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: blackfin: Remove Blackfin toolchain 2011R1 release.
Date: Tue, 14 May 2013 09:42:14 +0200	[thread overview]
Message-ID: <20130514094214.1414d216@skate> (raw)
In-Reply-To: <CAJxxZ0MT5top5C8-jMMrqeSOiSpeMvLDVXx5f3EmU4gZSX6kPQ@mail.gmail.com>

Dear Sonic Zhang,

On Tue, 14 May 2013 15:32:05 +0800, Sonic Zhang wrote:

> On Wed, Apr 10, 2013 at 3:50 PM, Sonic Zhang <sonic.adi@gmail.com> wrote:
> > From: Sonic Zhang <sonic.zhang@analog.com>
> >
> > Blackfin is supported in buildroot since 2012R1 release.
> >
> > Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> 
> Could you Acked-by this patch at least for -next tree?

Honestly, I don't understand this patch, and the commit log doesn't
explain much about it.

2012R1 is not a Buildroot version.

And Blackfin toolchains were supported in Buildroot before the 2012R1
release of the Blackfin toolchains.

Could you point to specific problems with this toolchain, or give a
more precise commit log?

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-05-14  7:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  7:50 [Buildroot] [PATCH] toolchain: blackfin: Remove Blackfin toolchain 2011R1 release Sonic Zhang
2013-05-14  7:32 ` Sonic Zhang
2013-05-14  7:42   ` Thomas Petazzoni [this message]
2013-05-14  7:57     ` Sonic Zhang
2013-05-14 15: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=20130514094214.1414d216@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