From: Steven Rostedt <rostedt@goodmis.org>
To: Felipe Balbi <felipe.balbi@linux.intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Linux USB <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Chunyan Zhang <zhang.chunyan@linaro.org>
Subject: Re: [PATCH] usb: gadget: functions: add ftrace export over USB
Date: Fri, 22 Mar 2019 08:22:52 -0400 [thread overview]
Message-ID: <20190322082252.2d239fbc@gandalf.local.home> (raw)
In-Reply-To: <87va0bdt7g.fsf@linux.intel.com>
On Fri, 22 Mar 2019 13:49:55 +0200
Felipe Balbi <felipe.balbi@linux.intel.com> wrote:
> > Can you post the latest to the list one more time. At least to make
> > sure you got the naming correct ;-)
> >
> > Not FTrace or f_trace.
>
> The reason for the name was discussed already. See [1] and [2]
>
> [1] https://marc.info/?i=878tl1qmrj.fsf@linux.intel.com
> [2] https://marc.info/?i=20170609110717.3304f6b9@gandalf.local.home
Ah, I forgot (was two years ago) But not doing FTrace still stands!
-- Steve
next prev parent reply other threads:[~2019-03-22 12:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 6:13 [PATCH] usb: gadget: functions: add ftrace export over USB Felipe Balbi
2017-06-09 10:28 ` Felipe Balbi
2017-06-09 11:15 ` Felipe Balbi
2017-07-14 5:52 ` Pratyush Anand
2017-07-14 6:53 ` Felipe Balbi
2017-07-14 21:44 ` Steven Rostedt
2017-06-09 14:02 ` Steven Rostedt
2017-06-09 14:05 ` Felipe Balbi
2017-06-09 15:07 ` Steven Rostedt
2017-06-10 3:38 ` kbuild test robot
2017-06-12 10:39 ` Felipe Balbi
2017-06-10 4:02 ` kbuild test robot
2017-07-13 11:40 ` Felipe Balbi
2017-07-14 5:31 ` Pratyush Anand
2017-07-14 6:56 ` Felipe Balbi
2019-03-21 9:38 ` Felipe Balbi
2019-03-21 16:37 ` Steven Rostedt
2019-03-22 11:49 ` Felipe Balbi
2019-03-22 12:22 ` Steven Rostedt [this message]
2019-03-22 12:27 ` Felipe Balbi
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=20190322082252.2d239fbc@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=zhang.chunyan@linaro.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.