From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch yem/misc-updates
Date: Wed, 4 Sep 2013 23:35:52 +0200 [thread overview]
Message-ID: <cover.1378330371.git.yann.morin.1998@free.fr> (raw)
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
Hello All!
Peter, here are a few changes I've been sitting on since before I
switched into holidays mode (and in redo-the-kitchen-from-scrath mode,
which ultimately kicked in the has-no-time-to-get-in-front-of-computer
mode) three weeks ago.
I'm now back in operational condition! :-]
- two changes RPI-related: bump kernel (rpi_defconfig), bunp firmware
- further cleanup top-level config by moving target options to their
own sub-menu
- optionally print toolchain wrapper's args one-per-line in DEBUG mode
I still have to dequeue all my mails, but I'm still on holidays until
the end of the week, so... ;-)
Regards,
Yann E. MORIN.
The following changes since commit 5128cc6602d56a2c3af4cf6a0fe072d39d6c1aca:
gcc: pass MAKEINFO=missing in the environment rather than as a ./configure arg (2013-09-04 16:22:30 +0200)
are available in the git repository at:
git://gitorious.org/buildroot/buildroot.git
for you to fetch changes up to e1d03e22b10b073d5906a4b6df22c72d38bfd8c2:
toolchain/wrapper: add option to print one argument per line (2013-09-04 23:27:37 +0200)
----------------------------------------------------------------
Yann E. MORIN (4):
package/rpi-firmware: bump version
configs: bump kernel use for RPi, use simpler defconfig
targets: move target options to their own sub-menu
toolchain/wrapper: add option to print one argument per line
arch/Config.in | 4 ++++
configs/rpi_defconfig | 4 ++--
package/rpi-firmware/rpi-firmware.mk | 2 +-
.../toolchain-external/ext-toolchain-wrapper.c | 25 +++++++++++++++-------
4 files changed, 24 insertions(+), 11 deletions(-)
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2013-09-04 21:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 21:35 Yann E. MORIN [this message]
2013-09-04 21:35 ` [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Yann E. MORIN
2013-09-05 13:42 ` Peter Korsgaard
2013-09-04 21:35 ` [Buildroot] [PATCH 2/4] configs: bump kernel use for RPi, use simpler defconfig Yann E. MORIN
2013-09-05 13:43 ` Peter Korsgaard
2013-09-04 21:35 ` [Buildroot] [PATCH 3/4] targets: move target options to their own sub-menu Yann E. MORIN
2013-09-05 2:25 ` Thomas De Schampheleire
2013-09-05 13:51 ` Yann E. MORIN
2013-09-05 13:44 ` Peter Korsgaard
2013-09-04 21:35 ` [Buildroot] [PATCH 4/4] toolchain/wrapper: add option to print one argument per line Yann E. MORIN
2013-09-05 12:48 ` Luca Ceresoli
2013-09-05 13:55 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2013-09-20 22:00 [Buildroot] [pull request] Pull request for branch yem/misc-updates Yann E. MORIN
2013-10-04 22:00 Yann E. MORIN
2013-10-04 22:04 ` 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.1378330371.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--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