From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch xtensa
Date: Thu, 15 Nov 2012 14:30:10 +0100 [thread overview]
Message-ID: <cover.1352986210.git.thomas.petazzoni@free-electrons.com> (raw)
The following changes since commit 53adfc5f4976704d426681a0404c1643db009552:
lua: refactor without useless define's (2012-11-15 12:39:19 +0100)
are available in the git repository at:
git://git.free-electrons.com/users/thomas-petazzoni/buildroot.git xtensa
for you to fetch changes up to 7c693cd311e2993cf78952db386b977b21196979:
xtensa: support configurable processor configurations (2012-11-15 14:30:02 +0100)
----------------------------------------------------------------
Chris Zankel (2):
xtensa: add support for the Xtensa architecture
xtensa: support configurable processor configurations
Thomas Petazzoni (3):
arch: improve definition of gcc mtune, mcpu, etc.
uClibc: remove useless linuxthreads-errno-fix patch
uClibc: update uClibc-snapshot.config to recent uClibcs
arch/Config.in | 70 +++++-
arch/Config.in.aarch64 | 5 +
arch/Config.in.arm | 52 +++++
arch/Config.in.avr32 | 5 +
arch/Config.in.bfin | 6 +
arch/Config.in.common | 245 --------------------
arch/Config.in.m68k | 21 ++
arch/Config.in.microblaze | 10 +
arch/Config.in.mips | 25 ++
arch/Config.in.powerpc | 45 ++++
arch/Config.in.sh | 17 ++
arch/Config.in.sparc | 31 +++
arch/Config.in.x86 | 89 +++++++
arch/Config.in.xtensa | 33 +++
linux/Config.in | 3 +-
package/binutils/binutils.mk | 9 +
package/ltrace/Config.in | 1 +
toolchain/Config.in | 2 +-
toolchain/gcc/gcc-uclibc-4.x.mk | 4 +
toolchain/gdb/gdb.mk | 4 +
toolchain/toolchain-buildroot/Config.in.2 | 4 +-
toolchain/toolchain-common.in | 2 +-
toolchain/uClibc/Config.in | 5 +-
toolchain/uClibc/uClibc-snapshot.config | 1 +
.../uClibc.snapshot.linuxthreads-errno-fix.patch | 68 ------
toolchain/uClibc/uclibc.mk | 1 +
26 files changed, 435 insertions(+), 323 deletions(-)
create mode 100644 arch/Config.in.aarch64
create mode 100644 arch/Config.in.avr32
delete mode 100644 arch/Config.in.common
create mode 100644 arch/Config.in.m68k
create mode 100644 arch/Config.in.microblaze
create mode 100644 arch/Config.in.xtensa
delete mode 100644 toolchain/uClibc/uClibc.snapshot.linuxthreads-errno-fix.patch
Thanks,
--
Thomas Petazzoni
next reply other threads:[~2012-11-15 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 13:30 Thomas Petazzoni [this message]
2012-11-15 13:30 ` [Buildroot] [PATCH 1/5] arch: improve definition of gcc mtune, mcpu, etc Thomas Petazzoni
2012-11-15 13:38 ` Yann E. MORIN
2012-11-15 13:54 ` Thomas Petazzoni
2012-11-15 13:30 ` [Buildroot] [PATCH 2/5] uClibc: remove useless linuxthreads-errno-fix patch Thomas Petazzoni
2012-11-15 13:30 ` [Buildroot] [PATCH 3/5] uClibc: update uClibc-snapshot.config to recent uClibcs Thomas Petazzoni
2012-11-15 13:30 ` [Buildroot] [PATCH 4/5] xtensa: add support for the Xtensa architecture Thomas Petazzoni
2012-11-15 13:30 ` [Buildroot] [PATCH 5/5] xtensa: support configurable processor configurations Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2012-11-15 13:53 [Buildroot] [pull request] Pull request for branch xtensa Thomas Petazzoni
2012-11-15 15:40 ` 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.1352986210.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