Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754732Ab3JXJmk (ORCPT ); Thu, 24 Oct 2013 05:42:40 -0400 Received: from mail-ve0-f178.google.com ([209.85.128.178]:63419 "EHLO mail-ve0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754389Ab3JXJmi (ORCPT ); Thu, 24 Oct 2013 05:42:38 -0400 MIME-Version: 1.0 In-Reply-To: <1382604360.5283.9.camel@pippen.local.home> References: <20131024075813.GA26929@gmail.com> <1382604360.5283.9.camel@pippen.local.home> Date: Thu, 24 Oct 2013 10:42:37 +0100 X-Google-Sender-Auth: tsTLUb2liHaXJQHltsMKxO-r3EY Message-ID: Subject: Re: ktap inclusion in drivers/staging/? From: Linus Torvalds To: Steven Rostedt Cc: Ingo Molnar , Greg Kroah-Hartman , jovi.zhangwei@huawei.com, =?UTF-8?B?RnLDqWTDqXJpYyBXZWlzYmVja2Vy?= , Peter Zijlstra , Arnaldo Carvalho de Melo , Thomas Gleixner , Andrew Morton , Linux Kernel Mailing List , Tom Zanussi , Namhyung Kim , David Ahern , Jiri Olsa Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1000 Lines: 23 On Thu, Oct 24, 2013 at 9:46 AM, Steven Rostedt wrote: > > But I agree, this should not be just dumped into the staging tree until > the patches themselves have been posted and reviewed. Btw, it's not just the commit history. The actual file layout is terminally horrible too. The actual LWN article made it look like ktap was just a user-space tool, and I was thinking that it was like tools/pert/, just in staging. But looking at the tree, it looks like parts of it is a kernel module, and parts of it is the user space thing, and it's totally impossible to see which is which, it's just all mixed up in the same directory structure. Maybe I misunderstood, but that was my reaction from a very quick look. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/