From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] kernel-yocto: consolidated pull request
Date: Fri, 5 Jul 2019 12:14:02 -0400 [thread overview]
Message-ID: <cover.1562342843.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Hi all,
Here's the next round of updates I've been testing. The 4.19 update is pretty
standard, and is both a -stable and -rt refresh. Boot testing shows no issues
on either kernel type.
We also have a configuration tweak to allow the beaglebone reference to be
booted in qemu directly.
Finally, there's a packaging change .. which I normally don't have in these
requests, but it is an underpinning change for some future kernel features
and updates that I'd like to get out separately. The problem was found while
moving postinsts into both kernel.bbclass and kernel-devsrc.bbclass, and
without it, you can't assemble a rootfs for packages that are using PKG_
constructs. The details are in the commit log of the patch.
The change has been working here (and at Xilinx) for a couple of months now,
so it shouldn't have any drastic side effects. There *may* be other places
that this is required, but I kept to the code paths I could test.
Cheers,
Bruce
The following changes since commit 4fd9ee4670293632cc0ca1e64b8833eb6014435d:
bitbake: bitbake: Add --skip-setscene option (2019-07-03 17:00:57 +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: bsp/beaglebone: support qemu -machine virt
linux-yocto/4.19: update to 4.19.57 and -rt22
package: check PKG_ variables before executing ontarget postinst
meta/classes/package.bbclass | 6 +++++-
.../linux/linux-yocto-rt_4.19.bb | 6 +++---
.../linux/linux-yocto-rt_5.0.bb | 2 +-
.../linux/linux-yocto-tiny_4.19.bb | 8 ++++----
.../linux/linux-yocto-tiny_5.0.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.19.bb | 20 +++++++++----------
meta/recipes-kernel/linux/linux-yocto_5.0.bb | 2 +-
7 files changed, 25 insertions(+), 21 deletions(-)
--
2.19.1
next reply other threads:[~2019-07-05 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 16:14 bruce.ashfield [this message]
2019-07-05 16:14 ` [PATCH 1/3] linux-yocto: bsp/beaglebone: support qemu -machine virt bruce.ashfield
2019-07-05 16:14 ` [PATCH 2/3] linux-yocto/4.19: update to 4.19.57 and -rt22 bruce.ashfield
2019-07-05 16:14 ` [PATCH 3/3] package: check PKG_ variables before executing ontarget postinst bruce.ashfield
-- strict thread matches above, loose matches on Subject: below --
2022-10-19 3:39 [PATCH 0/3] kernel-yocto: consolidated pull request bruce.ashfield
2020-08-21 19:02 Bruce Ashfield
2013-02-05 15:56 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.1562342843.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox