From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Stephen Boyd <stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] Makefile: Add tags rule
Date: Mon, 30 Jan 2017 12:17:10 +1100 [thread overview]
Message-ID: <20170130011710.GC14757@umbus> (raw)
In-Reply-To: <20170126184814.5325-1-stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
On Thu, Jan 26, 2017 at 10:48:14AM -0800, Stephen Boyd wrote:
> It's useful to have some tags to jump around sources. We don't
> include test sources in the toplevel Makefile because they
> probably aren't useful to main program development.
>
> Signed-off-by: Stephen Boyd <stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Applied, thanks.
> ---
>
> I noticed my previous patch wasn't pruning the *.tab.[ch] and *.lex.c
> files. This version corrects the find command so those aren't included.
>
> Makefile | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index 32dcfcf8e203..ce05eba6590b 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -218,6 +218,12 @@ kup: dist
> $(KUPDIR)/dtc-$(dtc_version).tar.gz
> endif
>
> +tags: FORCE
> + rm -f tags
> + find . \( -name tests -type d -prune \) -o \
> + \( ! -name '*.tab.[ch]' ! -name '*.lex.c' \
> + -name '*.[chly]' -type f -print \) | xargs ctags -a
> +
> #
> # Testsuite rules
> #
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-01-30 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 18:48 [PATCH v2] Makefile: Add tags rule Stephen Boyd
[not found] ` <20170126184814.5325-1-stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-01-30 1:17 ` David Gibson [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=20170130011710.GC14757@umbus \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).