From: <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: <ross.burton@arm.com>
Subject: [PATCH v3 0/1] bootchart2: Several fixes
Date: Sun, 24 Nov 2024 04:13:57 -0800 [thread overview]
Message-ID: <cover.1732450236.git.liezhi.yang@windriver.com> (raw)
From: Robert Yang <liezhi.yang@windriver.com>
* V3
- Fixed do_package error when usrmerge in DISTRO_FEATURES.
* V2: Fixed Ross' comments:
- Add -n to gzip to make the resulting files reproducible, so we don't need to
decompress them.
- Makefile: Let bootchartd.conf use EARLY_PREFIX, so that bootchartd.conf can
install to correct location.
- Set MANDIR and DOCDIR to make the files install to correct location for
bootchart2-native.
* V1
Initial version
// Robert
The following changes since commit 5e0ff36e025f5e842fa90b8219b53257d65ea66a:
lib/oe/sbom30: Prefix aliases with "http://spdx.org/spdxdocs/" (2024-11-23 14:28:29 +0000)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/bootchart2
https://github.com/robertlinux/yocto/tree/rbt/bootchart2
Robert Yang (1):
bootchart2: Several fixes
...efile-Let-bootchartd.conf-use-EARLY_.patch | 30 +++++++++++++++
.../0002-Makefile-Add-n-to-gzip.patch | 37 +++++++++++++++++++
.../bootchart2/bootchart2_0.14.9.bb | 12 ++++--
3 files changed, 76 insertions(+), 3 deletions(-)
create mode 100644 meta/recipes-devtools/bootchart2/bootchart2/0001-Makefile-Let-bootchartd.conf-use-EARLY_.patch
create mode 100644 meta/recipes-devtools/bootchart2/bootchart2/0002-Makefile-Add-n-to-gzip.patch
--
2.44.1
next reply other threads:[~2024-11-24 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 12:13 liezhi.yang [this message]
2024-11-24 12:13 ` [PATCH v3 1/1] bootchart2: Several fixes liezhi.yang
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.1732450236.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
/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