From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Tretter <m.tretter@pengutronix.de>
Subject: [ptxdist] [PATCH v3 0/2] add libtraceevent for perf
Date: Wed, 15 May 2024 09:22:55 +0200 [thread overview]
Message-ID: <20240515072254.12082-4-u.kleine-koenig@pengutronix.de> (raw)
Hello,
changes since (implicit) v1 available at
https://lore.ptxdist.org/ptxdist/ZjtM5u8mjdcZjx-B@pengutronix.de/:
- split in two patches (suggested by Michael Tretter)
- drop commented out targets (suggested by Michael Tretter)
- install plugin libraries
- comment about unset meson config options
changes since v2 available at https://lore.ptxdist.org/ptxdist/ZjtM5u8mjdcZjx-B@pengutronix.de/:
- use SECTION=system_libraries, sorry missed that when sending v2 :-\
Michael requested that I explicitly set all configuration options to
their default value. This felt wrong as most of them don't matter when
documentation is disabled (which is the case here). So as a suggested
compromise I explicitly listed the unset options.
Best regards
Uwe
Uwe Kleine-König (2):
libtraceevent: new package
kernel/perf: Make use of libtraceevent
rules/kernel.in | 1 +
rules/kernel.make | 1 -
rules/libtraceevent.in | 8 +++++
rules/libtraceevent.make | 70 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 79 insertions(+), 1 deletion(-)
create mode 100644 rules/libtraceevent.in
create mode 100644 rules/libtraceevent.make
base-commit: 9de477ba07b1778daa58537121091d9f3b8ea670
--
2.39.2
next reply other threads:[~2024-05-15 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 7:22 Uwe Kleine-König [this message]
2024-05-15 7:22 ` [ptxdist] [PATCH v3 1/2] libtraceevent: new package Uwe Kleine-König
2024-05-21 9:58 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-05-15 7:22 ` [ptxdist] [PATCH v3 2/2] kernel/perf: Make use of libtraceevent Uwe Kleine-König
2024-05-21 9:58 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20240515072254.12082-4-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=m.tretter@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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