From: Saul Wold <sgw@linux.intel.com>
To: poky@yoctoproject.org
Subject: [Consolidated Poky Pull 0/7] Poky Kernel, Tiny and scripts updates
Date: Mon, 25 Jun 2012 10:07:15 -0700 [thread overview]
Message-ID: <cover.1340643949.git.sgw@linux.intel.com> (raw)
Richard,
This pulls together a number of changes pending for meta-yocto
in Poky Master.
Sau!
The following changes since commit 5e3a61b40b7b697d83b41e7e247cd1f94eb7673c:
bblayers.conf.sample: Fix empty BBPATH entry warnings (2012-06-25 16:35:55 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib sgw/stage
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sgw/stage
Bruce Ashfield (2):
linux-libc-headers-yocto: use kernel-arch to set ARCH
linux-libc-headers-yocto: update to v3.4 and remove unecessary code
Darren Hart (2):
busybox: Introduce poky-tiny defconfig override
tiny-init: Basic init mechanism for poky-tiny
Saul Wold (1):
upstream_tracking: Update Upgraded and Manual Checked upstream
Tom Zanussi (2):
yocto-bsp: update yocto-bsp machine.conf template
yocto-bsp: update yocto-bsp xorg.conf templates
.../conf/distro/include/upstream_tracking.inc | 61 +-
meta-yocto/conf/distro/poky-tiny.conf | 2 +-
.../busybox/busybox-1.19.4/poky-tiny/defconfig | 1009 ++++++++++++++++++++
.../recipes-core/busybox/busybox_1.19.4.bbappend | 2 +
meta-yocto/recipes-core/tiny-init/files/init | 21 +
.../recipes-core/tiny-init/files/rc.local.sample | 23 +
meta-yocto/recipes-core/tiny-init/tiny-init.bb | 28 +
.../linux-libc-headers-yocto_git.bb | 45 +-
.../arch/qemu/conf/machine/{{=machine}}.conf | 7 +-
.../xserver-xf86-config/{{=machine}}/xorg.conf | 8 +
..."x86_64\": }} xserver-xf86-config_0.1.bbappend" | 2 -
11 files changed, 1132 insertions(+), 76 deletions(-)
create mode 100644 meta-yocto/recipes-core/busybox/busybox-1.19.4/poky-tiny/defconfig
create mode 100644 meta-yocto/recipes-core/busybox/busybox_1.19.4.bbappend
create mode 100644 meta-yocto/recipes-core/tiny-init/files/init
create mode 100644 meta-yocto/recipes-core/tiny-init/files/rc.local.sample
create mode 100644 meta-yocto/recipes-core/tiny-init/tiny-init.bb
delete mode 100644 "scripts/lib/bsp/substrate/target/arch/qemu/recipes-graphics/xorg-xserver/{{ if qemuarch == \"i386\" or qemuarch == \"x86_64\": }} xserver-xf86-config_0.1.bbappend"
--
1.7.7.6
next reply other threads:[~2012-06-25 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 17:07 Saul Wold [this message]
2012-06-25 17:07 ` [Consolidated Poky Pull 1/7] linux-libc-headers-yocto: use kernel-arch to set ARCH Saul Wold
2012-06-25 17:07 ` [Consolidated Poky Pull 2/7] linux-libc-headers-yocto: update to v3.4 and remove unecessary code Saul Wold
2012-06-25 17:07 ` [Consolidated Poky Pull 3/7] upstream_tracking: Update Upgraded and Manual Checked upstream Saul Wold
2012-06-25 17:07 ` [Consolidated Poky Pull 4/7] yocto-bsp: update yocto-bsp machine.conf template Saul Wold
2012-06-25 17:07 ` [Consolidated Poky Pull 5/7] yocto-bsp: update yocto-bsp xorg.conf templates Saul Wold
2012-06-25 17:07 ` [Consolidated Poky Pull 6/7] busybox: Introduce poky-tiny defconfig override Saul Wold
2012-06-25 17:07 ` [Consolidated Poky Pull 7/7] tiny-init: Basic init mechanism for poky-tiny Saul Wold
2012-06-26 14:36 ` [Consolidated Poky Pull 0/7] Poky Kernel, Tiny and scripts updates Richard Purdie
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.1340643949.git.sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=poky@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.