From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bhanusree Pola <bhanusreemahesh@gmail.com>
Cc: outreachy-kernel@googlegroups.com,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] Staging: rtlwifi: rtl8822be: Use __func__ instead of func name
Date: Tue, 26 Feb 2019 11:42:26 +0100 [thread overview]
Message-ID: <20190226104226.GA20764@kroah.com> (raw)
In-Reply-To: <20190226002243.15322-1-bhanusreemahesh@gmail.com>
On Tue, Feb 26, 2019 at 05:52:43AM +0530, Bhanusree Pola wrote:
> Fix checkpatch warning:
> WARNING: Prefer using '"%s...", __func__' to using 'rtl8822be_set_fw_rsvdpagepkt', this function's name, in a string
>
> Use __func__ instead of using complete function name.
> Avoid line over 80 characters
>
> Signed-off-by: Bhanusree Pola <bhanusreemahesh@gmail.com>
> ---
> drivers/staging/rtlwifi/rtl8822be/fw.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtlwifi/rtl8822be/fw.c b/drivers/staging/rtlwifi/rtl8822be/fw.c
> index f061dd1382aa..43a56962e37a 100644
> --- a/drivers/staging/rtlwifi/rtl8822be/fw.c
> +++ b/drivers/staging/rtlwifi/rtl8822be/fw.c
> @@ -736,10 +736,10 @@ void rtl8822be_set_fw_rsvdpagepkt(struct ieee80211_hw *hw, bool b_dl_finished)
> totalpacketlen = TOTAL_RESERVED_PKT_LEN;
>
> RT_PRINT_DATA(rtlpriv, COMP_CMD, DBG_LOUD,
> - "rtl8822be_set_fw_rsvdpagepkt(): HW_VAR_SET_TX_CMD: ALL\n",
> + ("%s: HW_VAR_SET_TX_CMD: ALL\n", __func__),
You did not even compile your change :(
This is not correct C, please fix up and always test your patches before
sending them out.
thanks,
greg k-h
prev parent reply other threads:[~2019-02-26 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 0:22 [PATCH] Staging: rtlwifi: rtl8822be: Use __func__ instead of func name Bhanusree Pola
2019-02-26 10:42 ` Greg Kroah-Hartman [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=20190226104226.GA20764@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=bhanusreemahesh@gmail.com \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.