From: Guillaume Clement <gclement@baobob.org>
To: Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Guillaume Clement <gclement@baobob.org>
Subject: [PATCH 2/5] staging: vt6655:fix warning for unexported non-static functions
Date: Tue, 22 Jul 2014 22:08:27 +0200 [thread overview]
Message-ID: <1406059710-30903-3-git-send-email-gclement@baobob.org> (raw)
In-Reply-To: <1406059710-30903-1-git-send-email-gclement@baobob.org>
There is one function in aes_ccmp.c which is exported, but sparse sees
it unexported because it doesn't include the header that exports it.
Signed-off-by: Guillaume Clement <gclement@baobob.org>
---
drivers/staging/vt6655/aes_ccmp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/vt6655/aes_ccmp.c b/drivers/staging/vt6655/aes_ccmp.c
index 4ccfe06..a25e6cf 100644
--- a/drivers/staging/vt6655/aes_ccmp.c
+++ b/drivers/staging/vt6655/aes_ccmp.c
@@ -35,6 +35,7 @@
#include "device.h"
#include "80211hdr.h"
+#include "aes_ccmp.h"
/*--------------------- Static Definitions -------------------------*/
--
1.8.5.5
next prev parent reply other threads:[~2014-07-22 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 20:08 [PATCH 0/5] staging: vt6655: fix sparse issues Guillaume Clement
2014-07-22 20:08 ` [PATCH 1/5] staging: vt6655: change type of PortOffset to void __iomem * Guillaume Clement
2014-07-22 22:01 ` Greg Kroah-Hartman
2014-07-22 20:08 ` Guillaume Clement [this message]
2014-07-22 20:08 ` [PATCH 3/5] staging: vt6655: statify some variables Guillaume Clement
2014-07-22 20:08 ` [PATCH 4/5] staging: vt6655: remove unused functions Guillaume Clement
2014-07-22 20:08 ` [PATCH 5/5] staging: vt6655: Fix unused function warning Guillaume Clement
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=1406059710-30903-3-git-send-email-gclement@baobob.org \
--to=gclement@baobob.org \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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®