From: Chetan Sethi <cpsethi369@gmail.com>
To: gregkh@linuxfoundation.org
Cc: wsa@the-dreams.de, shiva@exdev.nl, punitvara@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Chetan Sethi <cpsethi369@gmail.com>
Subject: [PATCH v4 5/6] staging: ks7010: fix coding style issue of using __func__ instead of __FUNCTION__
Date: Sun, 26 Feb 2017 16:02:49 +0900 [thread overview]
Message-ID: <1488092569-18004-1-git-send-email-cpsethi369@gmail.com> (raw)
In-Reply-To: <1488092374-17737-1-git-send-email-cpsethi369@gmail.com>
This patch fixes coding style issue of using __func__ instead of gcc
specific __FUNCTION__, warning as issued by checkpatch
Signed-off-by: Chetan Sethi <cpsethi369@gmail.com>
---
v2:
- split multiple changes across different patches
v3:
- mentioned patch revision in subject
v4:
- modified description to exclude mention of patch number from changelog
- updated subject to include driver name
drivers/staging/ks7010/ks_wlan.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ks7010/ks_wlan.h b/drivers/staging/ks7010/ks_wlan.h
index 78beca7..79737bf 100644
--- a/drivers/staging/ks7010/ks_wlan.h
+++ b/drivers/staging/ks7010/ks_wlan.h
@@ -38,7 +38,7 @@
#define DPRINTK(n, fmt, args...) \
do { \
if (KS_WLAN_DEBUG > (n)) \
- pr_notice("%s: "fmt, __FUNCTION__, ## args); \
+ pr_notice("%s: "fmt, __func__, ## args); \
} while (0)
#else
#define DPRINTK(n, fmt, args...)
--
2.7.4
next prev parent reply other threads:[~2017-02-26 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 6:59 [PATCH v4 1/6] staging: ks7010: fixed warning of avoiding line over 80 characters Chetan Sethi
2017-02-26 7:01 ` [PATCH v4 2/6] staging: ks7010: fix coding style issue of enclosing complex macro value in parentheses Chetan Sethi
2017-02-27 14:46 ` Greg KH
2017-02-28 2:59 ` [PATCH v5 1/5] staging: ks7010: fixed warning of avoiding line over 80 characters Chetan Sethi
2017-02-28 3:00 ` [PATCH v5 2/5] staging: ks7010: fix coding style issue of enclosing complex macro value in parentheses Chetan Sethi
2017-02-28 3:00 ` [PATCH v5 3/5] staging: ks7010: fix coding style issue of using pr_notice instead of printk Chetan Sethi
2017-02-28 3:01 ` [PATCH v5 4/5] staging: ks7010: fix coding style issue of using __func__ instead of __FUNCTION__ Chetan Sethi
2017-02-28 3:01 ` [PATCH v5 5/5] staging: ks7010: fix coding style issue of aligning comments properly Chetan Sethi
2017-02-28 19:26 ` [PATCH v5 1/5] staging: ks7010: fixed warning of avoiding line over 80 characters Greg KH
2017-02-28 19:27 ` Greg KH
2017-02-26 7:01 ` [PATCH v4 3/6] staging: ks7010: fix coding style issue of using tabs instead of spaces Chetan Sethi
2017-02-26 7:02 ` [PATCH v4 4/6] staging: ks7010: fix coding style issue of using pr_notice instead of printk Chetan Sethi
2017-02-26 7:02 ` Chetan Sethi [this message]
2017-02-26 7:03 ` [PATCH v4 6/6] staging: ks7010: fix coding style issue of aligning comments properly Chetan Sethi
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=1488092569-18004-1-git-send-email-cpsethi369@gmail.com \
--to=cpsethi369@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=punitvara@gmail.com \
--cc=shiva@exdev.nl \
--cc=wsa@the-dreams.de \
/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