From: Philipp Hahn <phahn-oss@avm.de>
To: jim.cromie@gmail.com
Cc: Jason Baron <jbaron@akamai.com>,
linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: dyndbg: pr_fmt(fmt) with additional arguments?
Date: Tue, 17 Mar 2026 21:41:32 +0100 [thread overview]
Message-ID: <abm8fHlgrDSo-9zI@mail-auth.avm.de> (raw)
In-Reply-To: <CAJfuBxyATqdrYNLNgBJDdZeodruu3enUHLtHWz0bLDgL=K4ixA@mail.gmail.com>
Hello Jim,
Am Sun, Mar 15, 2026 at 05:30:43PM -0600 schrieb jim.cromie@gmail.com:
> On Fri, Feb 27, 2026 at 4:12 AM Philipp Hahn <phahn-oss@avm.de> wrote:
> >
> > Hello Jason, hello Jim,
> >
> > I've been using the following in my modules to prefix all messages with
> > the module and function name:
> > #define pr_fmt(fmt) KBUILD_MODNAME ".%s ", __func__
>
> Your example loses the fmt, so is not actually useful.
Yes, somehow that 'fmt' got lost; I've re-added it.
> but that said, the compile err is real, I hit it once I changed
>
> 1 - the pr_debug("exited") call in test_dynamic_debug.c
> to pr_debug_ratelimited.
>
> 2- the pr_fmt in same:
> #if defined(TEST_DYNAMIC_DEBUG_SUBMOD)
> - #define pr_fmt(fmt) "test_dd_submod: " fmt
> + #define pr_fmt(fmt) KBUILD_MODNAME " test_dd_submod: %s" fmt, __func__
>
> 2 was my test-case, on my latest branch, yours (on master) will be different.
>
> please add that test to your patch, and my
> Acked-by: Jim Cromie <jim.cromie@gmail.com>
I did both; v2 is on it's way. Thank you for your review.
Philipp Hahn
next prev parent reply other threads:[~2026-03-17 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 11:12 Philipp Hahn
2026-03-13 12:55 ` Philipp Hahn
2026-03-15 23:30 ` jim.cromie
2026-03-17 20:41 ` Philipp Hahn [this message]
2026-03-17 20:39 ` [PATCH v2] dyndbg: Ignore additional arguments from pr_fmt Philipp Hahn
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=abm8fHlgrDSo-9zI@mail-auth.avm.de \
--to=phahn-oss@avm.de \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--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
Powered by JetHome