From: Stephen Boyd <sboyd@codeaurora.org>
To: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, Yang Bai <hamo.by@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] scripts: Have make TAGS not include structure members
Date: Fri, 15 Nov 2013 17:02:36 -0800 [thread overview]
Message-ID: <5286C42C.4050800@codeaurora.org> (raw)
In-Reply-To: <20131115093645.6dc03918@gandalf.local.home>
On 11/15/13 06:36, Steven Rostedt wrote:
> diff --git a/scripts/tags.sh b/scripts/tags.sh
> index 74f02e4..b985371 100755
> --- a/scripts/tags.sh
> +++ b/scripts/tags.sh
> @@ -218,7 +218,7 @@ exuberant()
>
> emacs()
> {
> - all_target_sources | xargs $1 -a \
> + all_target_sources | xargs $1 -a --no-members \
> --regex='/^\(ENTRY\|_GLOBAL\)(\([^)]*\)).*/\2/' \
> --regex='/^SYSCALL_DEFINE[0-9]?(\([^,)]*\).*/sys_\1/' \
> --regex='/^TRACE_EVENT(\([^,)]*\).*/trace_\1/' \
> @@ -248,13 +248,13 @@ emacs()
> --regex='/PCI_OP_READ(\([a-z]*[a-z]\).*[1-4])/pci_bus_read_config_\1/' \
> --regex='/PCI_OP_WRITE(\([a-z]*[a-z]\).*[1-4])/pci_bus_write_config_\1/'
>
> - all_kconfigs | xargs $1 -a \
> + all_kconfigs | xargs $1 -a --no-members \
> --regex='/^[ \t]*\(\(menu\)*config\)[ \t]+\([a-zA-Z0-9_]+\)/\3/'
>
> - all_kconfigs | xargs $1 -a \
> + all_kconfigs | xargs $1 -a --no-members \
> --regex='/^[ \t]*\(\(menu\)*config\)[ \t]+\([a-zA-Z0-9_]+\)/CONFIG_\3/'
>
> - all_defconfigs | xargs -r $1 -a \
> + all_defconfigs | xargs -r $1 -a --no-members \
> --regex='/^#?[ \t]?\(CONFIG_[a-zA-Z0-9_]+\)/\1/'
> }
>
Does it actually matter for the kconfigs and defconfigs?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-11-16 1:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 14:36 [PATCH] scripts: Have make TAGS not include structure members Steven Rostedt
2013-11-16 1:02 ` Stephen Boyd [this message]
2013-11-16 1:20 ` Steven Rostedt
2013-11-17 9:14 ` Geert Uytterhoeven
2013-11-17 14:27 ` Steven Rostedt
2013-11-17 15:19 ` Geert Uytterhoeven
2013-11-17 17:08 ` Steven Rostedt
2013-11-20 8:29 ` Geert Uytterhoeven
2013-11-19 23:59 ` Andrew Morton
2013-11-20 0:04 ` Steven Rostedt
2013-11-20 0:08 ` Andrew Morton
2013-11-20 0:14 ` Steven Rostedt
2013-11-20 0:18 ` Stephen Boyd
2013-11-20 0:34 ` Steven Rostedt
2014-01-03 13:24 ` mmarek
2014-01-06 19:32 ` Steven Rostedt
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=5286C42C.4050800@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=hamo.by@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox