From: Steven Rostedt <rostedt@goodmis.org>
To: Yordan Karadzhov <ykaradzhov@vmware.com>
Cc: Alan Mikhak <alanmikhak@gmail.com>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>,
Alan Mikhak <amikhak@wirelessfabric.com>
Subject: Re: [PATCH] Fix compiler error in KsSession.cpp on Raspberry Pi 3
Date: Wed, 12 Jun 2019 08:11:05 -0400 [thread overview]
Message-ID: <20190612081105.064b66b6@gandalf.local.home> (raw)
In-Reply-To: <876ffbbd-1574-3b06-c856-8b1930013bde@vmware.com>
On Wed, 12 Jun 2019 08:17:38 +0000
Yordan Karadzhov <ykaradzhov@vmware.com> wrote:
> Hi Alan,
>
> I just noticed that you created couple of issues in the issue tracker of
> the Steven's mirror repo on GitHub. Please note that the official
> repository of the project is here
> https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/
>
> and that the issue tracker that we use is here
>
> https://bugzilla.kernel.org/buglist.cgi?component=Trace-cmd%2FKernelshark&product=Tools&resolution=---
>
> Also I would like to ask you to copy the content of the trace data
> visualization issue in the official issue tracker, because I find your
> investigations interesting, and I think that this information can be
> useful for someone else having the same problem.
Thanks Yordan for pointing this out. I have disabled "Issues" from the
github repository.
-- Steve
prev parent reply other threads:[~2019-06-12 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 3:59 [PATCH] Fix compiler error in KsSession.cpp on Raspberry Pi 3 Alan Mikhak
2019-06-12 7:34 ` Yordan Karadzhov
2019-06-12 12:12 ` Steven Rostedt
2019-06-12 15:31 ` Alan Mikhak
2019-06-12 15:53 ` Steven Rostedt
2019-06-12 15:22 ` Alan Mikhak
2019-06-14 4:40 ` Alan Mikhak
2019-06-12 8:17 ` Yordan Karadzhov
2019-06-12 12:11 ` Steven Rostedt [this message]
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=20190612081105.064b66b6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alanmikhak@gmail.com \
--cc=amikhak@wirelessfabric.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=ykaradzhov@vmware.com \
/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;
as well as URLs for NNTP newsgroup(s).