From: Arnd Bergmann <arnd@arndb.de>
To: Jessica Yu <jeyu@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Jiri Kosina <jikos@kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Miroslav Benes <mbenes@suse.cz>,
Anson Jacob <ansonjacob.aj@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] modules: mark __inittest/__exittest as __maybe_unused
Date: Wed, 1 Feb 2017 18:00:14 +0100 [thread overview]
Message-ID: <20170201170028.2645354-1-arnd@arndb.de> (raw)
clang warns about unused inline functions by default:
arch/arm/crypto/aes-cipher-glue.c:68:1: warning: unused function '__inittest' [-Wunused-function]
arch/arm/crypto/aes-cipher-glue.c:69:1: warning: unused function '__exittest' [-Wunused-function]
As these appear in every single module, let's just disable the warnings by marking the
two functions as __maybe_unused.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
include/linux/module.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/module.h b/include/linux/module.h
index 38b4b2c754c8..48a5c57c858e 100644
--- a/include/linux/module.h
+++ b/include/linux/module.h
@@ -126,13 +126,13 @@ extern void cleanup_module(void);
/* Each module must use one module_init(). */
#define module_init(initfn) \
- static inline initcall_t __inittest(void) \
+ static inline initcall_t __maybe_unused __inittest(void) \
{ return initfn; } \
int init_module(void) __attribute__((alias(#initfn)));
/* This is only required if you want to be unloadable. */
#define module_exit(exitfn) \
- static inline exitcall_t __exittest(void) \
+ static inline exitcall_t __maybe_unused __exittest(void) \
{ return exitfn; } \
void cleanup_module(void) __attribute__((alias(#exitfn)));
--
2.9.0
next reply other threads:[~2017-02-01 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 17:00 Arnd Bergmann [this message]
2017-02-02 9:25 ` [PATCH] modules: mark __inittest/__exittest as __maybe_unused Rusty Russell
2017-02-02 10:19 ` Arnd Bergmann
2017-02-02 18:55 ` Rusty Russell
2017-02-02 19:44 ` Miroslav Benes
2017-02-07 0:51 ` Jessica Yu
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=20170201170028.2645354-1-arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ansonjacob.aj@gmail.com \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=paul.gortmaker@windriver.com \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).