From: Konrad Zapalowicz <bergo.torino@gmail.com>
To: gregkh@linuxfoundation.org
Cc: standby24x7@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
Konrad Zapalowicz <bergo.torino@gmail.com>
Subject: [PATCH 1/2] staging: rtl8821ae: fix double const in sw.c
Date: Sat, 17 May 2014 21:23:37 +0200 [thread overview]
Message-ID: <1400354618-13471-2-git-send-email-bergo.torino@gmail.com> (raw)
In-Reply-To: <1400354618-13471-1-git-send-email-bergo.torino@gmail.com>
This commit fixes the following sparse warning:
drivers/staging/rtl8821ae/rtl8821ae/sw.c:
- 449:14: warning: duplicate const
Signed-off-by: Konrad Zapalowicz <bergo.torino@gmail.com>
---
drivers/staging/rtl8821ae/rtl8821ae/sw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8821ae/rtl8821ae/sw.c b/drivers/staging/rtl8821ae/rtl8821ae/sw.c
index a8d1755..c24d426 100644
--- a/drivers/staging/rtl8821ae/rtl8821ae/sw.c
+++ b/drivers/staging/rtl8821ae/rtl8821ae/sw.c
@@ -446,7 +446,7 @@ MODULE_PARM_DESC(ips, "using no link power save (default 1 is open)\n");
MODULE_PARM_DESC(fwlps, "using linked fw control power save (default 1 is open)\n");
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,29))
-static const SIMPLE_DEV_PM_OPS(rtlwifi_pm_ops, rtl_pci_suspend, rtl_pci_resume);
+static SIMPLE_DEV_PM_OPS(rtlwifi_pm_ops, rtl_pci_suspend, rtl_pci_resume);
#endif
#if (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,29))
--
1.8.1.2
next prev parent reply other threads:[~2014-05-17 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 19:23 [PATCH 0/2] staging: rtl8821ae: fix sparse warnings " Konrad Zapalowicz
2014-05-17 19:23 ` Konrad Zapalowicz [this message]
2014-05-17 19:23 ` [PATCH 2/2] staging: rtl8821ae: fix not declared symbols should be static " Konrad Zapalowicz
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=1400354618-13471-2-git-send-email-bergo.torino@gmail.com \
--to=bergo.torino@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@gmail.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
all inboxes | Powered by JetHome®