From: Steven Rostedt <rostedt@goodmis.org>
To: Lina Iyer <ilina@codeaurora.org>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, andy.gross@linaro.org, david.brown@linaro.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
rnayak@codeaurora.org, bjorn.andersson@linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 03/10] drivers: qcom: rpmh-rsc: log RPMH requests in FTRACE
Date: Tue, 6 Mar 2018 17:34:32 -0500 [thread overview]
Message-ID: <20180306173432.2c43840f@vmware.local.home> (raw)
In-Reply-To: <20180306220542.GF4930@codeaurora.org>
On Tue, 6 Mar 2018 15:05:42 -0700
Lina Iyer <ilina@codeaurora.org> wrote:
> Duh. FTRACE seems to have been disabled. Will fix and update.
Don't feel bad. You're not alone, I've done that too ;-)
-- Steve
next prev parent reply other threads:[~2018-03-06 22:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 16:43 [PATCH v3 00/10] drivers/qcom: add RPMH communication support Lina Iyer
2018-03-02 16:43 ` [PATCH v3 01/10] drivers: qcom: rpmh-rsc: add RPMH controller for QCOM SoCs Lina Iyer
2018-03-06 19:45 ` Stephen Boyd
2018-03-06 19:45 ` Stephen Boyd
2018-03-09 21:33 ` Lina Iyer
2018-03-09 21:37 ` Stephen Boyd
2018-03-02 16:43 ` [PATCH v3 02/10] dt-bindings: introduce RPMH RSC bindings for Qualcomm SoCs Lina Iyer
2018-03-06 22:30 ` Stephen Boyd
2018-03-06 22:30 ` Stephen Boyd
2018-03-07 20:54 ` Lina Iyer
2018-03-02 16:43 ` [PATCH v3 03/10] drivers: qcom: rpmh-rsc: log RPMH requests in FTRACE Lina Iyer
2018-03-06 5:38 ` kbuild test robot
2018-03-06 5:38 ` kbuild test robot
2018-03-06 21:47 ` Steven Rostedt
2018-03-06 21:56 ` Lina Iyer
2018-03-06 22:05 ` Lina Iyer
2018-03-06 22:34 ` Steven Rostedt [this message]
2018-03-02 16:43 ` [PATCH v3 04/10] drivers: qcom: rpmh: add RPMH helper functions Lina Iyer
2018-03-08 18:57 ` Stephen Boyd
2018-03-08 18:57 ` Stephen Boyd
2018-03-08 21:37 ` Lina Iyer
2018-03-02 16:43 ` [PATCH v3 05/10] drivers: qcom: rpmh-rsc: write sleep/wake requests to TCS Lina Iyer
2018-03-08 19:41 ` Stephen Boyd
2018-03-08 19:41 ` Stephen Boyd
2018-03-08 23:58 ` Lina Iyer
2018-03-09 15:45 ` Lina Iyer
2018-03-02 16:43 ` [PATCH v3 06/10] drivers: qcom: rpmh-rsc: allow invalidation of sleep/wake TCS Lina Iyer
2018-03-08 20:40 ` Stephen Boyd
2018-03-08 20:40 ` Stephen Boyd
2018-03-09 16:41 ` Lina Iyer
2018-03-02 16:43 ` [PATCH v3 07/10] drivers: qcom: rpmh: cache sleep/wake state requests Lina Iyer
2018-03-05 20:44 ` Evan Green
2018-03-06 22:12 ` Lina Iyer
2018-03-02 16:43 ` [PATCH v3 08/10] drivers: qcom: rpmh: allow requests to be sent asynchronously Lina Iyer
2018-03-08 21:06 ` Stephen Boyd
2018-03-08 21:06 ` Stephen Boyd
2018-03-02 16:43 ` [PATCH v3 09/10] drivers: qcom: rpmh: add support for batch RPMH request Lina Iyer
2018-03-08 21:59 ` Stephen Boyd
2018-03-08 21:59 ` Stephen Boyd
2018-03-08 22:55 ` Lina Iyer
2018-03-16 17:00 ` Stephen Boyd
2018-03-26 15:30 ` Lina Iyer
2018-03-02 16:43 ` [PATCH v3 10/10] drivers: qcom: rpmh-rsc: allow active requests from wake TCS Lina Iyer
2018-03-08 20:47 ` Stephen Boyd
2018-03-08 20:47 ` Stephen Boyd
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=20180306173432.2c43840f@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=ilina@codeaurora.org \
--cc=kbuild-all@01.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rnayak@codeaurora.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.