From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "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>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
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 10:49:11 +0100 [thread overview]
Message-ID: <20131024094911.GA11921@kroah.com> (raw)
In-Reply-To: <1382604360.5283.9.camel@pippen.local.home>
On Thu, Oct 24, 2013 at 04:46:00AM -0400, Steven Rostedt wrote:
> On Thu, 2013-10-24 at 09:58 +0200, Ingo Molnar wrote:
> > Greg,
> >
> > I was surprised to see 'ktap' appear in the staging tree silently,
> > via these commits that are visible in today's staging-next:
> >
> > 2c856b9e3e06 staging: ktap: remove unused <asm/syscall.h> header file
> > 687b63a3bfd5 staging: ktap: update email name in MAINTAINERS
> > c63a164271f8 staging: ktap: add to the kernel tree
> >
> > ktap is pretty fresh instrumentation code, announced on lkml a
> > couple of months ago, and so far I haven't seen much technical
> > discussion of integrating ktap upstream, mostly I suspect because
> > not a _single_ patch was sent to linux-kernel for review. (!)
>
> I feel I'm partially to blame. Jovi has sent us several emails to look
> at his tree and I told him I would when I get time. What I should have
> done was told him to break up the changes and send them out as a patch
> series.
>
>
> >
> > An announcement of a Git tree was made (which Git tree is not very
> > structured), and some very minimal discussion ensued, but no actual
> > patches were sent with an intent to merge, no technical arguments
> > were made in favor of merging and nothing conclusive was achieved.
>
> Again, this may be partially our fault. We should have told Jovi to send
> out the patches and a pointer to a git tree is not acceptable. Then we
> could have had the necessary discussions required for this.
>
> But I agree, this should not be just dumped into the staging tree until
> the patches themselves have been posted and reviewed.
>
> I'll have to NAK it too.
Ok, I've just talked to Ingo in person about this, and I will revert the
ktap code, and work with Jovi to get this merged "properly" for 3.14 or
so. I do want to audit/change the user/kernel interface in ktap as I'm
not sold on the current one, so after I get that done, I'll work to get
a set of patches created to merge this to the "real" part of the kernel.
Jovi, sorry about this, but the good news is that everyone seems to
agree that this is the way to do this properly, so the end result will
be good for everyone involved. Again, great job with creating ktap, it
seems that it fills a real need that people are happy to see
implemented.
thanks,
greg k-h
next prev parent reply other threads:[~2013-10-24 9:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 7:58 ktap inclusion in drivers/staging/? Ingo Molnar
2013-10-24 8:46 ` Steven Rostedt
2013-10-24 9:42 ` Linus Torvalds
2013-10-24 10:04 ` Greg Kroah-Hartman
2013-10-25 10:10 ` Ingo Molnar
2013-10-24 9:49 ` Greg Kroah-Hartman [this message]
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=20131024094911.GA11921@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.