From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-yocto: consolidated pull request
Date: Mon, 9 Apr 2018 11:16:04 -0400 [thread overview]
Message-ID: <cover.1523286757.git.bruce.ashfield@windriver.com> (raw)
Hi all,
Given how close we are to the release, I'm staying away from -stable updates
to the linux-yocto kernels. But I do have one small patch integration and two
minor bug fixes that are worth getting in for the release.
I don't expect any issues with these .. famous last words :D
Cheers,
Bruce
The following changes since commit 29f65bda6d2c9fea4adb125c4857ee64f9312b9f:
nativesdk-glibc: Split glibc and libcrypt to use libxcrypt instead (2018-04-07 22:34:45 +0100)
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 (3):
linux-yocto/4.14: add elfutils, util-linux and openssl dependencies
linux-yocto-tiny/4.14: fix recipe name
linux-yocto/4.14/4.15: deterministic srcversion
meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb | 7 ++-
meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb | 4 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb | 7 ++-
meta/recipes-kernel/linux/linux-yocto-tiny_4.15.b | 25 -----------
meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb | 50 ++++++----------------
meta/recipes-kernel/linux/linux-yocto_4.14.bb | 21 +++++----
meta/recipes-kernel/linux/linux-yocto_4.15.bb | 18 ++++----
7 files changed, 47 insertions(+), 85 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.b
--
2.5.0
next reply other threads:[~2018-04-09 15:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 15:16 Bruce Ashfield [this message]
2018-04-09 15:16 ` [PATCH 1/3] linux-yocto/4.14: add elfutils, util-linux and openssl dependencies Bruce Ashfield
2018-04-09 15:16 ` [PATCH 2/3] linux-yocto-tiny/4.14: fix recipe name Bruce Ashfield
2018-04-09 15:16 ` [PATCH 3/3] linux-yocto/4.14/4.15: deterministic srcversion Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2020-03-22 1:18 [PATCH 0/3] linux-yocto: consolidated pull request Bruce Ashfield
2019-02-09 18:37 bruce.ashfield
2019-02-06 19:50 bruce.ashfield
2019-01-21 17:26 Bruce Ashfield
2019-01-12 18:12 Bruce Ashfield
2016-09-20 15:16 Bruce Ashfield
2016-06-06 8:15 Bruce Ashfield
2016-05-24 15:53 Bruce Ashfield
2013-11-26 17:33 Bruce Ashfield
2013-09-18 18:24 Bruce Ashfield
2012-12-03 20:49 Bruce Ashfield
2012-08-27 4:49 Bruce Ashfield
2012-08-28 14:22 ` Saul Wold
2012-08-29 7:58 ` Bruce Ashfield
2012-03-05 4:01 Bruce Ashfield
2012-03-13 15:54 ` Saul Wold
2012-02-27 19:34 Bruce Ashfield
2012-02-28 18:41 ` Saul Wold
2012-01-04 20:12 Bruce Ashfield
2011-12-08 17:11 Bruce Ashfield
2011-09-14 18:11 Bruce Ashfield
2011-09-15 17:37 ` Saul Wold
2011-09-03 3:03 Bruce Ashfield
2011-09-05 19:26 ` Richard Purdie
2011-08-19 5:20 Bruce Ashfield
2011-08-20 5:08 ` Bruce Ashfield
2011-08-15 20:24 Bruce Ashfield
2011-08-22 22:37 ` Saul Wold
2011-05-09 18:34 Bruce Ashfield
2011-05-10 17:53 ` Saul Wold
2011-05-05 4:53 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.1523286757.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox