From: Louis Chauvet <louis.chauvet@bootlin.com>
To: "Łukasz Bartosik" <ukaszb@chromium.org>,
"Jason Baron" <jbaron@akamai.com>,
"Jim Cromie" <jim.cromie@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Kees Cook" <keescook@chromium.org>,
"Douglas Anderson" <dianders@chromium.org>
Cc: Guenter Roeck <groeck@google.com>,
Yaniv Tzoreff <yanivt@google.com>,
Benson Leung <bleung@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
Pekka Paalanen <ppaalanen@gmail.com>,
Sean Paul <seanpaul@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>, Simon Ser <contact@emersion.fr>,
John Ogness <john.ogness@linutronix.de>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org, upstream@semihalf.com
Subject: Re: [PATCH v4 00/39] dyndbg: add support for writing debug logs to trace
Date: Wed, 5 Mar 2025 17:49:40 +0100 [thread overview]
Message-ID: <a96af07c-b8ee-4a9e-91c8-d5d6cd1d9cb0@bootlin.com> (raw)
In-Reply-To: <20240210235009.2405808-1-ukaszb@chromium.org>
Hi everyone,
I am looking for an update on the status of this series. Initially, I
intended to implement DRM logging in the trace system as suggested by
Sean in [1].
However, I came across this series which seems to offer a more
comprehensive solution by enabling DRM logging system-wide. I have
tested it, and it appears to work as expected after rebasing on top of
drm-misc-next.
Would it be appropriate for me to send a new version of this series with
a minor fix for the rebase?
Additionally, I haven't seen any reviews for this series yet. Have I
missed something?
Thanks,
Louis Chauvet
[1]:https://patchwork.kernel.org/project/dri-devel/cover/20200608210505.48519-1-sean@poorly.run/
--
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-03-05 16:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 23:49 Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 01/39] dyndbg: add _DPRINTK_FLAGS_ENABLED Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 02/39] dyndbg: add _DPRINTK_FLAGS_TRACE Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 03/39] dyndbg: add write events to tracefs code Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 04/39] dyndbg: add 2 trace-events: prdbg, devdbg Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 05/39] tracefs: add __get_str_strip_nl Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 06/39] dyndbg: use __get_str_strip_nl in prdbg and devdbg Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 07/39] dyndbg: repack _ddebug structure Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 08/39] dyndbg: move flags field to a new structure Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 09/39] dyndbg: add trace destination field to _ddebug Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 10/39] dyndbg: add open and close commands for trace Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 11/39] dyndbg: don't close trace instance when in use Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 12/39] dyndbg: handle [+T]:buf_name.flags grammar Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 13/39] dyndbg: add support for default trace destination Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 14/39] dyndbg: update default trace destination on reopen Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 15/39] dyndbg: update selection of trace destination Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 16/39] dyndbg: write debug logs to trace instance Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 17/39] dyndbg: add support for hex_dump output to trace Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 18/39] dyndbg: add label keyword handling Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 19/39] dyndbg: fix old BUG_ON in >control parser Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 20/39] dyndbg: treat comma as a token separator Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 21/39] dyndbg: split multi-query strings with % Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 22/39] dyndbg: reduce verbose/debug clutter Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 23/39] dyndbg: display the bad flag-val in parse-flags err msg Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 24/39] dyndbg: report err in ddebug_parse_flags when read_args fails Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 25/39] dyndbg: don't process queries when trace cmd fails Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 26/39] dyndbg: warn if no flags are given Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 27/39] dyndbg: update "ddcmd =:foo" behavior Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 28/39] dyndbg: don't show default trace destination "0" Łukasz Bartosik
2024-02-10 23:49 ` [PATCH v4 29/39] dyndbg-test: add tools/testing/selftests/dynamic_debug/* Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 30/39] dyndbg-test: fixup search-trace-name help Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 31/39] dyndbg-test: test_private_trace_mixed_class - parameterize modname Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 32/39] dyndbg-test: refactor test_private_trace_* tests Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 33/39] dyndbg-test: setup environment for tests execution Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 34/39] dyndbg-test: add test which verifies flags and dst Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 35/39] dyndbg-test: add test which verifies default dst Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 36/39] dyndbg-test: add test for label keyword Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 37/39] docs/dyndbg: update examples \012 to \n Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 38/39] docs/dyndbg: explain new delimiters: comma, percent Łukasz Bartosik
2024-02-10 23:50 ` [PATCH v4 39/39] docs/dyndbg: explain debug-to-tracefs (=T:label.flags) Łukasz Bartosik
2025-03-05 16:49 ` Louis Chauvet [this message]
2025-03-12 16:45 ` [PATCH v4 00/39] dyndbg: add support for writing debug logs to trace jim.cromie
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=a96af07c-b8ee-4a9e-91c8-d5d6cd1d9cb0@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=akpm@linux-foundation.org \
--cc=bleung@google.com \
--cc=contact@emersion.fr \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@google.com \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=ppaalanen@gmail.com \
--cc=rostedt@goodmis.org \
--cc=seanpaul@chromium.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=ukaszb@chromium.org \
--cc=upstream@semihalf.com \
--cc=vincent.whitchurch@axis.com \
--cc=yanivt@google.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
all inboxes | Powered by JetHome®