From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: pebolle@tiscali.nl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] tracing: Remove redundant module.h includes
Date: Fri, 10 Apr 2015 12:27:03 -0400 [thread overview]
Message-ID: <20150410122703.52fcfe4c@gandalf.local.home> (raw)
In-Reply-To: <c4cca918b8a38d269de1855400363208ec2e2d89.1428678555.git.tom.zanussi@linux.intel.com>
On Fri, 10 Apr 2015 11:05:02 -0500
Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> kallsyms.h now includes module.h, so remove module.h includes that
> were apparently there only to satisfy kallsyms use of MODULE_NAME_LEN.
Only remove it for those that need it for MODULE_NAME_LEN because it
was used in KSYM_SYMBOL_LEN. But not the rest. Lots of these files use
module code directly. Now you made it require kallsyms.h to get to that
code. If for some reason we no longer need kallsyms.h, or that
kallsyms.h no longer needs module.h, these files will not build.
If code uses module code, it must include module.h.
So NACK for this patch.
To see what needs module.h, before reverting this patch, remove the
module.h from kallsyms.h, and also remove the MODULE_NAME_LEN from it as
well. Compile all the tracing code, and see what does not build. Those
files will be the ones that you need to add back the module.h to.
-- Steve
next prev parent reply other threads:[~2015-04-10 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 16:04 [PATCH 0/4] kallsyms header cleanup Tom Zanussi
2015-04-10 16:05 ` [PATCH 1/4] tracing: Remove kallsyms.h include from linux/ftrace.h Tom Zanussi
2015-04-10 16:05 ` [PATCH 2/4] kallsyms: Add module.h include Tom Zanussi
2015-04-10 16:05 ` [PATCH 3/4] tracing: Remove redundant module.h includes Tom Zanussi
2015-04-10 16:27 ` Steven Rostedt [this message]
2015-04-10 18:25 ` Tom Zanussi
2015-04-10 18:54 ` Steven Rostedt
2015-04-10 16:05 ` [PATCH 4/4] lib: " Tom Zanussi
2015-04-10 16:28 ` Steven Rostedt
2015-04-10 18:27 ` Tom Zanussi
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=20150410122703.52fcfe4c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=tom.zanussi@linux.intel.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
all inboxes | Powered by JetHome®