From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>, <thomas.monjalon@6wind.com>
Subject: Re: [PATCH] tools: add tags and cscope index file generation support
Date: Fri, 13 Jan 2017 08:20:06 +0530 [thread overview]
Message-ID: <20170113025005.GA2951@localhost.localdomain> (raw)
In-Reply-To: <204efa1f-0631-ed9c-3d68-8c573edfbb76@intel.com>
On Thu, Jan 12, 2017 at 02:19:44PM +0000, Ferruh Yigit wrote:
> On 11/27/2016 12:12 AM, Jerin Jacob wrote:
> > This script generates cscope, gtags, and tags
> > index files based on EAL environment.
> > (architecture and OS(linux/bsd))
> >
> > Selection of the architecture and OS environment
> > is based on dpdk configuration target(T=)
> >
> > example usage:
> > make tags T=x86_64-native-linuxapp-gcc
> > make cscope T=x86_64-native-linuxapp-gcc
> > make gtags T=x86_64-native-linuxapp-gcc
> >
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>
> <...>
>
> > +
> > +if [ -n "$T" ]; then
> <...>
> > + usage $1
> > + exit
>
> I would prefer fallback to RTE_TARGET parsing, or processing all files (
> cscope -Rqn ), instead of exiting here, but that is your call.
I would prefer avoid any fallback(sometimes RTE_TARGET can be "build" also) and
print the usage and exit error if the requirements are not meet.
>
>
> Also "tags.sh" needs to be moved into "devtools" after latest updates.
Sure. I will send v2 to address this.
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Thanks for the review.
next prev parent reply other threads:[~2017-01-13 2:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 0:12 [PATCH] tools: add tags and cscope index file generation support Jerin Jacob
2016-11-28 5:50 ` Yuanhan Liu
2017-01-12 14:19 ` Ferruh Yigit
2017-01-13 2:50 ` Jerin Jacob [this message]
2017-01-13 12:23 ` Mcnamara, John
2017-01-17 8:41 ` [PATCH v2] " Jerin Jacob
2017-02-27 14:18 ` Thomas Monjalon
2017-02-28 14:12 ` Jerin Jacob
2017-03-01 10:51 ` Thomas Monjalon
2017-03-13 14:18 ` [PATCH v3] devtools: " Jerin Jacob
2017-03-19 10:52 ` [PATCH v4] " Jerin Jacob
2017-03-20 10:15 ` Dumitrescu, Cristian
2017-03-21 4:05 ` Jerin Jacob
2017-03-22 8:30 ` [PATCH v5] " Jerin Jacob
2017-04-14 12:44 ` Jerin Jacob
2017-04-28 8:50 ` Thomas Monjalon
2017-04-29 10:51 ` [PATCH v6] " Jerin Jacob
2017-04-30 10:45 ` Thomas Monjalon
2017-04-30 11:00 ` Thomas Monjalon
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=20170113025005.GA2951@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas.monjalon@6wind.com \
/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.