All of lore.kernel.org
 help / color / mirror / Atom feed
From: dvhart at infradead.org (Darren Hart)
Subject: [PATCH v2] selftests: futex Makefile add top level TAP header echo to RUN_TESTS
Date: Mon, 5 Mar 2018 16:18:20 -0800	[thread overview]
Message-ID: <20180306001820.GF25693@fury> (raw)
In-Reply-To: <20180301201907.17573-1-shuahkh@osg.samsung.com>

On Thu, Mar 01, 2018 at 01:19:07PM -0700, Shuah Khan wrote:
> Add top level TAP header echo, testname and separator line to make
> the output consistent with the common run_tests target.
> 
> This change prevents nested TAP13 headers output from individual tests.
> Nested TAP13 headers could cause problems for some parsers.
> 
> Signed-off-by: Shuah Khan <shuahkh at osg.samsung.com>


Reviewed-by: Darren Hart (VMware) <dvhart at infradead.org>


-- 
Darren Hart
VMware Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: dvhart@infradead.org (Darren Hart)
Subject: [PATCH v2] selftests: futex Makefile add top level TAP header echo to RUN_TESTS
Date: Mon, 5 Mar 2018 16:18:20 -0800	[thread overview]
Message-ID: <20180306001820.GF25693@fury> (raw)
Message-ID: <20180306001820.jLPUT_HYwAiXFM4uy4UP9t13Z5PTY_ZdAzQ0iUz6Pd4@z> (raw)
In-Reply-To: <20180301201907.17573-1-shuahkh@osg.samsung.com>

On Thu, Mar 01, 2018@01:19:07PM -0700, Shuah Khan wrote:
> Add top level TAP header echo, testname and separator line to make
> the output consistent with the common run_tests target.
> 
> This change prevents nested TAP13 headers output from individual tests.
> Nested TAP13 headers could cause problems for some parsers.
> 
> Signed-off-by: Shuah Khan <shuahkh at osg.samsung.com>


Reviewed-by: Darren Hart (VMware) <dvhart at infradead.org>


-- 
Darren Hart
VMware Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@infradead.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: shuah@kernel.org, tbird20d@gmail.com, tglx@linutronix.de,
	mingo@redhat.com, peterz@infradead.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] selftests: futex Makefile add top level TAP header echo to RUN_TESTS
Date: Mon, 5 Mar 2018 16:18:20 -0800	[thread overview]
Message-ID: <20180306001820.GF25693@fury> (raw)
In-Reply-To: <20180301201907.17573-1-shuahkh@osg.samsung.com>

On Thu, Mar 01, 2018 at 01:19:07PM -0700, Shuah Khan wrote:
> Add top level TAP header echo, testname and separator line to make
> the output consistent with the common run_tests target.
> 
> This change prevents nested TAP13 headers output from individual tests.
> Nested TAP13 headers could cause problems for some parsers.
> 
> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>


Reviewed-by: Darren Hart (VMware) <dvhart@infradead.org>


-- 
Darren Hart
VMware Open Source Technology Center

  reply	other threads:[~2018-03-06  0:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 20:19 [PATCH v2] selftests: futex Makefile add top level TAP header echo to RUN_TESTS shuahkh
2018-03-01 20:19 ` Shuah Khan
2018-03-01 20:19 ` Shuah Khan
2018-03-06  0:18 ` dvhart [this message]
2018-03-06  0:18   ` Darren Hart
2018-03-06  0:18   ` Darren Hart
2018-03-07  2:37   ` shuahkh
2018-03-07  2:37     ` Shuah Khan
2018-03-07  2:37     ` Shuah Khan

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=20180306001820.GF25693@fury \
    --to=unknown@example.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.