From: Joe Perches <joe@perches.com>
To: Gaurav Pathak <gauravpathak129@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replaced Function name in debug print with %s..., __func__
Date: Sun, 02 Jul 2017 09:13:45 -0700 [thread overview]
Message-ID: <1499012025.9885.5.camel@perches.com> (raw)
In-Reply-To: <1499004704-22473-1-git-send-email-gauravpathak129@gmail.com>
On Sun, 2017-07-02 at 19:41 +0530, Gaurav Pathak wrote:
> Signed-off-by: Gaurav Pathak <gauravpathak129@gmail.com>
Need a different subject like:
[PATCH] staging: rts5208: Replace embedded function names with "%s: ", __func__
and you also require some change log like
Avoid possible defects when refactoring.
> diff --git a/drivers/staging/rts5208/ms.c b/drivers/staging/rts5208/ms.c
[]
> @@ -3064,7 +3064,8 @@ static int mspro_rw_multi_sector(struct scsi_cmnd *srb,
>
> if (detect_card_cd(chip, MS_CARD) != STATUS_SUCCESS) {
> chip->rw_need_retry = 0;
> - dev_dbg(rtsx_dev(chip), "No card exist, exit mspro_rw_multi_sector\n");
> + dev_dbg(rtsx_dev(chip), "No card exist, %s\n",
> + __func__);
try not to change output too.
You could also drop what appear to be function tracing
style logging where the message is the equivalent of:
void func(args...)
{
dev_dbg("%s: entered\n", __func__)
...
}
as the generic function tracing mechanism works well.
next prev parent reply other threads:[~2017-07-02 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 14:11 [PATCH] Replaced Function name in debug print with %s..., __func__ Gaurav Pathak
2017-07-02 16:13 ` Joe Perches [this message]
2017-07-04 19:39 ` kbuild test robot
2017-07-04 19:47 ` kbuild test robot
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=1499012025.9885.5.camel@perches.com \
--to=joe@perches.com \
--cc=gauravpathak129@gmail.com \
--cc=gregkh@linuxfoundation.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