mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
	"Ingo Molnar" <mingo@kernel.org>,
	jovi.zhangwei@huawei.com,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Arnaldo Carvalho de Melo" <acme@infradead.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Tom Zanussi" <tom.zanussi@linux.intel.com>,
	"Namhyung Kim" <namhyung@kernel.org>,
	"David Ahern" <dsahern@gmail.com>, "Jiri Olsa" <jolsa@redhat.com>
Subject: Re: ktap inclusion in drivers/staging/?
Date: Thu, 24 Oct 2013 11:04:15 +0100	[thread overview]
Message-ID: <20131024100415.GB13223@kroah.com> (raw)
In-Reply-To: <CA+55aFxiNnpWSrA7GVHjsDsd6+a3XScDUAhpL7XPQ7F6g1-iJA@mail.gmail.com>

On Thu, Oct 24, 2013 at 10:42:37AM +0100, Linus Torvalds wrote:
> On Thu, Oct 24, 2013 at 9:46 AM, Steven Rostedt <rostedt@goodmis.org> 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.

No, you are correct, it is a mix and mess, and will be fixed up.

greg k-h

  reply	other threads:[~2013-10-24 10:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  7:58 Ingo Molnar
2013-10-24  8:46 ` Steven Rostedt
2013-10-24  9:42   ` Linus Torvalds
2013-10-24 10:04     ` Greg Kroah-Hartman [this message]
2013-10-25 10:10     ` Ingo Molnar
2013-10-24  9:49   ` Greg Kroah-Hartman
2013-10-24 12:44     ` Jovi Zhangwei
2013-10-24 12:11   ` Jovi Zhangwei
2013-10-24 12:25     ` Steven Rostedt
2013-10-24 19:46     ` Arnaldo Carvalho de Melo
2013-10-25  3:00       ` Jovi Zhangwei
2013-10-24 12:32 ` Jovi Zhangwei
2013-10-25 10:15   ` Ingo Molnar
2013-10-26  5:02     ` Jovi Zhangwei
2013-10-26  8:59       ` Ingo Molnar
2013-10-28 12:12         ` Masami Hiramatsu
2013-10-28 12:19           ` Ingo Molnar
2013-10-28 12:16         ` Masami Hiramatsu
2013-10-28 13:19           ` Jovi Zhangwei
2013-10-28  5:48     ` Masami Hiramatsu
2013-10-25 11:25 ` Pekka Enberg
2013-10-25 11:34   ` Ingo Molnar

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=20131024100415.GB13223@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=jovi.zhangwei@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tom.zanussi@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    /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

Powered by JetHome