From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, Christoph Hellwig <hch@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Stanley Chu <stanley.chu@mediatek.com>,
Can Guo <quic_cang@quicinc.com>, Bean Huo <beanhuo@micron.com>,
Asutosh Das <quic_asutoshd@quicinc.com>,
"Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
Arthur Simchaev <Arthur.Simchaev@wdc.com>,
Ziqi Chen <quic_ziqichen@quicinc.com>,
Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: [PATCH v2] scsi: ufs: Include the SCSI ID in UFS command tracing output
Date: Wed, 13 Sep 2023 20:45:47 -0400 [thread overview]
Message-ID: <yq1v8cdfuq6.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230907183739.905938-1-bvanassche@acm.org> (Bart Van Assche's message of "Thu, 7 Sep 2023 11:37:16 -0700")
Bart,
> The logical unit information is missing from the UFS command tracing
> output. Although the device name is logged, e.g. 13200000.ufs, this
> name does not include logical unit information. Hence this patch that
> replaces the device name with the SCSI ID in the tracing output. An
> example of tracing output with this patch applied:
Applied to 6.7/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-09-14 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 18:37 [PATCH v2] scsi: ufs: Include the SCSI ID in UFS command tracing output Bart Van Assche
2023-09-08 0:25 ` Can Guo
2023-09-14 0:45 ` Martin K. Petersen [this message]
2023-09-22 1:05 ` Martin K. Petersen
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=yq1v8cdfuq6.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=Arthur.Simchaev@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--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