From: Steven Rostedt <rostedt@goodmis.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Krishna Chaitanya Chundru <quic_krichai@quicinc.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, quic_vbadigan@quicinc.com,
quic_ramkri@quicinc.com, quic_nitegupt@quicinc.com,
quic_skananth@quicinc.com, quic_parass@quicinc.com
Subject: Re: [PATCH v11] bus: mhi: host: Add tracing support
Date: Mon, 12 Feb 2024 13:08:48 -0500 [thread overview]
Message-ID: <20240212130848.7415b87f@gandalf.local.home> (raw)
In-Reply-To: <20240206093110.GC8333@thinkpad>
On Tue, 6 Feb 2024 15:01:10 +0530
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> wrote:
> > Bot will check sparse warnings/errors mostly. But these checkpatch issues can be
> > fixed easily. If you don't do it now, then someone will send a patch for it
> > later.
> >
>
> Hmm, seems like we should ignore these checkpatch issues due to the way the
> macros are used by trace headers. Ignore my above comment, patch looks fine.
Yes please ignore checkpatch on any TRACE_EVENT() and related macros. It
doesn't understand them, and reports errors and asks for fixes that break
the default way of using TRACE_EVENT().
Someday I hope someone teaches checkpatch to know the TRACE_EVENT() default
format which is:
TRACE_EVENT(event,
TP_PROTO(<proto>),
TP_ARGS(<args>),
TP_STRUCT__entry(
__field( <type>, <field> )
__array( <type>, <field>, <len> )
),
TP_fast_assign(
<code-block>
),
TP_printk("format", <print-args>)
);
But checkpatch will error all over the above. :-(
-- Steve
next prev parent reply other threads:[~2024-02-12 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 4:32 [PATCH v11] bus: mhi: host: Add tracing support Krishna chaitanya chundru
2024-02-06 6:26 ` Manivannan Sadhasivam
2024-02-06 6:55 ` Krishna Chaitanya Chundru
2024-02-06 9:03 ` Manivannan Sadhasivam
2024-02-06 9:31 ` Manivannan Sadhasivam
2024-02-12 18:08 ` Steven Rostedt [this message]
2024-02-06 9:34 ` Manivannan Sadhasivam
2024-02-06 12:45 ` Naman Jain
2024-02-12 18:26 ` 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=20240212130848.7415b87f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=mhiramat@kernel.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_nitegupt@quicinc.com \
--cc=quic_parass@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_skananth@quicinc.com \
--cc=quic_vbadigan@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