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] [pull request] Pull request for branch uclibc-arch-type-cleanup
Date: Tue,  4 Sep 2012 15:49:42 +0200	[thread overview]
Message-ID: <cover.1346766545.git.thomas.petazzoni@free-electrons.com> (raw)

Hello,

Here is a simple patch set that moves BR2_ARM_TYPE and BR2_SPARC_TYPE
to a uClibc-specific place, since those are uClibc specific.

Thomas

The following changes since commit 27045cde7d18f6132ab804ed30673e3fb3961879:

  gcc: default to 4.6.x (2012-09-04 13:28:03 +0200)

are available in the git repository at:

  git://git.free-electrons.com/users/thomas-petazzoni/buildroot.git uclibc-arch-type-cleanup

for you to fetch changes up to 10451abfa0e2d9ad6d322ec73a726bf520c4c46e:

  Move BR2_SPARC_TYPE to an uClibc specific place (2012-09-04 15:48:24 +0200)

----------------------------------------------------------------
Thomas Petazzoni (2):
      Move BR2_ARM_TYPE to an uClibc specific place
      Move BR2_SPARC_TYPE to an uClibc specific place

 target/Config.in.arch      |   26 --------------------------
 toolchain/uClibc/Config.in |   30 ++++++++++++++++++++++++++++++
 toolchain/uClibc/uclibc.mk |    4 ++--
 3 files changed, 32 insertions(+), 28 deletions(-)

Thanks,
-- 
Thomas Petazzoni

             reply	other threads:[~2012-09-04 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 13:49 Thomas Petazzoni [this message]
2012-09-04 13:49 ` [Buildroot] [PATCH 1/2] Move BR2_ARM_TYPE to an uClibc specific place Thomas Petazzoni
2012-09-04 13:49 ` [Buildroot] [PATCH 2/2] Move BR2_SPARC_TYPE " Thomas Petazzoni
2012-09-04 22:38 ` [Buildroot] [pull request] Pull request for branch uclibc-arch-type-cleanup Yann E. MORIN
2012-09-20 20:25 ` 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=cover.1346766545.git.thomas.petazzoni@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