[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140805152540.GC19379@twins.programming.kicks-ass.net>
Date: Tue, 5 Aug 2014 17:25:40 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Shuah Khan <shuahkhan@...il.com>
Cc: Maarten Lankhorst <maarten.lankhorst@...onical.com>,
Greg KH <gregkh@...uxfoundation.org>,
Waiman Long <Waiman.Long@...com>,
Ingo Molnar <mingo@...nel.org>, Rik van Riel <riel@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Scott J Norton <scott.norton@...com>,
Fengguang Wu <fengguang.wu@...el.com>
Subject: Re: [PATCH 2/2 v6] locking/selftest: Support queued rwlock
On Tue, Aug 05, 2014 at 09:05:53AM -0600, Shuah Khan wrote:
> Maybe if tools doesn't sounds right, we could move testing from under tools
> and have it be testing
No, tools/testing/ is all userspace stuff afaict.
> We have several selftests spread around in the kernel tree. It makes it easier
> to pull them under a single make target devtest. I sent in a patch add devtest
> target that runs tests that are under tools/testing/selftests a couple of
> weeks ago, hopefully it will be included in 3.17. I am working towards pulling
> more kernel selftests that exist under this devtest umbrella. That is
> the motivation
A link to the patch might've been useful.. but no that's pointless,
there is no userspace component to locking-selftest, so your build/run
target is bloody pointless.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists