mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: shuah@kernel.org, dvhart@infradead.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 0/5] Handling for TAP header level
Date: Sat, 24 Feb 2018 09:39:14 +0100	[thread overview]
Message-ID: <20180224083914.x6qygtno7ms2dyzy@gmail.com> (raw)
In-Reply-To: <cover.1519423340.git.shuahkh@osg.samsung.com>


* Shuah Khan <shuahkh@osg.samsung.com> wrote:

> This patch series is a result discussion with Tim Bird about nested TAP header 
> handling. Based on the discussion, I am introducing a environment variable to 
> prevent nested TAP headers. These patches improve the run_tests output and the 
> output from the script generated by emit_tests.

Could you please provider a higher level description about what 'nested TAP header 
handling' is about and what it is good for?

Thanks,

	Ingo

      parent reply	other threads:[~2018-02-24  8:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23 22:11 Shuah Khan
2018-02-23 22:11 ` [PATCH 1/5] selftests: kselftest framework: add handling " Shuah Khan
2018-02-23 22:11 ` [PATCH 2/5] selftests: lib.mk set KSFT_TAP_LEVEL to prevent nested TAP headers Shuah Khan
2018-02-23 22:11 ` [PATCH 3/5] selftests: Makefile " Shuah Khan
2018-02-23 22:11 ` [PATCH 4/5] selftests: size call ksft_print_header() to print TAP header Shuah Khan
2018-02-23 22:11 ` [PATCH 5/5] selftests: futex Makefile add top level TAP header echo to RUN_TESTS Shuah Khan
2018-02-24 21:42   ` Darren Hart
2018-02-27 17:25     ` Shuah Khan
2018-03-06  0:17       ` Darren Hart
2018-02-24  8:39 ` Ingo Molnar [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=20180224083914.x6qygtno7ms2dyzy@gmail.com \
    --to=mingo@kernel.org \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=shuah@kernel.org \
    --cc=shuahkh@osg.samsung.com \
    --cc=tbird20d@gmail.com \
    --cc=tglx@linutronix.de \
    /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
all inboxes | Powered by JetHome®