From: RishabhHardas <rishabheudyptula@gmail.com>
To: gilad@benyossef.com
Cc: gregkh@linuxfoundation.org, linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
RishabhHardas <rishabhhardas@gmail.com>
Subject: [PATCH] staging/ccree: Declare compiled out fuctions static inline
Date: Mon, 31 Jul 2017 14:47:23 +0530 [thread overview]
Message-ID: <1501492643-7087-1-git-send-email-rishabheudyptula@gmail.com> (raw)
From: RishabhHardas <rishabhhardas@gmail.com>
Sparse was giving out a warning for symbols 'cc_set_ree_fips_status' and 'fips_handler'
that they were not declared and need to be made static. This patch makes both the symbols
static inline, to remove the warnings.
Signed-off-by: RishabhHardas <rishabhhardas@gmail.com>
---
drivers/staging/ccree/ssi_fips.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/ccree/ssi_fips.h b/drivers/staging/ccree/ssi_fips.h
index 369ddf9..63bcca7 100644
--- a/drivers/staging/ccree/ssi_fips.h
+++ b/drivers/staging/ccree/ssi_fips.h
@@ -40,1 +40,1 @@ static inline int ssi_fips_init(struct ssi_drvdata *p_drvdata)
}
static inline void ssi_fips_fini(struct ssi_drvdata *drvdata) {}
-void cc_set_ree_fips_status(struct ssi_drvdata *drvdata, bool ok) {}
-void fips_handler(struct ssi_drvdata *drvdata) {}
+static inline void cc_set_ree_fips_status(struct ssi_drvdata *drvdata, bool ok) {}
+static inline void fips_handler(struct ssi_drvdata *drvdata) {}
#endif /* CONFIG_CRYPTO_FIPS */
next reply other threads:[~2017-07-31 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 9:17 RishabhHardas [this message]
2017-08-01 12:35 ` [PATCH] staging/ccree: Declare compiled out fuctions static inline Gilad Ben-Yossef
2017-08-16 22:09 ` Greg KH
2017-08-22 11:21 ` Rishabh Hardas
2017-08-22 11:52 ` Dan Carpenter
2017-08-22 13:39 ` Rishabh Hardas
2017-08-22 13:53 ` Dan Carpenter
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=1501492643-7087-1-git-send-email-rishabheudyptula@gmail.com \
--to=rishabheudyptula@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gilad@benyossef.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rishabhhardas@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