Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sat, 24 Feb 2018 09:39:14 +0100
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
Message-ID: <20180224083914.x6qygtno7ms2dyzy@gmail.com>
References: <cover.1519423340.git.shuahkh@osg.samsung.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cover.1519423340.git.shuahkh@osg.samsung.com>
User-Agent: NeoMutt/20170609 (1.8.3)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


* 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