From: Jessica Yu <jeyu@kernel.org>
To: Mathieu Malaterre <malat@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/module: silence a gcc warning
Date: Mon, 16 Apr 2018 19:11:06 +0200 [thread overview]
Message-ID: <20180416171106.rlm2nrvrxfoodcvf@redbean> (raw)
In-Reply-To: <20180411190509.24995-1-malat@debian.org>
+++ Mathieu Malaterre [11/04/18 21:05 +0200]:
>In commit 8c8ef42aee8f ("module: include other structures in module version
>check"), the function `struct_module` was renamed to `module_layout` but no
>prototype was added to `include/linux/module.h`. Remove warning triggered
>at W=1:
>
> kernel/module.c:4378:6: warning: no previous prototype for ‘module_layout’ [-Wmissing-prototypes]
>
>Signed-off-by: Mathieu Malaterre <malat@debian.org>
>---
> include/linux/module.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
>diff --git a/include/linux/module.h b/include/linux/module.h
>index d44df9b2c131..28046e8b7e9d 100644
>--- a/include/linux/module.h
>+++ b/include/linux/module.h
>@@ -786,6 +786,14 @@ extern int module_sysfs_initialized;
>
> #define symbol_request(x) try_then_request_module(symbol_get(x), "symbol:" #x)
>
>+#ifdef CONFIG_MODVERSIONS
>+void module_layout(struct module *mod,
>+ struct modversion_info *ver,
>+ struct kernel_param *kp,
>+ struct kernel_symbol *ks,
>+ struct tracepoint * const *tp);
>+#endif /* CONFIG_MODVERSIONS */
>+
Hi Mathieu,
We're going to need a forward declaration in module.h for struct tracepoint
to address the kbuild warnings.
Thanks,
Jessica
> /* BELOW HERE ALL THESE ARE OBSOLETE AND WILL VANISH */
>
> #define __MODULE_STRING(x) __stringify(x)
>--
>2.11.0
>
next prev parent reply other threads:[~2018-04-16 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 19:05 Mathieu Malaterre
2018-04-13 1:42 ` kbuild test robot
2018-04-13 3:08 ` kbuild test robot
2018-04-16 17:11 ` Jessica Yu [this message]
2018-04-19 17:15 ` Mathieu Malaterre
2018-04-23 18:41 ` Mathieu Malaterre
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=20180416171106.rlm2nrvrxfoodcvf@redbean \
--to=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malat@debian.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®