From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Christoph Hellwig <hch@infradead.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-scsi@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Stanley Chu <stanley.chu@mediatek.com>,
Avri Altman <avri.altman@wdc.com>,
Asutosh Das <quic_asutoshd@quicinc.com>,
Bean Huo <beanhuo@micron.com>,
Ziqi Chen <quic_ziqichen@quicinc.com>,
Arthur Simchaev <Arthur.Simchaev@wdc.com>,
Adrien Thierry <athierry@redhat.com>
Subject: Re: [PATCH] scsi: ufs: Include major and minor number in command tracing output
Date: Fri, 2 Jun 2023 08:19:07 -0700 [thread overview]
Message-ID: <ZHoIayr4wtYwQEHq@infradead.org> (raw)
In-Reply-To: <2490926f-d8cc-3ce4-7a00-b8db58c89848@acm.org>
On Thu, Jun 01, 2023 at 02:12:04PM -0700, Bart Van Assche wrote:
> I will look into removing the GROUP ID information from the UFS tracing
> output. Do you agree with adding the GROUP ID information in the SCSI
> tracing output after data temperature support has been added in the block
> layer and SCSI core? As you probably know the T10 committee recently
> approved Ralph Weber's Constrained Streams proposal.
Yes. It might take a while for that with the speed of the committee..
prev parent reply other threads:[~2023-06-02 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 22:39 [PATCH] scsi: ufs: Include major and minor number in command tracing output Bart Van Assche
2023-06-01 5:23 ` Christoph Hellwig
2023-06-01 21:12 ` Bart Van Assche
2023-06-02 15:19 ` Christoph Hellwig [this message]
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=ZHoIayr4wtYwQEHq@infradead.org \
--to=hch@infradead.org \
--cc=Arthur.Simchaev@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=athierry@redhat.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=jaegeuk@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mhiramat@kernel.org \
--cc=quic_asutoshd@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;
as well as URLs for NNTP newsgroup(s).