From: "tip-bot for H. Peter Anvin" <hpa@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, sliakh.lkml@gmail.com,
hpa@zytor.com, mingo@redhat.com, tglx@linutronix.de,
jiang@cs.ncsu.edu
Subject: [tip:x86/mm] module: fix () used as prototype in include/linux/module.h
Date: Wed, 17 Feb 2010 19:52:12 GMT [thread overview]
Message-ID: <tip-45d5f58b53a055913fee4351cb3ce1133d3c5261@git.kernel.org> (raw)
In-Reply-To: <tip-7f5562635f80456c98d573cc45d10137dfcb1b8b@git.kernel.org>
Commit-ID: 45d5f58b53a055913fee4351cb3ce1133d3c5261
Gitweb: http://git.kernel.org/tip/45d5f58b53a055913fee4351cb3ce1133d3c5261
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Mon, 1 Feb 2010 17:33:56 -0800
Committer: H. Peter Anvin <hpa@zytor.com>
CommitDate: Wed, 17 Feb 2010 10:11:24 -0800
module: fix () used as prototype in include/linux/module.h
Checkin 7f5562635f80456c98d573cc45d10137dfcb1b8b had () used as a
prototype, which means (void) in C++, but means (...) in C, which is
almost never correct, and therefore issues a warning. Change it to
the properly intended (void).
Cc: Siarhei Liakh <sliakh.lkml@gmail.com>
Cc: Xuxian Jiang <jiang@cs.ncsu.edu>
LKML-Reference: <tip-7f5562635f80456c98d573cc45d10137dfcb1b8b@git.kernel.org>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
include/linux/module.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/module.h b/include/linux/module.h
index c6040ce..3232b31 100644
--- a/include/linux/module.h
+++ b/include/linux/module.h
@@ -668,11 +668,11 @@ static inline int module_get_iter_tracepoints(struct tracepoint_iter *iter)
return 0;
}
-static inline void set_all_modules_text_rw()
+static inline void set_all_modules_text_rw(void)
{
}
-static inline void set_all_modules_text_ro()
+static inline void set_all_modules_text_ro(void)
{
}
#endif /* CONFIG_MODULES */
parent reply other threads:[~2010-02-17 19:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tip-7f5562635f80456c98d573cc45d10137dfcb1b8b@git.kernel.org>]
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=tip-45d5f58b53a055913fee4351cb3ce1133d3c5261@git.kernel.org \
--to=hpa@zytor.com \
--cc=jiang@cs.ncsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sliakh.lkml@gmail.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome