From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
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 13:25:04 -0500 [thread overview]
Message-ID: <1428690304.19714.37.camel@picadillo> (raw)
In-Reply-To: <20150410122703.52fcfe4c@gandalf.local.home>
On Fri, 2015-04-10 at 12:27 -0400, Steven Rostedt wrote:
> 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.
>
I had grepped all those files for 'module' and didn't find anything
other than comments. The only files of those affected that use
KSYM_SYMBOL_LEN are trace_output and trace_syscalls, so I can respin the
patch including just those.
But I don't see that any of the other files really use module code, and
looking at those again, none of them seem to need kallsyms either so
they could remove those includes as well... But I agree all that that
probably doesn't belong as part of this patchset.
> 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.
>
Yeah, doing that I didn't see any build errors, but I'll stick with just
the explicit KSYM_SYMBOL_LEN-using files for this patchset to keep
things restricted to the specific case at hand.
Tom
> -- Steve
>
next prev parent reply other threads:[~2015-04-10 18:25 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
2015-04-10 18:25 ` Tom Zanussi [this message]
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=1428690304.19714.37.camel@picadillo \
--to=tom.zanussi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.