From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Felix Siegel <felix.siegel@posteo.de>
Cc: devel@driverdev.osuosl.org, John Joseph <jnjoseph@google.com>,
linux-kernel@vger.kernel.org, Rob Springer <rspringer@google.com>
Subject: Re: [PATCH 4/4] staging: gasket: Use __func__ instead of hardcoded string - Style
Date: Thu, 12 Jul 2018 21:53:17 +0200 [thread overview]
Message-ID: <20180712195317.GA28761@kroah.com> (raw)
In-Reply-To: <1531423694-22478-4-git-send-email-felix.siegel@posteo.de>
On Thu, Jul 12, 2018 at 09:27:15PM +0200, Felix Siegel wrote:
> Changed logging statements to use %s and __func__ instead of hard coding
> the function name in a string.
>
> Signed-off-by: Felix Siegel <felix.siegel@posteo.de>
> ---
> drivers/staging/gasket/apex_driver.c | 15 ++++++++-------
> drivers/staging/gasket/gasket_core.c | 11 ++++++-----
> drivers/staging/gasket/gasket_ioctl.c | 4 ++--
> drivers/staging/gasket/gasket_page_table.c | 13 ++++++++-----
> 4 files changed, 24 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/staging/gasket/apex_driver.c b/drivers/staging/gasket/apex_driver.c
> index ffcc59d..735d43d 100644
> --- a/drivers/staging/gasket/apex_driver.c
> +++ b/drivers/staging/gasket/apex_driver.c
> @@ -341,7 +341,7 @@ static int apex_add_dev_cb(struct gasket_dev *gasket_dev)
> ulong page_table_ready, msix_table_ready;
> int retries = 0;
>
> - gasket_log_error(gasket_dev, "apex_add_dev_cb.");
> + gasket_log_error(gasket_dev, "%s.", __func__);
Function calls that do nothing but log "Look at this function I just
entered/exited!" need to just be deleted entirely, as ftrace should be
used instead.
Care to do that here, and then send a patch for the remaining messages
that do need __func__?
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-12 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1531423694-22478-1-git-send-email-felix.siegel@posteo.de>
2018-07-12 19:27 ` [PATCH 2/4] staging: gasket: Move open-curly brace to match kernel code style Felix Siegel
2018-07-12 19:27 ` [PATCH 3/4] staging: gasket: fix multi line comments style Felix Siegel
2018-07-12 19:53 ` Greg Kroah-Hartman
2018-07-12 20:44 ` Felix Siegel
2018-07-12 19:27 ` [PATCH 4/4] staging: gasket: Use __func__ instead of hardcoded string - Style Felix Siegel
2018-07-12 19:53 ` Greg Kroah-Hartman [this message]
2018-07-12 19:42 ` [PATCH 1/4] staging: gasket: add SPDX-License-Identifier tag Greg Kroah-Hartman
2018-07-12 20:28 ` Felix Siegel
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=20180712195317.GA28761@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=felix.siegel@posteo.de \
--cc=jnjoseph@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rspringer@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