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>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH] ufs: core: Improve the documentation of UFS data frames
Date: Sun, 11 Jan 2026 22:04:23 -0500 [thread overview]
Message-ID: <yq1ms2j4jm9.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260106190017.2527978-1-bvanassche@acm.org> (Bart Van Assche's message of "Tue, 6 Jan 2026 12:00:17 -0700")
Bart,
> In source code comments, use terminology that comes from the JEDEC UFS
> standard. This makes it easier to compare the UFS driver code with the
> JEDEC UFS standard. Add static_assert() statements that verify the
> size of data structures defined in the UFS standard.
Applied to 6.20/scsi-staging, thanks!
--
Martin K. Petersen
next prev parent reply other threads:[~2026-01-12 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 19:00 [PATCH] ufs: core: Improve the documentation of UFS data frames Bart Van Assche
2026-01-12 3:04 ` Martin K. Petersen [this message]
2026-01-17 4:36 ` 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=yq1ms2j4jm9.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
/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