From: Amerigo Wang <amwang@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
akpm@linux-foundation.org, linux-kbuild@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>, Amerigo Wang <amwang@redhat.com>
Subject: [Patch 2/5] Makefile: clean .gcov files
Date: Thu, 3 Sep 2009 21:25:43 -0400 [thread overview]
Message-ID: <20090904012811.3749.77259.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20090904012755.3749.69645.sendpatchset@localhost.localdomain>
Clean *.gcov files when "make clean".
Signed-off-by: WANG Cong <amwang@redhat.com>
---
Index: linux-2.6/Makefile
===================================================================
--- linux-2.6.orig/Makefile
+++ linux-2.6/Makefile
@@ -1218,7 +1218,8 @@ clean: archclean $(clean-dirs)
-o -name '.*.d' -o -name '.*.tmp' -o -name '*.mod.c' \
-o -name '*.symtypes' -o -name 'modules.order' \
-o -name 'Module.markers' -o -name '.tmp_*.o.*' \
- -o -name '*.gcno' \) -type f -print | xargs rm -f
+ -o -name '*.gcno' -o -name '*.gcov' \) \
+ -type f -print | xargs rm -f
# mrproper - Delete all generated files, including .config
#
next prev parent reply other threads:[~2009-09-04 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 1:25 [RFC Patch 0/5] gcov: integrate gcov into kbuild Amerigo Wang
2009-09-04 1:25 ` [Patch 1/5] gitignore: add .gcov files Amerigo Wang
2009-09-04 1:25 ` Amerigo Wang [this message]
2009-09-04 1:25 ` [Patch 3/5] doc: move the scripts in gcov.txt to tools/gcov/ Amerigo Wang
2009-09-04 1:25 ` [Patch 4/5] scripts: add gen_gcov.sh Amerigo Wang
2009-09-04 1:26 ` [Patch 5/5] Makefile: implement "make foo.c.gcov" Amerigo Wang
2009-09-07 8:24 ` [RFC Patch 0/5] gcov: integrate gcov into kbuild Peter Oberparleiter
2009-09-07 9:58 ` Amerigo Wang
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=20090904012811.3749.77259.sendpatchset@localhost.localdomain \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oberpar@linux.vnet.ibm.com \
--cc=sam@ravnborg.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.