From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Yang Bai <hamo.by@gmail.com>, Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH] scripts: Have make TAGS not include structure members
Date: Tue, 19 Nov 2013 15:59:07 -0800 [thread overview]
Message-ID: <20131119155907.11fbdecea0aa40764a3d927a@linux-foundation.org> (raw)
In-Reply-To: <CAMuHMdXSBSOkfd2MGbn=rpXQRZYw5TKLsR=3SoeSyrcD2CzunA@mail.gmail.com>
On Sun, 17 Nov 2013 10:14:46 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Fri, Nov 15, 2013 at 3:36 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > It is really annoying when I use emacs TAGS to search for something
> > like "dev_name" and have to go through 12 iterations before I find the
> > function "dev_name". I really do not care about structures that include
> > "dev_name" as one of its fields, and I'm sure pretty much all other
> > developers do not care either.
>
> While I'm also annoyed by this (although with vim/tags), I regularly do search
> for struct members, so losing this ability would hurt, too.
metoo.
> Is there a solution, without throwing out the baby with the bath water?
Remove the tags for those struct members whose name duplicates some
other symbol?
next prev parent reply other threads:[~2013-11-19 23:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 14:36 Steven Rostedt
2013-11-16 1:02 ` Stephen Boyd
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 [this message]
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=20131119155907.11fbdecea0aa40764a3d927a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=geert@linux-m68k.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 \
--cc=sboyd@codeaurora.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
all inboxes | Powered by JetHome®