linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Alan Mikhak <alanmikhak@gmail.com>
Cc: Yordan Karadzhov <ykaradzhov@vmware.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 11:53:44 -0400	[thread overview]
Message-ID: <20190612115344.3359003c@gandalf.local.home> (raw)
In-Reply-To: <CAOY98Nfv24YknzV36PZFnVLsPK6UcCxZiKfTJ-mv4dUsDUzaMA@mail.gmail.com>

On Wed, 12 Jun 2019 08:31:30 -0700
Alan Mikhak <alanmikhak@gmail.com> wrote:

> Hi Steve and Yordan,
> 
> FYI, I ran the kernel get_maintainers.pl script when preparing this
> patch but the script didn't suggest linux-trace-devel@vger.kernel.org
> or either of you as maintainers.

Hi Alan,

Heh, that script is made to work with the Linux kernel. I never thought
about trying it against the trace-cmd.git repo. I may be able to make
that work, it shouldn't be too hard. I just need to create a
MAINTAINERS file.

I do have both: trace-cmd.org and kernelshark.org, that should show how
to submit patches.

Thanks!

-- Steve

  reply	other threads:[~2019-06-12 15:53 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 [this message]
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

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=20190612115344.3359003c@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).