From: Trilok Soni <quic_tsoni@quicinc.com>
To: Gokul krishna Krishnakumar <quic_gokukris@quicinc.com>,
<linux-remoteproc@vger.kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
<linux-kernel@vger.kernel.org>,
"Satya Durga Srinivasu Prabhala" <quic_satyap@quicinc.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Elliot Berman <quic_eberman@quicinc.com>,
"Guru Das Srinagesh" <quic_gurus@quicinc.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Melody Olvera <quic_molvera@quicinc.com>
Subject: Re: [PATCH v4 0/2] Patches for introducing traces in remoteproc.
Date: Wed, 31 May 2023 14:36:15 -0700 [thread overview]
Message-ID: <f69b6e5c-e6d6-b575-9e9c-6516a3dfe5e8@quicinc.com> (raw)
In-Reply-To: <63da3282-6a94-3807-b23f-73c4c6111936@quicinc.com>
On 5/31/2023 2:35 PM, Trilok Soni wrote:
> On 5/31/2023 2:28 PM, Gokul krishna Krishnakumar wrote:
>> V4: Add config symbol REMOTEPROC_TRACEPOINTS to enable traces
>> Rename rproc_qcom.h to remoteproc_tracepoints.h
>> Rename qcom_tracepoints.c to remoteproc_tracepoints.c
>> Switch to EXPORT_SYMBOL_GPL
>
>
> Any reasons you have not sent these patches to mailing list?
I don't see linux-arm-msm mailing list. Are you CCing all the required
lists and maintainers?
---Trilok Soni
next prev parent reply other threads:[~2023-05-31 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1685486994.git.quic_gokukris@quicinc.com>
2023-05-31 21:35 ` Trilok Soni
2023-05-31 21:36 ` Trilok Soni [this message]
2023-05-31 21:49 ` Gokul Krishna Krishnakumar
2023-05-31 21:50 ` Trilok Soni
[not found] ` <5c1744bc362fbc80615349f12c18c8ab5c4f0a6e.1685486994.git.quic_gokukris@quicinc.com>
2023-05-31 21:51 ` [PATCH v4 1/2] remoteproc: Introduce traces for remoteproc events Trilok Soni
2023-06-01 0:55 ` Gokul Krishna Krishnakumar
[not found] ` <bd949ac8225abb842630bd7f4a2d45334c58f17f.1685486994.git.quic_gokukris@quicinc.com>
2023-06-01 14:18 ` [PATCH v4 2/2] remoteproc: qcom: Add remoteproc tracing kernel test robot
2023-06-01 14:18 ` kernel test robot
2023-06-07 15:35 ` Mathieu Poirier
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=f69b6e5c-e6d6-b575-9e9c-6516a3dfe5e8@quicinc.com \
--to=quic_tsoni@quicinc.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_eberman@quicinc.com \
--cc=quic_gokukris@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=quic_molvera@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_sibis@quicinc.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
all inboxes | Powered by JetHome®