From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] devtools: return error on failure
Date: Fri, 28 Jun 2019 20:40:02 +0100 [thread overview]
Message-ID: <20190628194001.GC366@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20190628092747.2c77eed1@hermes.lan>
On Fri, Jun 28, 2019 at 09:27:47AM -0700, Stephen Hemminger wrote:
> On Tue, 25 Jun 2019 18:01:06 +0100
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> > Currently script is always returning success, returning failure on error
> > helps on using script on automation tools.
> >
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Looks good, but maybe this script is getting complex enough that
> it should be python?
>
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
+1
next prev parent reply other threads:[~2019-06-28 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 17:01 Ferruh Yigit
2019-06-28 16:27 ` Stephen Hemminger
2019-06-28 19:40 ` Bruce Richardson [this message]
2020-07-30 22:56 ` 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=20190628194001.GC366@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).