From: Bart Van Assche <bvanassche@acm.org>
To: Ziqi Chen <quic_ziqichen@quicinc.com>,
quic_asutoshd@quicinc.com, quic_cang@quicinc.com,
quic_nguyenb@quicinc.com, mani@kernel.org,
stanley.chu@mediatek.com, adrian.hunter@intel.com,
beanhuo@micron.com, avri.altman@wdc.com,
junwoo80.lee@samsung.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, Alim Akhtar <alim.akhtar@samsung.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:TRACING" <linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH v6] scsi: ufs: core: Add trace event for MCQ
Date: Tue, 14 Mar 2023 11:13:33 -0700 [thread overview]
Message-ID: <70bf37fb-bc66-d341-7c2d-bf1785ba464f@acm.org> (raw)
In-Reply-To: <1678792580-3178-1-git-send-email-quic_ziqichen@quicinc.com>
On 3/14/23 04:15, Ziqi Chen wrote:
> TP_printk(
> - "%s: %s: tag: %u, DB: 0x%x, size: %d, IS: %u, LBA: %llu, opcode: 0x%x (%s), group_id: 0x%x",
> - show_ufs_cmd_trace_str(__entry->str_t), __get_str(dev_name),
> - __entry->tag, __entry->doorbell, __entry->transfer_len,
> - __entry->intr, __entry->lba, (u32)__entry->opcode,
> - str_opcode(__entry->opcode), (u32)__entry->group_id
> + "%s: %s: tag: %u, DB: 0x%x, size: %d, IS: %u, LBA: %llu, opcode: 0x%x (%s), group_id: 0x%x, hwq_id: %d",
> + show_ufs_cmd_trace_str(__entry->str_t), __get_str(dev_name),
> + __entry->tag, __entry->doorbell, __entry->transfer_len, __entry->intr,
> + __entry->lba, (u32)__entry->opcode, str_opcode(__entry->opcode),
> + (u32)__entry->group_id, __entry->hwq_id
The alignment of the TP_printk() arguments looks odd. Please make sure
that arguments 2 and later start in the same column as the opening
double quote (") instead of one column to the right of that double quote.
Thanks,
Bart.
next prev parent reply other threads:[~2023-03-14 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 11:15 Ziqi Chen
2023-03-14 18:13 ` Bart Van Assche [this message]
2023-03-15 7:43 ` Ziqi Chen
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=70bf37fb-bc66-d341-7c2d-bf1785ba464f@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=jejb@linux.ibm.com \
--cc=junwoo80.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mhiramat@kernel.org \
--cc=quic_asutoshd@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_ziqichen@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=stanley.chu@mediatek.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®