From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: [RFC][PATCH 0/2] kbuild: create force-deps for fixdep for recordmcount
Date: Mon, 16 May 2011 22:10:27 -0400 [thread overview]
Message-ID: <20110517021027.390391519@goodmis.org> (raw)
While doing a ktest patchcheck on several patches I've pulled,
an update to recordmcount caused ftrace to fail. This is because
ktest does a make mrproper for the first patch, but just uses the
dependencies for the patches after that. But one of the patches
modified both the way recordmcount worked, and what ftrace expected
in the kernel. Since modification of recordmcount does not force
updates to all object files, the expectation that ftrace had on
the object files was incorrect and caused ftrace to fail.
This is an RFC to modify fixdep to allow addition of files that would
be added as dependencies to all objects in the kernel.
Thoughts?
Steven Rostedt (2):
kbuild: Add force-deps to fixdep
ftrace/kbuild: Add recordmcount files to force full build
----
scripts/Kbuild.include | 3 ++-
scripts/Makefile.build | 6 ++++--
scripts/basic/fixdep.c | 18 ++++++++++++++++--
3 files changed, 22 insertions(+), 5 deletions(-)
next reply other threads:[~2011-05-17 2:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 2:10 Steven Rostedt [this message]
2011-05-17 2:10 ` [RFC][PATCH 1/2] kbuild: Add force-deps to fixdep Steven Rostedt
2011-05-17 2:10 ` [RFC][PATCH 2/2] ftrace/kbuild: Add recordmcount files to force full build Steven Rostedt
2011-05-17 13:36 ` Michal Marek
2011-05-17 13:47 ` Steven Rostedt
2011-05-17 14:20 ` Steven Rostedt
2011-05-17 14:21 ` Steven Rostedt
2011-05-17 14:42 ` Michal Marek
2011-05-19 17:31 ` [tip:perf/core] " tip-bot for Michal Marek
2011-06-16 14:03 ` tip-bot for Michal Marek
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=20110517021027.390391519@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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).