From: Daniel Thompson <daniel.thompson@linaro.org>
To: Stephen Zhang <stephenzhangzsd@gmail.com>
Cc: jason.wessel@windriver.com, dianders@chromium.org,
gustavoars@kernel.org, kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] kdb: kdb_support: Fix debugging information problem
Date: Thu, 4 Feb 2021 15:56:35 +0000 [thread overview]
Message-ID: <20210204155635.ibvnyzo7qqgysfhl@maple.lan> (raw)
In-Reply-To: <1612440429-6391-1-git-send-email-stephenzhangzsd@gmail.com>
On Thu, Feb 04, 2021 at 08:07:09PM +0800, Stephen Zhang wrote:
> There are several common patterns.
>
> 0:
> kdb_printf("...",...);
>
> which is the normal one.
>
> 1:
> kdb_printf("%s: "...,__func__,...)
>
> We could improve '1' to this :
>
> #define kdb_func_printf(format, args...) \
> kdb_printf("%s: " format, __func__, ## args)
>
> 2:
> if(KDB_DEBUG(AR))
> kdb_printf("%s "...,__func__,...);
>
> We could improve '2' to this :
> #define kdb_dbg_printf(mask, format, args...) \
> do { \
> if (KDB_DEBUG(mask)) \
> kdb_func_printf(format, ## args); \
This line is picked up by checkpatch as being overlong.
> } while (0)
>
> In additon, we changed the format code of size_t to %zu.
Should be `addition`.
> Signed-off-by: Stephen Zhang <stephenzhangzsd@gmail.com>
It is arguable that there should be a Reviewed-by: from Doug here...
although given the big changes in v3 I don't think you were wrong
to drop it.
Nevertheless... given the implicit R-b ("when Daniel merges") in Doug's
comments on v3 I decided to reinstate it.
No action needed from you on this. I have fixed up all these issues
when I applied the patch. Thanks!
Daniel.
prev parent reply other threads:[~2021-02-04 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 12:07 Stephen Zhang
2021-02-04 15:56 ` Daniel Thompson [this message]
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=20210204155635.ibvnyzo7qqgysfhl@maple.lan \
--to=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=gustavoars@kernel.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stephenzhangzsd@gmail.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®