From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] linux-yocto: consolidated pull request
Date: Mon, 14 Sep 2020 18:34:15 -0400 [thread overview]
Message-ID: <cover.1600122415.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's the latest round of -stable updates for the active kernels in
master.
My first runs ran into the lttng-modules issues, and I've included a
10 patch backport of changes from lttng 2.12.x to address the various
build issues I found against 5.4 and 5.8.
There's a different lttng patch on the list, but it didn't address all
of my build failures, so I generated this full backport change.
Cheers,
Bruce
The following changes since commit 070d9b8f5e753e8928d2d7048e0c7bd9adbb3c29:
linux-yocto/config: netfilter: Enable nat for ipv4 and ipv6 (2020-09-14 12:13:47 -0400)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib zedd/kernel
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (5):
linux-yocto/5.8: update to v5.8.8
linux-yocto/5.4: update to v5.4.64
linux-yocto/config: configuration warning cleanup
linux-yocto/5.8: update to v5.8.9
linux-yocto/5.4: update to v5.4.65
Jens Rehsack (1):
lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+
builds
.../linux/linux-yocto-rt_5.4.bb | 6 +-
.../linux/linux-yocto-rt_5.8.bb | 6 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +-
.../linux/linux-yocto-tiny_5.8.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +-
meta/recipes-kernel/linux/linux-yocto_5.8.bb | 22 +-
...ndency-issue-when-building-in-tree-w.patch | 54 ++
...ce.h-into-the-mmu-sub-directory-v5.9.patch | 41 +
...Make-kvm_mmu_page-definition-and-acc.patch | 39 +
...he-length-of-per-inode-prealloc-list.patch | 84 ++
...e-via-a-block-bitmap-read-is-prefetc.patch | 63 ++
...al-of-smp_-read_barrier_depends-v5.9.patch | 391 ++++++++
...teback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch | 59 ++
...x-sync-livelock-due-to-b_dirty_time-.patch | 117 +++
...es-for-ext4_discard_preallocations-a.patch | 52 +
.../0010-Fix-system-call-filter-table.patch | 918 ++++++++++++++++++
.../lttng/lttng-modules_2.12.2.bb | 12 +-
17 files changed, 1865 insertions(+), 37 deletions(-)
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0001-Kconfig-fix-dependency-issue-when-building-in-tree-w.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0002-fix-Move-mmutrace.h-into-the-mmu-sub-directory-v5.9.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0003-fix-KVM-x86-mmu-Make-kvm_mmu_page-definition-and-acc.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0004-fix-ext4-limit-the-length-of-per-inode-prealloc-list.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0005-fix-ext4-indicate-via-a-block-bitmap-read-is-prefetc.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0006-fix-removal-of-smp_-read_barrier_depends-v5.9.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0007-fix-writeback-Drop-I_DIRTY_TIME_EXPIRE-v5.9.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0008-fix-writeback-Fix-sync-livelock-due-to-b_dirty_time-.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0009-fix-version-ranges-for-ext4_discard_preallocations-a.patch
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0010-Fix-system-call-filter-table.patch
--
2.19.1
next reply other threads:[~2020-09-14 22:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 22:34 Bruce Ashfield [this message]
2020-09-14 22:34 ` [PATCH 1/6] linux-yocto/5.8: update to v5.8.8 Bruce Ashfield
2020-09-14 22:34 ` [PATCH 2/6] linux-yocto/5.4: update to v5.4.64 Bruce Ashfield
2020-09-14 22:34 ` [PATCH 3/6] linux-yocto/config: configuration warning cleanup Bruce Ashfield
2020-09-14 22:34 ` [PATCH 4/6] linux-yocto/5.8: update to v5.8.9 Bruce Ashfield
2020-09-14 22:34 ` [PATCH 5/6] linux-yocto/5.4: update to v5.4.65 Bruce Ashfield
2020-09-14 22:34 ` [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds Bruce Ashfield
2020-09-14 22:35 ` Bruce Ashfield
2020-09-15 5:03 ` [OE-core] " Jens Rehsack
2020-09-15 11:37 ` Bruce Ashfield
2020-09-15 5:44 ` Jens Rehsack
2020-09-15 11:33 ` Bruce Ashfield
2020-09-15 11:45 ` Richard Purdie
2020-09-15 11:53 ` Bruce Ashfield
2020-09-25 16:43 ` Steve Sakoman
2020-09-25 16:52 ` Bruce Ashfield
2020-09-25 19:48 ` Steve Sakoman
2020-09-27 21:18 ` Bruce Ashfield
[not found] ` <1638C0AFDA43827E.8201@lists.openembedded.org>
2020-09-28 17:44 ` Bruce Ashfield
2020-09-28 22:35 ` Steve Sakoman
2020-09-28 22:53 ` Bruce Ashfield
[not found] ` <16391475BC3C80C8.17908@lists.openembedded.org>
2020-09-29 14:54 ` Bruce Ashfield
2020-09-29 17:23 ` Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2026-01-14 17:24 [PATCH 0/6] linux-yocto: consolidated pull request bruce.ashfield
2024-10-14 13:45 bruce.ashfield
2021-03-05 3:54 Bruce Ashfield
2021-02-18 3:59 Bruce Ashfield
2018-10-17 13:38 Bruce Ashfield
2016-07-07 18:39 Bruce Ashfield
2016-06-13 15:56 Bruce Ashfield
2015-10-23 20:18 Bruce Ashfield
2015-08-24 13:51 Bruce Ashfield
2014-10-01 4:43 Bruce Ashfield
2014-05-05 14:10 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.1600122415.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