All of lore.kernel.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] kernel-yocto: misc build / config changes
Date: Wed, 14 Aug 2019 11:31:28 -0400	[thread overview]
Message-ID: <cover.1565796002.git.bruce.ashfield@gmail.com> (raw)

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi all,

This pull request is a collection of smaller fixes that I've been collecting
while I work through the 5.2/5.3 kernel intro, new libc-headers, etc. There's
no reason to make them wait while I finish that work, so here they are in a
single branch.

There's nothing major here, just a some legwork changes, licensing update
and a short term workaround for embedded host paths in the kernel binaries.

Cheers,

Bruce

The following changes since commit 88c6be81a5fbed098999fbef5576c5e0bb90cc21:

  opensbi: handle deploy task under sstate (2019-08-06 11:24:27 +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 (5):
  kernel-devsrc: tweak for v5.3+
  kern-tools: Add SPDX license headers to source files
  linux-yocto: arch/x86/boot: use prefix map to avoid embedded paths
  kernel-yocto: import security fragments from meta-security
  kconf_check: tweak CONFIG_ regex

 .../kern-tools/kern-tools-native_git.bb        |  4 ++--
 meta/recipes-kernel/linux/kernel-devsrc.bb     |  4 ++--
 .../linux/linux-yocto-rt_4.19.bb               |  2 +-
 .../recipes-kernel/linux/linux-yocto-rt_5.0.bb |  4 ++--
 .../linux/linux-yocto-tiny_4.19.bb             |  2 +-
 .../linux/linux-yocto-tiny_5.0.bb              |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.19.bb  |  2 +-
 meta/recipes-kernel/linux/linux-yocto_5.0.bb   | 18 +++++++++---------
 8 files changed, 21 insertions(+), 21 deletions(-)

-- 
2.19.1



             reply	other threads:[~2019-08-14 15:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 15:31 bruce.ashfield [this message]
2019-08-14 15:31 ` [PATCH 1/5] kernel-devsrc: tweak for v5.3+ bruce.ashfield
2019-08-29  9:17   ` Mittal, Anuj
2019-08-29 12:27     ` Bruce Ashfield
2019-08-30  2:13       ` Mittal, Anuj
2019-08-30  3:40         ` Bruce Ashfield
2019-08-14 15:31 ` [PATCH 2/5] kern-tools: Add SPDX license headers to source files bruce.ashfield
2019-08-14 15:31 ` [PATCH 3/5] linux-yocto: arch/x86/boot: use prefix map to avoid embedded paths bruce.ashfield
2019-08-14 15:31 ` [PATCH 4/5] kernel-yocto: import security fragments from meta-security bruce.ashfield
2019-08-14 15:31 ` [PATCH 5/5] kconf_check: tweak CONFIG_ regex bruce.ashfield
2019-08-14 16:02 ` ✗ patchtest: failure for kernel-yocto: misc build / config changes Patchwork
2019-08-29  9:29 ` [PATCH 0/5] " richard.purdie
2019-08-29 12:25   ` Bruce Ashfield
2019-08-29 12:43     ` Bruce Ashfield
2019-08-29 15:28       ` Jonathan Rajotte-Julien
2019-08-29 15:31         ` Bruce Ashfield
2019-08-29 15:32           ` Bruce Ashfield
2019-08-30 14:39             ` richard.purdie
2019-08-30 14:50               ` Bruce Ashfield
2019-08-30 16:19                 ` richard.purdie

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.1565796002.git.bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.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.