From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] kernel: consolidated pull request
Date: Tue, 9 Mar 2021 14:23:35 -0500 [thread overview]
Message-ID: <cover.1615317549.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here's my latest set of kernel changes. They are a bit more varied than
at times:
- stable updates. These shouldn't be an issue
- kern-tools: minor fixes from the list
The more time consuming change is the perf reproducibility changes. They
are passing locally for me, so could use some time on the AB to see if
that is truely the case. As usual, we don't patch perf, so these take the
form of various sed changes to the source. They shouldn't cause issues on
older versions of perf, but I haven't tested that extensively.
The changes are specific to our builds, and I need to re-consider them
in the context of upstream (since quite honestly, I don't know why some
of the paths that were being captured were being captured at all). I've
marked them as such in commit header and in the recipe.
Cheers,
Bruce
The following changes since commit 281eba70c2c3beef556949980d7f81e7461ba5dd:
bitbake: __init__.py: Fix bitbake debug log handling (2021-03-09 00:02:41 +0000)
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 (6):
perf: fix reproducibility issues
reproducibile: remove perf from exclusions
linux-yocto/5.10: update to v5.10.21
linux-yocto/5.4: update to v5.4.103
linux-yocto/qemuarmv5: fix configuration warning
kern-tools: symbol-why fix and README update
meta/lib/oeqa/selftest/cases/reproducible.py | 1 -
.../kern-tools/kern-tools-native_git.bb | 2 +-
.../linux/linux-yocto-rt_5.10.bb | 6 +--
.../linux/linux-yocto-rt_5.4.bb | 6 +--
.../linux/linux-yocto-tiny_5.10.bb | 8 ++--
.../linux/linux-yocto-tiny_5.4.bb | 8 ++--
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 22 +++++------
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +++++------
meta/recipes-kernel/perf/perf.bb | 38 +++++++++++++++++++
9 files changed, 75 insertions(+), 38 deletions(-)
--
2.19.1
next reply other threads:[~2021-03-09 19:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 19:23 Bruce Ashfield [this message]
2021-03-09 19:23 ` [PATCH 1/6] perf: fix reproducibility issues Bruce Ashfield
2021-03-10 10:42 ` [OE-core] " Kory Maincent
2021-03-10 11:27 ` Kory Maincent
2021-03-10 13:37 ` Bruce Ashfield
2021-03-10 13:58 ` Richard Purdie
2021-03-09 19:23 ` [PATCH 2/6] reproducibile: remove perf from exclusions Bruce Ashfield
2021-03-09 19:26 ` Bruce Ashfield
2021-03-09 19:23 ` [PATCH 3/6] linux-yocto/5.10: update to v5.10.21 Bruce Ashfield
2021-03-10 10:32 ` [OE-core] " Kory Maincent
2021-03-10 13:35 ` Bruce Ashfield
2021-03-09 19:23 ` [PATCH 4/6] linux-yocto/5.4: update to v5.4.103 Bruce Ashfield
2021-03-09 19:23 ` [PATCH 5/6] linux-yocto/qemuarmv5: fix configuration warning Bruce Ashfield
2021-03-09 19:23 ` [PATCH 6/6] kern-tools: symbol-why fix and README update Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2022-02-04 4:16 [PATCH 0/6] kernel: consolidated pull request bruce.ashfield
2022-01-27 3:55 bruce.ashfield
2022-01-14 18:23 bruce.ashfield
2021-11-04 19:48 bruce.ashfield
2019-10-21 20:16 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.1615317549.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.