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 v2 1/4] toolchain-external: Remove BLACKFIN_UCLINUX_2012R2
Date: Sun, 4 Oct 2015 16:19:05 +0100	[thread overview]
Message-ID: <20151004161905.60263d38@free-electrons.com> (raw)
In-Reply-To: <1443901828-11390-1-git-send-email-maxime.hadjinlian@gmail.com>

Dear Maxime Hadjinlian,

On Sat,  3 Oct 2015 21:50:25 +0200, Maxime Hadjinlian wrote:
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> ---
>  toolchain/toolchain-external/Config.in             | 19 -------------------
>  toolchain/toolchain-external/toolchain-external.mk |  8 ++------
>  2 files changed, 2 insertions(+), 25 deletions(-)

Patches 1 to 3 applied. However patch 4 not applied since the "select
BR2_PACKAGE_LIBTIRPC" is not needed and the same change should be done
in mpd (and possibly other reverse dependencies of libnfs, if any other
than kodi and mpd).

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2015-10-04 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03 19:50 [Buildroot] [PATCH v2 1/4] toolchain-external: Remove BLACKFIN_UCLINUX_2012R2 Maxime Hadjinlian
2015-10-03 19:50 ` [Buildroot] [PATCH v2 2/4] blackfin: 2012R2 toolchain is gone, remove kludges Maxime Hadjinlian
2015-10-03 20:49   ` Arnout Vandecappelle
2015-10-03 19:50 ` [Buildroot] [PATCH v2 3/4] libnfs: Without native RPC use libtirpc Maxime Hadjinlian
2015-10-03 20:50   ` Arnout Vandecappelle
2015-10-03 19:50 ` [Buildroot] [PATCH v2 4/4] kodi: " Maxime Hadjinlian
2015-10-03 20:41 ` [Buildroot] [PATCH v2 1/4] toolchain-external: Remove BLACKFIN_UCLINUX_2012R2 Arnout Vandecappelle
2015-10-04 15:19 ` Thomas Petazzoni [this message]

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=20151004161905.60263d38@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