From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>, Jason Baron <jbaron@akamai.com>
Subject: Re: [PATCH 0/3] dyndbg: add source file name to prefix
Date: Mon, 20 Mar 2023 22:13:10 +0000 [thread overview]
Message-ID: <705ae57b-80af-4fae-a0c6-827db39711a6@t-8ch.de> (raw)
In-Reply-To: <20221223-dyndbg-filename-v1-0-cbf8543009a1@weissschuh.net>
Hi Jim,
did you get a chance to look at this yet?
Thanks,
Thomas
On Mon, Jan 30, 2023 at 02:01:17AM +0000, Thomas Weißschuh wrote:
> Currently dyndbg has no facility to print the source file name of a
> debug statement.
> Without the source file the line number is of limited use.
> Also the dyndbg control file uses the filename as the primary index, so
> having it in the logmessage makes the relation clearer.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Thomas Weißschuh (3):
> dyndbg: constify opt_array
> dyndbg: increase PREFIX_SIZE to 128
> dyndbg: add source filename to prefix
>
> Documentation/admin-guide/dynamic-debug-howto.rst | 5 +++--
> include/linux/dynamic_debug.h | 4 +++-
> lib/dynamic_debug.c | 8 ++++++--
> 3 files changed, 12 insertions(+), 5 deletions(-)
> ---
> base-commit: 6d796c50f84ca79f1722bb131799e5a5710c4700
> change-id: 20221223-dyndbg-filename-02e0879dae4b
>
> Best regards,
> --
> Thomas Weißschuh <linux@weissschuh.net>
>
next prev parent reply other threads:[~2023-03-20 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 2:01 [PATCH 0/3] dyndbg: add source file name to prefix Thomas Weißschuh
2023-01-30 2:01 ` [PATCH 1/3] dyndbg: constify opt_array Thomas Weißschuh
2023-01-30 2:01 ` [PATCH 2/3] dyndbg: increase PREFIX_SIZE to 128 Thomas Weißschuh
2023-01-30 2:01 ` [PATCH 3/3] dyndbg: add source filename to prefix Thomas Weißschuh
2023-02-03 16:45 ` Jason Baron
2023-02-04 14:49 ` linux
2023-03-22 15:54 ` jim.cromie
2023-03-20 22:13 ` Thomas Weißschuh [this message]
2023-06-27 14:30 ` [PATCH 0/3] dyndbg: add source file name " Thomas Weißschuh
2023-06-27 14:47 ` Greg Kroah-Hartman
2023-06-27 14:57 ` Thomas Weißschuh
2023-06-27 15:01 ` Greg Kroah-Hartman
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=705ae57b-80af-4fae-a0c6-827db39711a6@t-8ch.de \
--to=linux@weissschuh.net \
--cc=corbet@lwn.net \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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