From: Michal Marek <mmarek@suse.cz>
To: Prarit Bhargava <prarit@redhat.com>, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kirill Tkhai <tkhai@yandex.ru>,
Michael Opdenacker <michael.opdenacker@free-electrons.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Makefile, CONFIG_MODVERSIONS, export RCS_FIND_IGNORE and ignore *.mod.c files in tags creation
Date: Thu, 06 Feb 2014 16:57:10 +0100 [thread overview]
Message-ID: <52F3B0D6.6000308@suse.cz> (raw)
In-Reply-To: <1391691102-23721-1-git-send-email-prarit@redhat.com>
On 2014-02-06 13:51, Prarit Bhargava wrote:
> CONFIG_MODVERSIONS=y results in a .mod.c for every compiled file in the kernel.
> Issuing a 'make cscope' on a compiled kernel tree results in the cscope files
> containing *.mod.c files.
>
> [prarit@prarit linux]# make cscope
> [prarit@prarit linux]# cat cscope.files | grep mod.c | wc -l
> 4807
>
> These files are not useful for cscope and should be ignored. For example,
>
> # line filename / context / line
> 1 105 arch/x86/kvm/kvm-intel.mod.c <<GLOBAL>>
> { 0x618911fc, __VMLINUX_SYMBOL_STR(numa_node) },
> 2 508 drivers/block/mtip32xx/mtip32xx.h <<GLOBAL>>
> int numa_node;
> 3 55 drivers/block/mtip32xx/mtip32xx.mod.c <<GLOBAL>>
> { 0x618911fc, __VMLINUX_SYMBOL_STR(numa_node) },
> 4 37 drivers/cpufreq/acpi-cpufreq.mod.c <<GLOBAL>>
> { 0x618911fc, __VMLINUX_SYMBOL_STR(numa_node) },
> <snip>
>
> Add an export to RCS_FIND_IGNORE so it can be used in scripts/tags.sh and
> add explicitly ignore *.mod.c files.
Thanks, applied to kbuild.git#misc. But next time, please use a shorter
subject line. I changed it to "scripts/tags.sh: Ignore *.mod.c" so that
it does not take two lines everywhere.
Michal
prev parent reply other threads:[~2014-02-06 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 12:51 [PATCH] Makefile, CONFIG_MODVERSIONS, export RCS_FIND_IGNORE and ignore *.mod.c files in tags creation Prarit Bhargava
2014-02-06 15:57 ` Michal Marek [this message]
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=52F3B0D6.6000308@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=prarit@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tkhai@yandex.ru \
/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