LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul McQuade <paulmcquad@gmail.com>
To: paulmcquad@gmail.com
Cc: devel@driverdev.osuosl.org, keescook@chromium.org,
johannes.berg@intel.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, Linyu.Yuan@alcatel-sbell.com.cn,
hdegoede@redhat.com, arnd@arndb.de, arvind.yadav.cs@gmail.com,
colin.king@canonical.com, davem@davemloft.net,
Larry.Finger@lwfinger.net
Subject: [v2 PATCH 1/5] Staging:rtl8723bs static variables are always 0
Date: Tue, 20 Mar 2018 20:26:18 +0000 [thread overview]
Message-ID: <20180320202622.13339-1-paulmcquad@gmail.com> (raw)
C standard guarantees that:
global and static variables will be implicitly initialized to 0 or NULL
if no explicit initializer is given.
Signed-off-by: Paul McQuade <paulmcquad@gmail.com>
---
drivers/staging/rtl8723bs/os_dep/rtw_proc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/rtw_proc.c b/drivers/staging/rtl8723bs/os_dep/rtw_proc.c
index 9a885e626d1c..37ee8d90709a 100644
--- a/drivers/staging/rtl8723bs/os_dep/rtw_proc.c
+++ b/drivers/staging/rtl8723bs/os_dep/rtw_proc.c
@@ -19,7 +19,7 @@
#ifdef PROC_DEBUG
-static struct proc_dir_entry *rtw_proc = NULL;
+static struct proc_dir_entry *rtw_proc;
#define RTW_PROC_NAME "rtl8723bs"
--
2.16.2
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2018-03-20 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 20:26 Paul McQuade [this message]
2018-03-20 20:26 ` [v2 PATCH 2/5] Staging:rtl8723bs clean up spaces Paul McQuade
2018-03-20 20:26 ` [v2 PATCH 3/5] Staging:rtl8723bs Remove unnecessary braces Paul McQuade
2018-03-20 20:26 ` [v2 PATCH 4/5] Staging:rtl8723bs:Add blank line after declaration Paul McQuade
2018-03-20 20:26 ` [v2 PATCH 5/5] Staging:rtl8723bs clean spaces Paul McQuade
2018-03-20 20:32 ` Joe Perches
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=20180320202622.13339-1-paulmcquad@gmail.com \
--to=paulmcquad@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=Linyu.Yuan@alcatel-sbell.com.cn \
--cc=arnd@arndb.de \
--cc=arvind.yadav.cs@gmail.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=johannes.berg@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [v2 PATCH 1/5] Staging:rtl8723bs static variables are always 0' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).