From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] linux-yocto: introduce 4.4 named/versioned recipe
Date: Mon, 11 Jan 2016 11:58:25 -0500 [thread overview]
Message-ID: <cover.1452531312.git.bruce.ashfield@windriver.com> (raw)
Richard/Ross,
The 4.4 kernel has been released for about 20 hours, so it is about time
we get a named recipe in oe-core master :)
This is a quick update and re-test of what has already been in linux-yocto -dev.
Nothing blew up in my smoke testing, so hopefully that means a smooth
integration.
This is just the kernel part of the updates, I'll be following up with
preferred version bumps, and a rev of libc-headers shortly .. but there's
no need to wait on this.
Cheers,
Bruce
The following changes since commit 1ee08426d792ce27213dd411a885595d8435ae33:
sstatesig: Handle special case of gcc-source shared-workdir for printdiff (2016-01-11 15:41:47 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-yocto: introduce v4.4 standard/preempt-rt/standard kernel
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 27 +++++++++++++++
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 23 +++++++++++++
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 42 +++++++++++++++++++++++
3 files changed, 92 insertions(+)
create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.4.bb
--
2.1.0
next reply other threads:[~2016-01-11 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 16:58 Bruce Ashfield [this message]
2016-01-11 16:58 ` [PATCH 1/1] linux-yocto: introduce v4.4 standard/preempt-rt/standard kernel Bruce Ashfield
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.1452531312.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.