From: Brenda Butler <bjb@mojatatu.com>
To: David Miller <davem@davemloft.net>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Chris Mi <chrism@mellanox.com>,
Lucas Bates <lucasb@mojatatu.com>,
Alexander Aring <aring@mojatatu.com>,
Roman Mashak <mrv@mojatatu.com>,
BTaskaya <batuhanosmantaskaya@gmail.com>,
dcaratti@redhat.com, netdev@vger.kernel.org, kernel@mojatatu.com
Subject: Re: [PATCH net-next 1/1] tools: tc-testing: Can refer to $TESTID in test spec
Date: Thu, 8 Mar 2018 12:59:37 -0500 [thread overview]
Message-ID: <CAEj_wPRexvhdp2HdapcbWVU1RFok8eBDaB-wrAnLDPV7e-wXDw@mail.gmail.com> (raw)
In-Reply-To: <20180308.124556.676950922810984655.davem@davemloft.net>
The patches are independent and can be applied in any order.
I will change my process, to use send-email in separate invocations
for unrelated patches, so the patches are more obviously independent.
Sorry for the misleading submission.
Thanks for feedback. I will resubmit the patches.
bjb
On Thu, Mar 8, 2018 at 12:45 PM, David Miller <davem@davemloft.net> wrote:
> From: "Brenda J. Butler" <bjb@mojatatu.com>
> Date: Wed, 7 Mar 2018 09:27:15 -0500
>
>> At debug level 5 or above, the test script will pause just before
>> the post_suite functions are called. This allows the tester to
>> inspect the system before it is torn down.
>
> I've asked for changes in that patch, which means this needs updating
> too.
next prev parent reply other threads:[~2018-03-08 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 14:27 [PATCH net-next 1/1] tools: tc-testing: Can pause just before post-suite Brenda J. Butler
2018-03-07 14:27 ` [PATCH net-next 1/1] tools: tc-testing: Can refer to $TESTID in test spec Brenda J. Butler
2018-03-08 17:45 ` David Miller
2018-03-08 17:59 ` Brenda Butler [this message]
2018-03-08 17:45 ` [PATCH net-next 1/1] tools: tc-testing: Can pause just before post-suite David Miller
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=CAEj_wPRexvhdp2HdapcbWVU1RFok8eBDaB-wrAnLDPV7e-wXDw@mail.gmail.com \
--to=bjb@mojatatu.com \
--cc=aring@mojatatu.com \
--cc=batuhanosmantaskaya@gmail.com \
--cc=chrism@mellanox.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=lucasb@mojatatu.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 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).