From: Christian Borntraeger <borntraeger@de.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org, torvalds@linux-foundation.org,
paulmck@linux.vnet.ibm.com, linux-s390@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [PATCH 1/2] s390/ebdic: disable gcov on ebcdic.o
Date: Wed, 25 Mar 2015 14:15:35 +0100 [thread overview]
Message-ID: <1427289336-22883-2-git-send-email-borntraeger@de.ibm.com> (raw)
In-Reply-To: <1427289336-22883-1-git-send-email-borntraeger@de.ibm.com>
ebcdic.o is also used for the compressed kernel image. The decompressor
has no gcov support, so better do not add any gcov related functions.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
arch/s390/kernel/Makefile | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/s390/kernel/Makefile b/arch/s390/kernel/Makefile
index 31fab26..89352da 100644
--- a/arch/s390/kernel/Makefile
+++ b/arch/s390/kernel/Makefile
@@ -8,6 +8,10 @@ CFLAGS_REMOVE_early.o = $(CC_FLAGS_FTRACE)
CFLAGS_REMOVE_ftrace.o = $(CC_FLAGS_FTRACE)
endif
+# ebcdic.o is also used in arch/s390/boot/compressed/ with does not
+# have gcov support
+GCOV_PROFILE_ebcdic.o = n
+
#
# Passing null pointers is ok for smp code, since we access the lowcore here.
#
--
2.1.4
next prev parent reply other threads:[~2015-03-25 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 13:15 [PATCH/RFC 0/2] followup change for READ_ONCE/WRITE_ONCE Christian Borntraeger
2015-03-25 13:15 ` Christian Borntraeger
2015-03-25 13:15 ` Christian Borntraeger [this message]
2015-03-25 13:15 ` [PATCH 2/2] compiler.h: Fix word size check for READ/WRITE_ONCE Christian Borntraeger
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=1427289336-22883-2-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).