From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/9][stable] kernel-yocto: consolidated pull request
Date: Thu, 2 Nov 2017 22:45:24 -0400 [thread overview]
Message-ID: <cover.1509676901.git.bruce.ashfield@windriver.com> (raw)
Hi all,
This pull request is mainly for the -stable, and bug fixes that I gathered
during the last part of the 2.4 release.
I'm clearing my queue before I do the next round of -stable updates and
start removing kernels in preparation for 4.14 and feature work.
All of these commits are suitable for backport to the rocko stable branch.
I've built and booted on all the relevant arches via qemu .. but as usual,
the extra autobuilder coverage will help shake out anything subtle.
Cheers,
Bruce
The following changes since commit 5dacc5516718efdf0a470e074a5c05b1ecf8cc15:
bitbake: main: Give a user readable error if we can't locate topdir (2017-10-31 09:09:21 +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 (9):
linux-yocto-dev: bump to v4.14-rcX
linux-yocto/4.12: configuration and feature updates
linux-yocto/4.4: update to v4.4.93
linux-yocto/4.9: update to v4.9.57
linux-yocto/4.12: update to v4.12.14
linux-yocto/4.12: stable backports and bug fixes
kern-tools: make fuzzy matching optional
linux-yocto/4.12: configuration fragment updates
linux-yocto/4.12: ide:ide-cd: fix kernel panic resulting from missing
scsi_req_init
.../kern-tools/kern-tools-native_git.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb | 6 +++---
meta/recipes-kernel/linux/linux-yocto_4.12.bb | 20 ++++++++++----------
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 20 ++++++++++----------
meta/recipes-kernel/linux/linux-yocto_4.9.bb | 20 ++++++++++----------
11 files changed, 50 insertions(+), 50 deletions(-)
--
2.5.0
next reply other threads:[~2017-11-03 2:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 2:45 Bruce Ashfield [this message]
2017-11-03 2:45 ` [PATCH 1/9] linux-yocto-dev: bump to v4.14-rcX Bruce Ashfield
2017-11-03 2:45 ` [PATCH 2/9] linux-yocto/4.12: configuration and feature updates Bruce Ashfield
2017-11-03 2:45 ` [PATCH 3/9] linux-yocto/4.4: update to v4.4.93 Bruce Ashfield
2017-11-03 2:45 ` [PATCH 4/9] linux-yocto/4.9: update to v4.9.57 Bruce Ashfield
2017-11-03 2:45 ` [PATCH 5/9] linux-yocto/4.12: update to v4.12.14 Bruce Ashfield
2017-11-03 2:45 ` [PATCH 6/9] linux-yocto/4.12: stable backports and bug fixes Bruce Ashfield
2017-11-03 2:45 ` [PATCH 7/9] kern-tools: make fuzzy matching optional Bruce Ashfield
2017-11-03 2:45 ` [PATCH 8/9] linux-yocto/4.12: configuration fragment updates Bruce Ashfield
2017-11-03 2:45 ` [PATCH 9/9] linux-yocto/4.12: ide:ide-cd: fix kernel panic resulting from missing scsi_req_init 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.1509676901.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.