From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: Re: [PATCH 0/1] tiny: Update linux-yocto-tiny to 3.2
Date: Tue, 03 Apr 2012 16:47:43 -0700 [thread overview]
Message-ID: <4F7B8C1F.40402@linux.intel.com> (raw)
In-Reply-To: <cover.1333264701.git.dvhart@linux.intel.com>
On 04/01/2012 12:19 AM, Darren Hart wrote:
> The following changes since commit c97f7f4e4ecd6c431712059c34ebc17b68b055ae:
>
> cross-canadian.bbclass: fix rpath for sdk executables (2012-03-31 18:00:36 +0100)
>
> are available in the git repository at:
> git://git.infradead.org/users/dvhart/oe-core.git dvhart/tiny
> http://git.infradead.org/users/dvhart/oe-core.git/shortlog/refs/heads/dvhart/tiny
>
> Darren Hart (1):
> tiny: Update linux-yocto-tiny to 3.2
>
> meta/recipes-kernel/linux/linux-yocto-tiny/ata.cfg | 9 -
> .../recipes-kernel/linux/linux-yocto-tiny/core.cfg | 19 -
> .../linux/linux-yocto-tiny/debug.cfg | 5 -
> .../linux/linux-yocto-tiny/devtmpfs.cfg | 6 -
> .../linux/linux-yocto-tiny/e1000.cfg | 7 -
> .../recipes-kernel/linux/linux-yocto-tiny/ext2.cfg | 1 -
> .../recipes-kernel/linux/linux-yocto-tiny/ext3.cfg | 2 -
> .../recipes-kernel/linux/linux-yocto-tiny/lzma.cfg | 3 -
> meta/recipes-kernel/linux/linux-yocto-tiny/net.cfg | 26 -
> .../linux/linux-yocto-tiny/qemux86/defconfig | 613 --------------------
> .../linux/linux-yocto-tiny/ramfs.cfg | 6 -
> .../linux/linux-yocto-tiny/rtc-pc.cfg | 13 -
> .../linux/linux-yocto-tiny/serial.cfg | 7 -
> meta/recipes-kernel/linux/linux-yocto-tiny/smp.cfg | 7 -
> meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb | 39 --
> meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb | 25 +
> 16 files changed, 25 insertions(+), 763 deletions(-)
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/ata.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/core.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/debug.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/devtmpfs.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/e1000.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/ext2.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/ext3.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/lzma.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/net.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/qemux86/defconfig
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/ramfs.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/rtc-pc.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/serial.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny/smp.cfg
> delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb
> create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-04-03 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 7:19 [PATCH 0/1] tiny: Update linux-yocto-tiny to 3.2 Darren Hart
2012-04-01 7:19 ` [PATCH 1/1] " Darren Hart
2012-04-01 12:52 ` [PATCH 0/1] " Bruce Ashfield
2012-04-03 23:47 ` Saul Wold [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=4F7B8C1F.40402@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.