Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/8] kernel-yocto: consolidated pull request
Date: Sat, 22 Sep 2018 13:18:46 -0400	[thread overview]
Message-ID: <cover.1537636541.git.bruce.ashfield@windriver.com> (raw)

Hi all,

Here is the consolidated pull request for the active linux-yocto
kernels.

It is -stable updates, configuration audit warning fixes as well
as a fix for the qemuarm64 boot hang with the ssl update.

Nothing to major here, and I've boot tested on all architectures,
but you never know what the autobuilder may dig out.

Cheers,

Bruce

The following changes since commit 18b90a0fd9bdc00d82140fbd55761e9cea308fb1:

  yocto-uninative: Add aarch64 uninative tarball checksum (2018-09-20 09:06:00 -0700)

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 (7):
  linux-yocto: configuration warning fixes
  linux-yocto/4.18: update to v4.18.7
  linux-yocto: tweak RTC configuration
  linux-yocto/4.14: fix kernel configuration audit warnings
  linux-yocto/4.18: update to v4.18.9
  linux-yocto/4.14: update to v4.14.71
  linux-yocto: enable pci and CRYPTO_DEV_VIRTIO

Hongzhi.Song (1):
  linux-yocto-rt: Add paravirt_kvm support for qemux86-64

 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb   |  8 ++++----
 meta/recipes-kernel/linux/linux-yocto-rt_4.18.bb   |  8 ++++----
 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.18.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.14.bb      | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.18.bb      | 20 ++++++++++----------
 6 files changed, 34 insertions(+), 34 deletions(-)

-- 
2.5.0



             reply	other threads:[~2018-09-22 17:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-22 17:18 Bruce Ashfield [this message]
2018-09-22 17:18 ` [PATCH 1/8] linux-yocto-rt: Add paravirt_kvm support for qemux86-64 Bruce Ashfield
2018-09-22 17:18 ` [PATCH 2/8] linux-yocto: configuration warning fixes Bruce Ashfield
2018-09-22 17:18 ` [PATCH 3/8] linux-yocto/4.18: update to v4.18.7 Bruce Ashfield
2018-09-22 17:18 ` [PATCH 4/8] linux-yocto: tweak RTC configuration Bruce Ashfield
2018-09-22 17:18 ` [PATCH 5/8] linux-yocto/4.14: fix kernel configuration audit warnings Bruce Ashfield
2018-09-22 17:18 ` [PATCH 6/8] linux-yocto/4.18: update to v4.18.9 Bruce Ashfield
2018-09-22 17:18 ` [PATCH 7/8] linux-yocto/4.14: update to v4.14.71 Bruce Ashfield
2018-09-22 17:18 ` [PATCH 8/8] linux-yocto: enable pci and CRYPTO_DEV_VIRTIO Bruce Ashfield
2018-09-22 17:24 ` [PATCH 0/8] kernel-yocto: consolidated pull request Khem Raj
2018-09-22 19:03 ` richard.purdie
2018-09-22 23:03 ` richard.purdie
  -- strict thread matches above, loose matches on Subject: below --
2017-12-04 15:39 Bruce Ashfield
2017-12-10 12:32 ` Richard Purdie
2017-12-10 15:16   ` Bruce Ashfield
2017-12-10 17:40     ` Bruce Ashfield
2017-12-10 17:44   ` 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.1537636541.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